View Single Post
  #135 (permalink)  
Old Mon Jul 16, 2007, 04:11pm
Old School Old School is offline
Guest
 
Join Date: Nov 2006
Posts: 1,097
Quote:
Originally Posted by rainmaker
The not-switching-the-arrow thing is not the penalty for the kick. The new throw in is. The no-switching-the-arrow thing is simply because the throw-in was never completed. There's still only one penalty for the kick and that's A getting the ball for a throw-in.
However, when you consider the endline priviledge remained after the kickball, so the TI is still a ELTI, and it is also a kickball TI. How come the subsequent TI can not still be the APTI, like the ELTI, which then the next legal touch would cause the arrow to switch? Which is the way it should be. Delaying the AP Switch permanently until the NEXT held/jump ball is double jeopardy for the defense.

Quote:
The penalty for B causing the ball to go oob in the first case, and for B kicking the ball in the second case is the same -- A gets the ball for a throw-in. No one "takes the arrow away" from B. They simply don't get it if they kick the ball, because the APTI wasn't completed. It's the same thing that would happen if B committed a foul during A's APTI. The penalty is for the foul, and the arrow isn't switched. A keeps the arrow, but not because B fouled. It's because the APTI wasn't completed. Why is that so hard to understand?
The penality for the foul can have different consequences other than another immeditate inbound. I understand that, and unfortunately it is the same even if Team A commits the foul. However, something we have not talked about to much here. Why is it, if team A kicks the ball, the arrow switches but if Team B kicks the ball, the arrow remains, the APTI for this occurrence is now null and void? How is it that kicking the ball can have different penalities depending on who kicked it? The rule makers have really outdone themselves here.

Last edited by Old School; Mon Jul 16, 2007 at 06:20pm.
Reply With Quote