![]() |
Quote:
|
Quote:
What's really funny is after the NFL and NFL apologists defend that call, which is fine, they'll spin the wheel of excuses to write-off other penalties they don't call. Here's the current "NFL Official's Wheel of Bad/Wrong/Missed Calls Excuse": 1) It was a bang-bang play 2) We can't see everything 3) We can't call THAT at THAT point in the game 4) We were letting them play at that moment in the game 5) Players shouldn't allow bad calls to affect a game 6) Geeez we're part-time employees, this ain't even our main job 7) We're not perfect 8) XYZ is subjective 9) There's a hold on every play, we can't call them all or nobody would score 10) Radio silence |
Quote:
|
Are we not entertained?
The more I think about it and the money that these players make for playing a game, the less I'm inclined to even care about sports. We get bent out of shape, upset, rage on the internet for days and what is the outcome? |
Quote:
|
Quote:
|
Quote:
I suspect it's never called because you don't often have a WR standing that tight to the lineman and so far forward that his foot is literally past the nearest defenders head into the neutral zone. I mean damn fellas, what choice did he really give the officials with that one? It's just so stinkin' obvious. His BACK foot is lined up about where Rice's front foot is on the opposite side of the formation . Visually it's just so blatant. It doesn't get called because...well...most players aren't stupid enough to do it. It's just a REALLY bad penalty. There's no excuse for it. |
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">This photo removes all doubt. 19 was blatantly offside. <a href="https://t.co/KD0R0Rvguy">pic.twitter.com/KD0R0Rvguy</a></p>— ProFootballTalk (@ProFootballTalk) <a href="https://twitter.com/ProFootballTalk/status/1734210600471822339?ref_src=twsrc%5Etfw">December 11, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>
|
Billion dollar business - and I have to laugh that people actually believe the "ineptitude" narrative.
If the NFL thought it was a problem, it would have been addressed years ago. Add to that, the NFL does not allow coaches to challenge PI or other penalties.....I dont see any other conclusion than the NFL is perfectly ok with how officials call games. (cough - cough - vegas - cough) |
I want to be really mad about this - if Toney checked, that’s ridiculous for the ref not to scoot him back. This is jaywalking where there’s not much advantage to the penalty. At the same time the refs are gonna give a lot of leeway if he just lines up behind the ball. That’s probably the very simple ask and he did that poorly. You gotta enforce some of that so defenses know who’s eligible
|
Quote:
like I would be much less butthurt if the two penalties didn't have wildly different outcomes and reasonings. |
I had the same outrage that Andy/Mahomes are expressing now, LAST week over the missed DPI call.
I think that was way more egregious. Toney was blatantly offsides. |
Look at Taylor. They could've easily called him for illegal formation as well. I do not understand why these mistakes are being repeated on a weekly basis but the entire offensive coaching staff needs to get their collective shit together and get this ****ery under control instead of whining about the refs being mean.
|
Quote:
But sure, Pat. Let 'em play. And THIS: Quote:
|
Since game one this year, the refs have been hyper-critical of our alignment AND the timing of our get-off at the snap. The Chiefs are treated differently in these areas than other teams. Those are facts anyone can see.
I doubt this call is made in this situation if the whole fiasco against the Lions doesn't happen week one. NFL refs were badly embarrassed when the entire league-wide fanbase watched Cris Collinsworth criticize Taylor's alignment/timing during the season opener. A memo was circulated after that and they've been overcompensating with those calls against the Chiefs all season. |
All times are GMT -6. The time now is 11:28 AM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.