ChiefsPlanet

ChiefsPlanet (https://www.chiefsplanet.com/BB/index.php)
-   Nzoner's Game Room (https://www.chiefsplanet.com/BB/forumdisplay.php?f=1)
-   -   Chiefs Eric Fisher injured Friday [but is ACTIVE for Oakland] (https://www.chiefsplanet.com/BB/showthread.php?t=325080)

TEX 09-14-2019 06:58 PM

Quote:

Originally Posted by MightyMouse (Post 14446798)
This thread quickly went stupid

Fisher is a fine LT. league average is about right. You could do worse and we could go more in depth about the chiefs LT position in the future but for this season we have a problem.
Irving is decent depth on the inside but he is a major problem at tackle, this has been shown time and again. Rankins may suck as well for all I know but he may be the best option. Regardless it’s all about play calling if fisher is out and you want Mahomes to make it through the season.

Rankins will get Pat KILLED. He was the absolute worst of the Texans O-Lineman. He was not going top make the team, so they traded him to us for a guy who was not going to make our team. Hyde will help the Texans more than Rankin will help KC, IF he stays the same player that he was in Houston. I don't want him anywhere near Mahomes.

RunKC 09-14-2019 07:02 PM

Quote:

Originally Posted by pugsnotdrugs19 (Post 14446774)
They scored 24 mother****ing points that quarter just to stay in the game.

Spare me any bullshit about clock management.

That was Pat, not Andy.

HemiEd 09-14-2019 07:09 PM

Quote:

Originally Posted by -King- (Post 14446509)
Yep. Both of our losses to the Patriots and our loss to the Rams would have been wins if we didn't score so fast on our last drives.

ROFL I watched Arizona State play this afternoon and got a good reminder about Herm and "circus offenses"

I think one of Herms own players slipped on Herms jizz when the score was 3 to zip in the 4th quarter. ROFL

staylor26 09-14-2019 07:12 PM

Quote:

Originally Posted by RunKC (Post 14446808)
That was Pat, not Andy.

It’s really ****ing petty to bitch about clock management in that game.

Was it also on Andy that Pat missed a wide open Williams in the 1st half?

TEX 09-14-2019 07:15 PM

Quote:

Originally Posted by -King- (Post 14446509)
Yep. Both of our losses to the Patriots and our loss to the Rams would have been wins if we didn't score so fast on our last drives.

Well, we beat the Rams regardless if Scandrick, or however you spell his name, makes the INT, that was right in his hands, in the 4th qtr. It was a for sure pick 6, but a game winner regardless if he just caught the damn thing. :shake:

DaFace 09-14-2019 07:15 PM

Quote:

Originally Posted by TrebMaxx (Post 14446761)
Welp, another thread that has gone OT.

Are you new here?

rabblerouser 09-14-2019 07:24 PM

Quote:

Originally Posted by TrebMaxx (Post 14446761)
Welp, another thread that has gone OT.

Do your balls hurt?

JakeF 09-14-2019 07:40 PM

Quote:

Originally Posted by MightyMouse (Post 14446798)
This thread quickly went stupid

Fisher is a fine LT. league average is about right. You could do worse and we could go more in depth about the chiefs LT position in the future but for this season we have a problem.
Irving is decent depth on the inside but he is a major problem at tackle, this has been shown time and again. Rankins may suck as well for all I know but he may be the best option. Regardless it’s all about play calling if fisher is out and you want Mahomes to make it through the season.

If you can go multiple games without noticing your left tackle then he is better than average. Without his dumb penalties, Fisher can go a long time without getting noticed.
If he was more aggressive he would be damn good. Fisher is too passive, wish he would play pissed off all the time. Ask JJ Watt what Fisher is like when he's pissed.

KChiefs1 09-14-2019 08:46 PM

Quote:

Originally Posted by Hammock Parties (Post 14446335)
It'd be hilarious if "Gimpy Mahomes" was just 2015 Alex Smith and we started dominating TOP and nursing 7 and 10 point leads in the second half of games and laughing while the clock ticked down.


Gotta keep the scoring record going.

rabblerouser 09-14-2019 09:10 PM

Any updates?

RunKC 09-14-2019 09:31 PM

Quote:

Originally Posted by staylor26 (Post 14446817)
It’s really ****ing petty to bitch about clock management in that game.

Was it also on Andy that Pat missed a wide open Williams in the 1st half?

Pat was a first year starter. He was barely in the league for 20 months while Andy has been in the league for over 20 years. And Pat more than made up for his struggles in the first half with that amazing drive with 30 something seconds left to send the game to OT.

Look..if our defense is like last week and is not able to stop anyone from passing the ball at will, we need to have the intention of running the ball with our offense for a play or two to win the game.

2:54 left in that game at the Pats 40. We scored in 2 plays. That’s great, but we need to be more aware of the situation. That literally happened in the loss n NE where we scored fast and then the Pats used the rest of the clock to run it out to win on the last play.

Andy should have ran a few running plays to burn the clock. Put the ball in Pat’s hands to decide the game, not the defense. Force the Pats to burn timeouts. Who cares if it’s a no gain on first down? The offense can score from 40 yards in 2 plays. We really don’t think they can get 10 in 3 plays?

If the defense is like last year (hopefully it’s not), Andy needs to play it smart at the end.

I don’t want the game in the defenses hands praying they won’t **** it up. I want the game in the hands of our amazing QB.

staylor26 09-14-2019 09:33 PM

Quote:

Originally Posted by RunKC (Post 14446935)
Pat was a first year starter. He was barely in the league for 20 months while Andy has been in the league for over 20 years. And Pat more than made up for his struggles in the first half with that amazing drive with 30 something seconds left to send the game to OT.

Look..if our defense is like last week and is not able to stop anyone from passing the ball at will, we need to have the ability to change our offense to win the game.

2:54 left in that game at the Pats 40. We scored in 2 plays. That’s great, but we need to be more aware of the situation. That literally happened in the loss n NE where we scored fast and then the Pats used the rest of the clock to run it out to win on the last play.

Andy should have ran a few running plays to burn the clock. Put the ball in Pat’s hands to decide the game, not the defense. Force the Pats to burn timeouts. Who cares if it’s a no gain on first down? The offense can score from 40 yards in 2 plays. We really don’t think they can get 10 in 3 plays?

If the defense is like last year (hopefully it’s not), Andy needs to play it smart at the end.

I don’t want the game in the defenses hands praying they won’t **** it up. I want the game in the hands of our amazing QB.

You can’t just choose when you score when you have to score. It doesn’t work like that and anybody that thinks it does is a ****ing moron. If we run the ball for no gain or negative yardage and it kills the drive, you’d be bitching about that.

RunKC 09-14-2019 09:41 PM

Quote:

Originally Posted by staylor26 (Post 14446936)
If we run the ball for no gain or negative yardage and it kills the drive, you’d be bitching about that.

This offense scored 31 points in the 2nd half and went 40 yards in 2 plays for a TD.

We could do whatever we wanted on offense and the Patriots knew it LMAO

TLO 09-14-2019 09:44 PM

I had a dream last night he played.

Take that for what it's worth

UChieffyBugger 09-14-2019 09:48 PM

I'm expecting him to play tbh. Reports suggest he was laughing and joking in the locker rooms after the last training session so I would imagine it was merely a tweak. If he's not feeling good then rest him and let Allen play there. See how he fairs in the first three or so drives and if things aren't going to well then just make Pat get the ball out quicker and utilise the run game a little more...simple.


All times are GMT -6. The time now is 04:39 PM.

Powered by vBulletin® Version 3.8.8
Copyright ©2000 - 2024, vBulletin Solutions, Inc.