Quote:
Originally Posted by BillyMac
I'm not 100% against your "suggestion" to charge an immediate technical foul for a ball that's slapped away to oblivion, I might even react in such a way in the heat of a real game, but I just don't see any caseplay justification for such action, and in fact, see a caseplay that states that we must warn, with the exception of 9.2.10 SITUATION A which seems to indicate that we can charge a technical without warning when there are five seconds or less in a game.
I would like to see something stronger than a "suggestion", maybe a citation like a caseplay, or an annual interpretation.
This is a great start: 10-3 Player Technical A player shall not: Delay the game by acts such as: Preventing the ball from being made live promptly or from being put in play.
Can we take it to the next level because 10-3 alone seems to contradict Rule 10-1-5 and Caseplay 10.1.5.A, an existing caseplay that's very clear, which say to warn first.
|
Caseplays are mostly examples. 10-1-5 talks about delays, 10-3 prevention. A case covering delays doesn't imply how to cover situations that prevent the prompt live ball. I'd say that deliberately batting a ball into he stands prevents it from being made live promptly (its going to take a while to go get that ball) while knocking the ball 3-4 feet out if their grasp merely delays. It is a matter of degrees, just like contact fouls.