Quote:
Originally Posted by Snaqwells
If the dribbler cuts off a defender's established path, isn't he by definition setting a moving screen?
|
If a defender runs into a dribbler, isn't he, by definition, committing a block/push/charge?
Basically, you have two players that are moving such that their paths intersect. At least one of the two has the right to be moving at that time (sometimes both, but not in this case).
To determine which, you have to decide if A1 is screening or B1 is guarding.
Who is trying to get to where? Where is the defender trying go? Who is he trying to guard? Usually, the defender is attempting to guard the player with the ball. If it were a screen, who is the screen set for, who is it freeing up?
If A1 is trying to cut to the basket or otherwise make a play with B1 is trying to stop A1, this simply can not be a screen, it is a guarding situation. B1 must have LGP at the time of contact in order to be moving legally.
If B1 is trying to get to another player in order to guard them (perhaps a pick-and-roll type of play where B1 is trying to cover the roller), A1 must set a legal screen....with time and distance.
In the situation as presented, there is no indication that B1 was doing anything other than trying to stay with and guard A1. Thus, B1 is guarding (poorly) and A1 is not screening....guarding rules apply. During a guarding situation, the only path that matters is that of the offense...the defense must get in the spot before the offense. If they're running side by side, I don't see that the defender beat the player to any spot, the defender was late. Even if the dribbler did a perfect 90 turn toward the defender, the defender was moving and was never facing the dribbler...still a block.