Quote:
Originally Posted by Snaqwells
I think you're reading way too much into this wording.
If the defender hasn't done anything illegal, and hasn't done anything to lose LGP, then I don't see how a block can be called.
The only thing we're talking about him doing illegal is potentially faking a foul. If it's that obvious, warn or call the T. If it's not obvious, then I'd say it's a PC or nothing.
If your local leadership wants a block as the warning for a flop, then do that, but let's not pretend there's rule backing. This is sort of like making the wrong OOB call to save a foul; do it if you must, but call it what it is.
|
Ok, maybe we're not that far apart.
First, I was backing Scrapper's opinion with the specific rule. You ask what did B1 do wrong? 4-23-4(b) is pretty specific, and it does not differentiate between a player having LGP or not. If B1 did not get to A1's landing spot before A1 leaves the floor, it's a block on B1. You're the one that seems to be reading more into the rule - you seem to be advocating that the wording doesn't apply if B1 established LGP first, and the rule doesn't state that.
My point was while I agree with Scrapper on that point, it would have to be fairly obvious that B1 got the landing spot after A1 leaves the floor, and before A1 lands. B1 standing or laying on the floor doesn't matter. I think we agree on that. I think we also agree that if B1 slides to the landing spot before A1 leaves the floor, it cannot be a block. Or when A1 lands, then trips or falls over B1 on the floor, it cannot be a block on B1, because they got to that spot first.
All I was disagreeing with was the opinion that it will be a block on B1 because there was contact after falling backwards and attempting to fake being fouled. If B1 has and maintains LGP throughout the play, B1 did nothing wrong,
except if B1 gets to airborne A1's landing spot after A1 leaves the ground and before they land.