The Official Forum

The Official Forum (https://forum.officiating.com/)
-   Basketball (https://forum.officiating.com/basketball/)
-   -   Faking being fouled ... (https://forum.officiating.com/basketball/85812-faking-being-fouled.html)

ga314ref Sun Jan 15, 2012 01:54am

"22, stop flopping."

BillyMac Sun Jan 15, 2012 12:09pm

Both For The Flopper And The Floppee ...
 
Quote:

Originally Posted by bainsey (Post 813453)
Flopping is unsportsmanlike (and a little insulting), period.

And it could be dangerous too.

Adam Sun Jan 15, 2012 12:15pm

Quote:

Originally Posted by bainsey (Post 813453)
Just deal with the source, I say, and be 100% sure that the player is flopping. Being quite certain isn't enough.

I'll talk to the player when I get a chance, but if two or more players from the team do it, I'll talk to the coach instead.

Friday night I had a player do it in traffic; I just told him to get up, but would have called him for a foul if he had affected an opponent while on the floor.

Ignats75 Sun Jan 15, 2012 12:19pm

I had this in a BJV game last week except the OTHER coach WANTED the T. V1 flopped on two consecutive trips down the floor only to give up put backs. I told the home HC loudly enough for V1 to hear, "he didn't flop. he's just so uncoordinated, he tripped over the foul line." Home coach was a tool all night, starting at the opening jump. His team was up by 20 and won by 40 and he full court pressed for 28 minutes. He wanted every contact called and his team was bigger and stronger. I thought I was doing an LeBron James game again. (Now thats a flashback as bad as anything LSD could give me.)

packersowner Sun Jan 15, 2012 02:42pm

Quote:

Originally Posted by ga314ref (Post 813469)
"22, stop flopping."

I like visiting with that player. However, I might tell the player and the coach, "I'll give you the charge if there is contact, otherwise it's a technical if you are intentionally flopping."

I think this sets the right expectation with the coach and player.

icallfouls Sun Jan 15, 2012 03:26pm

BBRef
 
While my initial post may not have stated it, you misunderstood my meaning. So I take the responsibility for that.

Not my deal to just make up stuff that isn't there.

My meaning was along the lines of slight contact, not no contact.

just another ref Sun Jan 15, 2012 03:45pm

Quote:

Originally Posted by icallfouls (Post 813614)
While my initial post may not have stated it, you misunderstood my meaning. So I take the responsibility for that.

Not my deal to just make up stuff that isn't there.

My meaning was along the lines of slight contact, not no contact.

The principle is still the same. If it isn't a block, the flop doesn't make it a block.

Camron Rust Sun Jan 15, 2012 04:44pm

Quote:

Originally Posted by just another ref (Post 813618)
The principle is still the same. If it isn't a block, the flop doesn't make it a block.

So you're calling the T? If not, why not? That is what it really is.

Adam Sun Jan 15, 2012 04:55pm

Quote:

Originally Posted by Camron Rust (Post 813631)
So you're calling the T? If not, why not? That is what it really is.

If there's slight contact, I'll just consider it anticipation rather than faking. Either a no-call or a charge. But anticipation doesn't make it a block.

just another ref Sun Jan 15, 2012 05:20pm

Quote:

Originally Posted by Camron Rust (Post 813631)
So you're calling the T? If not, why not? That is what it really is.

Calling a T is an option. Calling a block because of a flop is not.

Camron Rust Sun Jan 15, 2012 05:56pm

Quote:

Originally Posted by just another ref (Post 813642)
Calling a T is an option. Calling a block because of a flop is not.

When there is contact (as is the case in the point under discussion) it is always an option.

just another ref Sun Jan 15, 2012 07:18pm

Quote:

Originally Posted by Camron Rust (Post 813649)
When there is contact (as is the case in the point under discussion) it is always an option.

It's an option whether there is contact or not. Anything the official chooses to do is an option, but this one is not supported by rule.

Adam Sun Jan 15, 2012 08:06pm

Quote:

Originally Posted by Camron Rust (Post 813649)
When there is contact (as is the case in the point under discussion) it is always an option.

I'm not seeing what the defender does wrong here. Slight contact, defender falls back, but maintains LGP. Why a block?

Camron Rust Sun Jan 15, 2012 08:23pm

Quote:

Originally Posted by Snaqwells (Post 813709)
I'm not seeing what the defender does wrong here. Slight contact, defender falls back, but maintains LGP. Why a block?

Contact enough to cause that reaction between the bodies and the offense did cause it, then the defender did (or at least that is the way you can sell it).

Adam Sun Jan 15, 2012 08:26pm

Quote:

Originally Posted by Camron Rust (Post 813719)
Contact enough to cause that reaction between the bodies and the offense did cause it, then the defender did.

Then we're picturing this differently. I see what would be an obvious charge mitigated by the defender bailing. Bracing or falling backwards in anticipation is expressly allowed, so I don't understand a block call.


All times are GMT -5. The time now is 01:19pm.



Search Engine Friendly URLs by vBSEO 3.3.0 RC1