![]() |
Quote:
|
I disagree.
I just think a lot of officials aren't going to reward a player who falls before contact. Sent from my iPhone using Tapatalk Pro |
I'm not talking about a player who throws himself/herself to the floor. In those cases, I defer to the offense since the defender made it impossible to tell how hard they were or were not hit. I'm talking about the play that leans back.
Fundamentally, there is no rule support for calling a block on a player that leans backwards before contact any more than their is for calling a block on a player that steps backwards before contact. Yet, there is plenty of rules support for the opposite. Such a player is only doing what LGP allows them to do...move obliquely/away and/or ducking/turning to soften the impact and they are not invading the vertical space of their opponent nor extending outside of their own vertical space over an opponent. To call a block or even to just not call the charge is rewarding the offensive player for running through the space legally obtained by an opponent...which only encourages reckless play. |
I'm sorry, but I don't see where verticality has to do with the offensive player. Every article in the definition (4-45) talks about the defender's verticality.
Perhaps giving me a scenario where the dribbler/shooter's verticality is necessary to know. Sent from my SM-G955U using Tapatalk |
Doing a trust fall backwards because you’re too scared to take the contact is not the same as ducking/bracing for the imminent charge.
Call a charge and have fun explaining to the offensive coach why you’re bailing out a defender who didn’t take the contact and put the offensive player in a vulnerable position. Call a block and it’s much easier to explain to the defender’s coach why you didn’t reward his guy. Plus that’s the expectation at the higher levels, and I disagree that there’s “no rules support” for calling it that way. |
Quote:
Fundamentally, calling blocks as a default encourages rough play. It encourages offensive players to go where it will create unnecessary contact when they should pull up or divert around a defender that has cut off the path. I'd rather get a call right than choose the call that may be easy to explain. That was the case for a long time with being "set". Only are most officials starting to call it correctly after decades of using "set" as the criteria. And if you say there is rules support for calling a block, I'm waiting for you to cite such rules. |
Quote:
But, that is really just a distraction from the main point. You've still not shown anything where the defender violated the verticality principle other than proclaiming it. |
Quote:
Sent from my SM-G955U using Tapatalk |
Quote:
|
Quote:
Quote:
Quote:
|
Quote:
Quote:
And let's put to rest the idea that the defender is in any way responsible for putting the offensive player in a vulnerable position. The offensive player is responsible for being in control of his body. If the defender not being there to bang against leaves the offensive player in a vulnerable position, that is the offensive player being out of control and is his own responsibilty. |
Quote:
|
Quote:
|
Quote:
My priority in these situations is: (1) to get them to stop flopping (2) make a correct call in that order. Sent from my iPad using Tapatalk Pro |
Quote:
Those posts are showing everyone why the rule of verticality does not apply to this situation. And why your continued suggestions that I think otherwise are wrong. Sent from my SM-G955U using Tapatalk |
All times are GMT -5. The time now is 12:52pm. |