ChiefsPlanet Mobile
Page 194 of 194
« First < 94144184190191192193194
Nzoner's Game Room>**** The Official Buccaneers vs Chiefs GameDay Thread ****
Tribal Warfare 12:00 AM Yesterday
Tampa Bay Buccaneers vs Kansas City Chiefs odds - Nov 4


Spread Favorite: Kansas City (-9)
Moneyline: Kansas City (-446), Tampa Bay (+346)
Total: 45.5 points


[Reply]
Gravedigger 09:52 AM Today
And if the 2 point conversion fails then people would be saying “Why would you go for it against that defense in Arrowhead instead of having a chance in Overtime!?!?!?” Always convenient that your visions of hindsight forsee the correct outcome.
[Reply]
DJ's left nut 09:55 AM Today
Originally Posted by BigRedChief:
The film in all the previous games has shown him open deep at least twice every game and Mahomes was looking at it him and didn't thrown the touchdown ball. We need him to stretch the field and let Dhop and Kelce work their magic underneath.

He's a rookie who was going to be brought along slowly like most rookie WR's in an Andy run offense. Due to injuries, he's thrown into the fire. I hope he's not stupid, it was just a rookie mistake that wont happen again. But, Veach doesn't usually draft stupid kids out of college. So, I'm still on the Brown train.
I've said this for years but "He was open on X throw" just means so very little to me.

Guys are open on throws almost every single down. QBs complete about 2/3 of their passes, right? So lets assume an average QB throws 15 incomplete passes in every game. And I'm gonna say there's someone 'open' on at least 10 of those most games. And hell, on COMPLETIONS there are usually guys open downfield that would've been better plays. It's just the nature of football.

Missed shots is one thing (and yeah, Mahomes has missed a couple of those. Damn I'd have liked to have seen that deep ball to Watson thrown to Xavier because Mahomes put GREAT touch and arc on that ball. Juuuuuuust a little more speed from a guy who's slightly better at tracking the ball and you have a 6). But "he was open on 4 plays where he didn't get the ball" is Skyy Moore stuff.
[Reply]
ChiTown 09:55 AM Today
Originally Posted by BigRedChief:
The film in all the previous games has shown him open deep at least twice every game and Mahomes was looking at it him and didn't thrown the touchdown ball. We need him to stretch the field and let Dhop and Kelce work their magic underneath.

He's a rookie who was going to be brought along slowly like most rookie WR's in an Andy run offense. Due to injuries, he's thrown into the fire. I hope he's not stupid, it was just a rookie mistake that wont happen again. But, Veach doesn't usually draft stupid kids out of college.
I think he'll be fine, but he's got to step up his field recognition and intensity. That was a completely regrettable performance, and deserving of getting your ass benched...if we actually had someone that could take his place. He's lucky we are so razor thin at WR.

Hopefully he bounces back and has a better game vs the Donks.
[Reply]
Shiver Me Timbers 09:55 AM Today
Originally Posted by Gravedigger:
And if the 2 point conversion fails then people would be saying “Why would you go for it against that defense in Arrowhead instead of having a chance in Overtime!?!?!?” Always convenient that your visions of hindsight forsee the correct outcome.
exactly ^
[Reply]
Nirvana58 09:55 AM Today
Originally Posted by Al Bundy:
The only real bad call was the call on Wirfs that wasn't a face mask.
Made no difference. It was a hold either way. People are up in arms about 5 yards.
[Reply]
DJ's left nut 09:57 AM Today
Originally Posted by Gravedigger:
And if the 2 point conversion fails then people would be saying “Why would you go for it against that defense in Arrowhead instead of having a chance in Overtime!?!?!?” Always convenient that your visions of hindsight forsee the correct outcome.
Yeah, I don't buy that for a minute.

That entire stadium sat there confused as Bowles sent the kick team out. And when it was obvious it wasn't any sort of ruse, the relief was palpable.

I suspect that was the consensus on Twitter and the folks at home as well.

When the other team is elated at the decision you've made, you've probably made the wrong decision. And literally every Chiefs fan, coach and player knew that Bowles was making the decision most likely to give Mahomes a chance to win that game for them.

No, I don't think he'd have gotten beaten up for that at all. Because nobody expected Bowles to do that even as the Bucs drive started. We all assumed that was a 'game on the line' drive. Nobody expected OT there.
[Reply]
philfree 10:02 AM Today
Maybe a vet gets both feet in but Worthy caught the ball where it was thrown. But oh woe is me field awareness! Over Reaction Planet is on par once again.
[Reply]
philfree 10:05 AM Today
8-0:-)
[Reply]
Bearcat 10:27 AM Today
I mean, everybody was calling for the two point conversion before they even scored the touchdown... the guys on ESPN were talking about it before they scored and there were several mentions of it in this thread and on Twitter.

That's.... not hindsight.
[Reply]
ThaVirus 10:33 AM Today
Originally Posted by DJ's left nut:
Nobody seems to have mentioned it, but in the "Why didn't Bowles go for 2" conversation, I think Mahomes is the reason.

Because with 26 seconds and 3 timeouts with a loss on the table if he doesn't get into FG range, you KNOW Bowles was worried about him driving it down the field with 4 downs and getting the game won in regulation.

I think Bowles was content taking his chances with a coin toss because he thought that was a better scenario than giving the ball back to Mahomes. Which makes you wonder why he took a timeout after that play that put them at the 1.

If you're THAT worried about Mahomes, either force KC to use a TO there or simply let the clock run to about 15 seconds before you call that next play. That's still time for 3 plays from the 1.
Bowles is a nice guy and a defensive guru but also a conservative pussy. Always has been.

I believe him when he says they gave “very minor consideration” to going for 2 there. It probably wasn’t even on his radar.

Bigger issue than not going for it was calling a timeout when they got to the 1 yard line with 30 seconds left. I suppose he wanted to leave some wiggle room to be able to run the ball without worrying about time expiring but it didn’t make much sense to me.
[Reply]
WilliamTheIrish 10:37 AM Today
Originally Posted by Chiefspants:
He looked like the spitting image of Year 2 Hardman out there. Not good.
First time all season I yelled at the TV on that play where X didn’t know where the sideline was. That drive, up to that play, was just beautiful.

Hunt/Kelce/Hunt/Kelce/Hunt/Kelce

And then that transient ischemic attack to Worthy’s brain just took the air out of everything. That play was set up so perfectly the only player who could fuck it up was Worthy.

The NFL game today is so dependent on little switches in momentum. Forcing a FG on that drive is a defensive win. Getting the sack and forcing the punt was a huge turn.

I think Worthy will be okay, but damn, that was a big play in the game.
[Reply]
MMXcalibur 10:40 AM Today
Originally Posted by DJ's left nut:
Nobody seems to have mentioned it, but in the "Why didn't Bowles go for 2" conversation, I think Mahomes is the reason.

Because with 26 seconds and 3 timeouts with a loss on the table if he doesn't get into FG range, you KNOW Bowles was worried about him driving it down the field with 4 downs and getting the game won in regulation.

I think Bowles was content taking his chances with a coin toss because he thought that was a better scenario than giving the ball back to Mahomes. Which makes you wonder why he took a timeout after that play that put them at the 1.

If you're THAT worried about Mahomes, either force KC to use a TO there or simply let the clock run to about 15 seconds before you call that next play. That's still time for 3 plays from the 1.
The Bucs lost the game when they took that timeout at the 1 yard line.

They lost all ability to drain the clock from that point on.
[Reply]
Page 194 of 194
« First < 94144184190191192193194
Up