KSUFans Archives
Sports => Snyder's Electronic Cyber Space World => Topic started by: michigancat on October 16, 2006, 09:30:55 AM
-
1) The fake FG was pretty bad, maybe cost us 4 points.
2) Late-half clock management was bad, maybe cost us 3-7 points.
3) I don't see how everyone thinks a QB sneak is a guaranteed TD with this offensive line. I'm not saying I liked the Patton run, but you can't say that we score a TD with any degree of certainty by running a sneak...it was too late to make a difference, anyway.
IMO, the problem with coaching is primarily offensive line development, not in-game strategy.
-
I guarantee we score if we run the sneak. I say that with a huge degree of certainty. See, I can say it.
-
I guarantee we score if we run the sneak. I say that with a huge degree of certainty. See, I can say it.
Dammit.
-
The gameplan was fine going into the game.
We sold out on the FG and got burnt. I'm sure our guys were told to look for fake, and one or two players are responsible for a TE or upback leaking out, we missed it. Good execution by the Huskers there.
We went in trying to establish a running game and NU stopped it. We went to the passing game and were able to move the ball at times.
The fake punt was about as gutsy a call as I've ever seen.
I was disappointed we didn't try a sneak there as well, but it was obvious there was a miscommunication on the oline b/c the NU DT came through untouched.
Got to learn from the mistakes in that game and move on, the results were about what I expected, but I thought the spread would be around 10. That would've been about right had we punched it in inside the 10.
-
1) The fake FG was pretty bad, maybe cost us 4 points.
2) Late-half clock management was bad, maybe cost us 3-7 points.
3) I don't see how everyone thinks a QB sneak is a guaranteed TD with this offensive line. I'm not saying I liked the Patton run, but you can't say that we score a TD with any degree of certainty by running a sneak...it was too late to make a difference, anyway.
IMO, the problem with coaching is primarily offensive line development, not in-game strategy.
I don't know what to call it...gameplan or offensive scheme...but we don't seem to try to mitigate, through the use of formations or playcalls our o-line sucking. Now, I know there is only so much you can do with this o-line becasue they have some major issues, but we can't seem to run plays that will aid in them not taking so much heat (i.e. screens, misdirection, etc.). IIRC, we've executed maybe one screen correctly, and I haven't seen a QR screen ever. We rarely try to use inside shovel passes or even a designed QB draw, nor have we, from what I've seen, tried to cut down the line splits to help out with the pass rush and general blitzing/pressure that occurs up the middle. Our offensive "gameplan" was okay I guess, if the gameplan was for Freeman to run for his life and complete passes.
-
The shovel pass did work once...I don't remember them going back to it, even though they might have tried it but the execution was just horrible.
The offensive line is just beyond bad...I don't know if playcalling can cover that fact up any more than it already is.
-
The shovel pass did work once...I don't remember them going back to it, even though they might have tried it but the execution was just horrible.
This is going to be every ku fan's reasoning behind predicting a win against us.
-
The offensive line is just beyond bad...I don't know if playcalling can cover that fact up any more than it already is.
I agree; maybe they are that bad and there just isn't anything the coaching staff can do. I know that ku cut down their line splits after the first quarter against NU and had some success protecting Barman and running the ball; but then again their o-line appears to be atleast Big 12 competent. We seem to be able to move the ball between the 20's, relatively speaking, and then urinate down our leg in the redzone.
-
Our main problem is red-zone offense and 3-d conversion. While we aren't moving the ball that great, it's ridiculous that we average 27 yards per point scored. Last year we were at 13 yards per point scored.
-
27 yards per point scored
:flush: Baseball-esque made up stats
-
In 2002 it was 9.7 yards per point.
:love: :love:
-
Entire B12:
UT 8.6 (!)
MU 12.2
BU 12.7
OSU 13.5
NU 14.2
CU 14.9
ku 15.0
aTm 15.7
OU 16.2
TT 20.1
ISU 23.7
KSU 26.8
-
Christ. I thought we would be an "efficient team" under Prince.
-
Prince @UVA:
2003: 13.8
2004: 14.0
2005: 13.7
-
to me, it didn't make sense to think we could come out running like we did against osu. it killed our whole first half and dug us a hole. we are going to have to embrace being a passing team this season to have any real success on offense.
-
I can't get over the non-TO's at the end of the half. 8-year olds on x-box can figure that out.
-
" will aid in them not taking so much heat (i.e. screens, misdirection"
Screens/ misdirection work well only with good offensive lines.
-
The time management was atrocious. I think the only reason the max protect, running game was somewhat effective against OSU was that they had not prepared for it. Look, Patton has some talent but our O-Line is beyond pitiful. I think misdirection should have some positive impact because as quickly as the opposition's line blows past our guys, we should be able to counter against that.
I think we should try to execute a short to mid range passing game as our basis, and mix in traps and misdirection/cutback running plays that negate pressure to slow down the rush so that we can then take a few shots down the field...with a rolling pocket. I think that is the only logical approach when your line can't run block or pass block. We tried to build on our running game but the line is obviously too pathetic to run when the other team knows we will...even with 2 tight ends and another in the backfield. That is a power formation and allows the D to bring 9+ guys into the box. There is no room for a back to find a hole with that alignment and no blocking.