![]() |
The MVS no call is the worst no call I've ever seen
How in the **** do you not call that? I've never ever seen such an obvious penalty by a DB in my life, and I've watched some shitty as corners in my Chiefs fandom.
Just unbelievable |
Forgetting the Rams and Saints in the playoffs?
|
You know it’s bad when…
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">Blatant pass interference. Ref gagged at Lambeau.</p>— Skip Bayless (@RealSkipBayless) <a href="https://twitter.com/RealSkipBayless/status/1731529759811899475?ref_src=twsrc%5Etfw">December 4, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
Chiefs get all the calls!
|
I don't understand what this refs are looking at -- some calls are really hard. That one is not.
|
Forward progress call was worse.
|
Ask the Saints. That was worse and the situation was much bigger.
|
Yet they will receive no discipline, this league is a ****ing joke.
|
They were afraid to call it after ****ing up earlier in the drive. This shit is ruining the sport.
|
Repeating ain't for pussies
|
MVS is such a bad receiver he can't even get obvious PI calls
|
Quote:
|
Wonder how much extra cash the refs got in their pockets tonight from the gambling people. 18 point swing for Green Bay on 3-4 calls.
|
This is the most obvious DPI I've ever seen. Its so obvious it should be shown when teaching pee wee players how NOT to commit the penalty
<blockquote class="twitter-tweet"><p lang="en" dir="ltr">This is ****ing unbelievable. Just flat out choosing to miss this call…the defensive back was trying to go on a piggy back ride with MVS & it wasn’t called <a href="https://t.co/U9gtgehUGS">pic.twitter.com/U9gtgehUGS</a></p>— Braiden Turner (@bturner23) <a href="https://twitter.com/bturner23/status/1731531490461135334?ref_src=twsrc%5Etfw">December 4, 2023</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script> |
Quote:
|
It was an awful no call. I refuse to grovel about missed calls losing games. Play better and don't let it come to that. Loser fan bases complain about refs losing games.
The offense is awful. Full stop. Losing several starters on defense hurt for sure. How many NFL games do you expect to win scoring 19 points though? |
Horrific non-call but **** being down by 8 to the Packers. The offense just doesn’t have the playmakers to execute the level of offense we are used to seeing.
|
How the **** can everyone watching the game see PI except the people paid to see it?
|
Quote:
Quote:
|
I do hate seeing refs deciding games like that
|
Quote:
|
Quote:
|
Given that MVS was the intended receiver, it was ruled uncatchable.
|
Quote:
|
Refs suck
I hate nfl referees. They ruin the game. It is the away team vs home team vs blind 0 iq referees.
|
Quote:
Heh |
It wasn't just that call, but that was the most blatant example of their steering that game in the Packers' direction. That was the first game we'd truly been ****ed by the refs since the Brady SB loss.
|
|
Quote:
|
Not the worst ever but pretty ****ing awful. I really hope some of our guys say **** it and get some fines from the post game press conference.
|
Quote:
On the first drive, I think we made a mistake not running ball in the red zone. Those sacks killed the drive. Second drive, the phantom Creed hold killed the drive. In the second half, we went: Touchdown Touchdown Punt (missed PI, which was also pretty blatant) Interception (pick who you want to blame there) End of game (missed blatant PI) So really, refs ended 3 drives. Play calling probably killed the first drive. Either Skyy or Mahomes killed one drive. I’d say A LOT more blame goes to the defense tonight. They gave up extra yards all over the field. |
Sometimes calls get missed and sometimes they get called.
We have seen that and far lesser calls against the Chiefs for years. The game against the Raiders in 2017 saw 4 of those late in the game called that were far more egregious. I'm usually not one to complain about a call or two, but that in isolation is just insanity. I won't say that it cost us the game but between that and some other questionable penalties, it didn't give us a real shot at the end. |
Worst this season for sure. The funny part was if the guy had let MVS actually try to catch it he only has a 50% chance to catch lmao
I still say the real key to the L is Mahomes making a poor decision, going away from running that last drive etc. |
It was bad. The DPI GB got hosed on and the unnecessary roughness against them were almost as bad.
This officiating crew made so many errors that it isn’t possible to tell what the outcome would have been otherwise. |
Quote:
|
When millions of people watching the game see the foul and the people paid to watch for fouls don't, it's hard to argue things are rigged for one reason or another.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
I feel pretty confident we would've mucked up the 2 point try anyway. But god damn. That was a horrid call. To be fair, the personal foul hit on Mahomes was a bad call too, but the non-PI had much more sway.
|
Quote:
|
Quote:
So how does that change your evaluation of the game and how do you advise everyone else who clearly understands its implications to adjust? |
The chiefs got 2 bad calls in their favor on that last drive. The late hit out of bounds on mahomes was bullshit and a free 15 yards. Then there was a short pass the receiver went out of bounds well back towards the line of scrimmage and they stopped the clock when the clock should be running in that situation.
|
The ref probably thought it was uncatchable because it's MVS.
|
Quote:
|
Quote:
It happens to every defense, and I’ll assume the injuries had a lot to do with it. Can’t help but think one or two of those big gains on first don’t happen with Tranquil in there. I’ll blame the defense for this, but also give them a pass. I’m not giving up on them by any stretch after this. |
Quote:
|
Quote:
|
They didn't want two penalties in a row for the chiefs.
And honestly this is on Andy. No reason to blame the chiefs. We sucked. Unprepared. We are not fixing our problems. We are predictable on offense because they cannot catch. |
The ref was brad allen.
|
I am sure we will get an apology letter from the NFL this week....as if that makes it better
|
Quote:
|
Quote:
Holy shit. |
Quote:
Sent from my SM-S906U1 using Tapatalk |
Nothing will change.
I almost think the NFL likes the controversy. People talk about it and no one stops watching. The ratings continue to increase. Want change? Quit watching. Force them to confront the issue. |
Quote:
The referees are just shit. |
Quote:
|
Quote:
|
Happens to every team every week. This call doesn’t define the reason the chiefs lost this game.
Example: A few plays earlier Mahomes was tackled while running for a first down while still inbounds but the Packers were flagged for 15 for a personal foul. That was a garbage call against them. |
It was obviously but the refs had their orders.
|
Quote:
|
Quote:
My bad. |
Quote:
|
I understand the no-call with a dozen guys bumping while going up for the hail-Mary in the endzone. But one-on-one with the DB jumping on the receiver's back and putting him in a choke hold is just so blantant and obvious that the refs on that crew should be fined by the league. (they won't be)
|
Chiefs win by 10 if the Chiefs play Chief Ball (although it might require Skyy Moore do die a horrible death) even with the dog**** officiating.
But the officiating was DOG ****, this was the worst instance of the night but shit officiating was taking me out of the game all night long. |
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Not even close to the worst no-call. Hell, it probably isn't the worst this week.
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
Quote:
|
I want to be mad.
But we didn't deserve to win that game. So ultimately I just can't get there. |
Quote:
|
All times are GMT -6. The time now is 05:36 PM. |
Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2025, vBulletin Solutions, Inc.