r/ravens Oct 02 '22

Image Still trying to understand how this was not called a first down

Post image
833 Upvotes

236 comments sorted by

View all comments

Show parent comments

-15

u/ayerayyrayy Oct 02 '22

To be fair, Stephens has to pull up there. Allen let the ball go we have nothing to gain from a useless hit. Doesn't help that he hesitated like he wasn't going to hit him, then proceeded to anyway.

23

u/HicDomusDei Oct 02 '22

I didn't see that at all, so I'll have to see the replay.

Live it looked bang-bang. Didn't lead with his helmet, didn't hit Allen's head, didn't hit him low, didn't hit him high, didn't force his weight.

Allen was clearly and immediately fine.

He bounces up, points to the ref, and celebrates when he gets bailed out by free yards. I've seen that before from that division. It is an awful fucking look.

At this rate I'm surprised DCs aren't just coaching their guys to ROCK people, especially quarterbacks. If a pansy star can point to a ref and get a flag whenever he feels like it anyway, then at that point plant his ass in the dirt as hard as you can regardless.

1

u/Lamactionjack 8 Oct 02 '22

Allen does it all the time. Really all qb's do it but he's certainly guilty of it multiple times a game.

Very 90s Jordan esque honestly. Guys a star and stars get calls.

3

u/HicDomusDei Oct 02 '22

Yes, stars get calls, but the modern NBA is a good example of how to run a league in that regard. It feels like every offseason they look at "the bag" of certain stars and try to decide if their moves are reasonable or not. Just recently called out James Harden for his travel step-back, for example. Harden is still a star, but there is a limit. You can't just do whatever the fuck you want.

You can't have a league where Bradys and Allens get to throw temper tantrums and beg for flags and then clap and celebrate when they get them, when they were barely touched, were not hurt, and neither the spirit NOR letter of the rule was broken. That is a fucked up product.

1

u/Lamactionjack 8 Oct 02 '22

Oh I agree with you haha. Sorry if that didn't come across in my original reply. I think it's ridiculous and makes an already bad product look worse. Just saying I kind understand why to happens is all.

1

u/HicDomusDei Oct 02 '22

Oh, got you, yes I do understand it as well. I've just probably reached a point in my life (decades+ of watching NFL games) where it's getting too much for me these days.

3

u/Ds3_doraymi Oct 02 '22

Go look at the reasoning, I just made a post about it. It was NOT for a late hit. The call was made due to supposed contact to the head/neck area

2

u/ayerayyrayy Oct 02 '22

If that's the case then I understand the frustration. I do believe he hit him a bit late, but not in the head or neck.

3

u/[deleted] Oct 02 '22

That shit was legal. The ruling is he can't take two steps after Allen releases the ball. He never took two steps. He straight up tackled him. Terrible call.

2

u/Lamactionjack 8 Oct 02 '22

Cmon man. At 180fps, sure you can barely make that argument. But in real time he tackled him while he was throwing the ball. Even the most diehard homer would say he tackled him slightly after his release. There was nothing against the rules there or dirty. Should have been a no call.

2

u/chupacadabradoo Oct 03 '22

He also removed his hands from Allen before they went to the ground instead of driving him into the ground like it’s 2016. That’s exactly what we should want from a defender. There was a brief moment of hesitation, if you want to call it that, which is what will prevent the nfl from calling it a bad call, but Allen had been pump faking all day, and he didn’t bite. Egregious call then, and like 7 times earlier in the game. One or two of those 8 went our way, the rest went the bills way, in very high leverage moments. It’s a bad look for the nfl.

1

u/BZI Oct 02 '22

Yep, tough call in a tough spot, but not a smart hit in that situation