Quote:
|
Originally Posted by Johnny Ringo
Now, I was asked what I would do in this situation, but am curious to what you all say.
My thought was to tell/warn B1 not to do that again or call a delay of game warning on Team B.
|
Why would you have considered giving a "delay of game" warning? Didn't he speed the game up by kicking the ball against the wall?
This thread reminds me of a Rec League play I had a couple years ago:
Team A is running their offense in the front court (I know, in Rec ball this is either an oxymoron or a conumdrum). A2 throws a pass back to A1 who is unguarded near mid-court. A1 drops the ball and it rolls slowly into the backcourt. A1 chases the ball into the backcourt but doesn't touch it. When the ball is 1/2 way between the half-court circle and the 3-point line B1 & B2 finally catch up and converge on the ball. Just as B1 goes to reach for the ball A1 kicks the ball very hard and it sails OOB towards B's basket.
Of course I call a ....... wait... here it comes....gee, I forget if I called a 'kicked ball' or a 'b/c violation'. Either way Team B is screaming for me to call a technical foul. For amusement sake I ask why. Someone says "because he intentionally kicked the ball", so I say "but kicking the ball is a only a violation" and they respond "it should be a tech because he kicked it so hard". I could only laugh at that argument. What's really bad for Team B is that they lost by 1-point on a 3-pointer at the buzzer from halfcourt and I had clock responsibilities for the play. They really didn't like me then.