View Full Version : I`ve been trying not to bash Raye...
09-10-2000, 06:11 PM
But, I can no longer hold back!
This guy is a bonehead!
He proved it on that series when the Chiefs had 1st and goal-4 runs, no score!
09-10-2000, 06:19 PM
I wonder when someone on offense will speak
up about this?
09-10-2000, 06:23 PM
I'm no Jimmy Raye fan, but I still think a lot his playcalling is dictated by Gunther's wishes. Don't get me wrong, I want him gone as much as the next person. But I got a feeling the next OC won't do a whole lot better as long as Gun is the HC. I hope to be proven wrong.
09-10-2000, 06:25 PM
I agree that was total bonehead play calling but don't you think our OL should've been able to jam that down Tennessee's thoat? Our running game has been horrible. I actually liked going for it on fourth down. Even though a FG in that situation would have won us the game. Obviously, my last statement makes the dangerous assumption that Stoyo has the leg to make that kick.
[This message has been edited by AZChief (edited 09-10-2000).]
09-10-2000, 06:26 PM
Stoyo probably could have made that one.
Bob Dole feels that his outside range is now the 10-12.
09-10-2000, 06:28 PM
AZ - IMO, our running game has been bad because our opponents have game-planned exclusively on stopping it! And why not? Gun comes right out & says what we're going to do. Our players come right out & say what we're going to do. Our OC predictably calls games just as Gun and the players stated. It's almost comical -- actually, it would be hillarious if I weren't a KC fan.
09-10-2000, 06:28 PM
It wasn`t a bad idea going for it on 4th-but a little creativity would have helped-a fake hand-off and EG on a naked bootleg.SOMETHING!
09-10-2000, 06:35 PM
HC & KC30-I agree, something to mix it up would help us. I just can't believe that a team that relies so heavily on the run can't smash it in from the inch line. I feel our young D has played well enough for us to win the last two weeks and our Offense continues to be totally inept.
09-11-2000, 12:55 AM
I must respectfully disagree with most of you. I am no fan of Gunther C., but calling four runs in that situation was the right thing to do. A running team simply HAS to be able to run it in from that close. Why has the Chiefs running game gone into the toilet this year, with the same players as 1999?
P.S. Bennett would have scored.
09-11-2000, 01:27 AM
If we're going to run it 4 straight plays, at least give it to TRich 4 straight times.
09-11-2000, 02:31 AM
Ok, I'm convinced. We should try out OCBC. Offensive Coordinator By Committee!
Reasons to get serious about offense:
#1 - RBBC sucks. It doesn't allow you to follow any sort of rythym on offense. Only with the Chiefs can a RB rip off a 28 yard run and be benched for the rest of the quarter! While the coaching staff may feel this makes the running backs 'hungry', what I really think it does is distribute the blame. If nobody is accountable why try your hardest?
#2 - Predictability. Who at home or in the stands can't guess the playcalling? For those who haven't learned the pattern yet (must be new to KC football!) it goes like this:
Run - Run - Pass
Sometimes when we're feeling cocky it goes:
Run - Run - Run
Last Sunday, my girlfriend was watching the game for a little bit and said to me, "I thought they had to run twice before they were allowed to throw the ball". It shocked her that other teams were throwing the ball on first down! She doesn't know a lot about football, but she could probably run our offense already!
#3 - Stupid playcalling. If you're going to follow a pattern as outlined above, perhaps you should make sure it works! We were moving the ball fairly well several times today. When we made it to the end zone and ran four times only to turn it over on downs, I about threw my shoe at the TV. Grrr!
Too many times we seem like we're trying to make a statement with our running game. This is all swell and good if it works. When it doesn't work and the passing game does, quit running so damn much! Stick with a winner...
vBulletin® v3.8.8, Copyright ©2000-2017, vBulletin Solutions, Inc.