Unusual and weird situation resulting in ejection

[Adam]

Originally Posted by justacoach

I would normally ignore these errant pronouncements save for the fact that you are 'representing' every official who walks on a court. I strongly suggest you follow up on your stated desire to hang up your whistle, and that you do so immediately. How can you suggest such a faulty course of action that has absolutely no basis in any rules set extant. The proper treatment for flopping is clearly delineated in the citations presented throughout this thread. You need to learn how to be more detached in the execution of you officiating responsibilities. Leave your emotional baggage in the locker room and refrain from bringing your sh!t into OUR game.

Let me just say this, in some places, a block on this place is an acceptable way to put a stop to it. Personally, if I were to do it that way, I'd accompany it with a warning to the player letting him know why I called it. Next one is a T.

[just another ref]

Originally Posted by Snaqwells

Let me just say this, in some places, a block on this place is an acceptable way to put a stop to it.

The rulebook ain't one of them.

[Adam]

Originally Posted by just another ref

The rulebook ain't one of them.

True, but the rule book doesn't advocate using advantage to determine palming or three seconds; nor does it advocate taking 15 seconds to get to 10 on free throw.

There are other regional practices not explicitly allowed by rule, either.

[just another ref]

Originally Posted by Snaqwells

True, but the rule book doesn't advocate using advantage to determine palming or three seconds; nor does it advocate taking 15 seconds to get to 10 on free throw.

Good point, but all these thing involve varying degrees of ignoring things that happened. Calling something that didn't happen, imo, is considerably more serious.

[Adam]

Originally Posted by just another ref

Good point, but all these thing involve varying degrees of ignoring things that happened. Calling something that didn't happen, imo, is considerably more serious.

Like calling OOB on green when they committed a small foul on white causing white to knock it OOB?

[just another ref]

Originally Posted by Snaqwells

Like calling OOB on green when they committed a small foul on white causing white to knock it OOB?

I'm all for this one. However, there is another association near me who reportedly has the policy that as long as the defense knocks it out, there is no foul. Period. Kinda like partially blocking a punt and not drawing a flag. As long as you get a small piece of the ball, you can take as much of the kicker as you want along with it.

[Jurassic Referee]

Originally Posted by just another ref

The rulebook ain't one of them.

+1

If you call a block instead of the correct call, you're making up your own rules. Flopping, by definition, has no or incidental contact. It's faking being fouled. Blocking is a foul using illegal contact as the criteria. Completely different animals with completely different penalties.

In my experience, the people that advocate calling a block on this situation usually do so because they feel they will get less flak from the coach if they make that call. That's the wrong reason to make any call imo.

My motto is "If I'm gonna make a call, I might as well make the right one."

[mbyron]

Originally Posted by Snaqwells

Let me just say this, in some places, a block on this place is an acceptable way to put a stop to it. Personally, if I were to do it that way, I'd accompany it with a warning to the player letting him know why I called it. Next one is a T.

Working in one of the areas where officials call a block on a flop, I agree with your claim.

That said, I don't like the call. For one thing, with no contact it's just not a personal foul, and block is the wrong call. For another, you might end up punishing the offense if they might have had a shot and the foul interrupts the game.

I use a version of "wave, warn, whack." The first instance, when I see the player on the floor I'll wave "upward" in a "get up!" signal. The purpose is to signal that I saw the whole play and the flopper ain't gonna get that call. Next time, I verbally warn the player and coach. Then whack.

I've found that just signaling that I saw what happened and passed on the "contact" usually sends a message and it doesn't happen again. This serves the same purpose as a warning (ending the behavior) without slowing the game.

If a verbal warning is necessary, I find that including the coach lays the groundwork if I have to give a T.

Some of you might find that this method has one layer of warning too many (or wouldn't bother with the coach). I understand -- the method certainly isn't in the manual -- but my rationale for it is that nobody calls that T around here, and nobody expects it. So if I'm going to call it, everybody in the gym needs to know that it's coming. YMMV.