Week 7 AAC Games and CFB in General

[Hueyhog20]

The CFP committee is going to have UCF at around 12-15. There will be many one loss teams ahead of them, and I bet two loss teams will jump them after they have a win against a t25 team. Just the way it is. 

[bullsfan1983]

I say we move to 20. Lots of top 25 lost and many of those that won were not impressive. 

[NewEnglandBull]

2 hours ago, bullsfan1983 said:

I say we move to 20. Lots of top 25 lost and many of those that won were not impressive. 

Thinking the same...maybe 21

[hightechbull]

Alabama could be 1-6 and the pollsters would still rank them #1.  "They played a tough schedule in the SEC"  would be their excuse.

The whole system is rigged.

[chapelbull]

11 hours ago, MikeG said:

Exactly.

The difference about the time is that you are basically spiking the ball to conserve as much time as you want because you have the ball.

Calling a spike play-- especially if the players are tired or confused-- is the EASIEST play to get everyone on the same page immediately. It saves time and lets you get your collective **** together when you run a play the next down. You have 3 more downs to use-- and this saves time.

You can spike the ball again if you need to -- sure-- after a pass that gets you closer or even a first down-- and then you have the play clock to decide and get your guys lined up for hat you want to do next. 28 seconds is NOTHING. And in the event of a penalty-- which did happen-- you are screwed. You almost never get a penalty when everyone hears "spike it spike it" or whatever the team knows the play as. It also gets them to move to the line as fast as possible if you have coached them correctly.

This, as someone said from the get go, is Football 101. It is a "no brainer" because it is OBVIOUS. You have seen this tons of times.

 

SIDENOTE:

One other thing I recently learned regarding spiking the football-- teams are not allowed to spike the ball when the play starts with less than 3 seconds on the clock. This is a new rule in the NCAA this year. They put it in because of not being able to ensure proper time keeping at all levels or something like that.

They should have been moving to the line fast as possible anyway.  It's only OBVIOUS and a no brainer because the guy jumped.  I've seen teams not spike the ball plenty of times in similar situations.  There was around 30 seconds on the clock when the guy was tackled.  Plenty of time to call a play especially when you are in FG range.  All you had to do was gain a few more yards and set up the kicker.  There was no need to rush and the players shouldn't be confused.   If you do spike and something goes wrong on the next play (loss of yards) you are scrambling on 3rd down to run a play or spike it to kick. They could have spiked it, but it wasn't a no brainer and not a good excuse for the guy to jump. 

You really want to question something?  Question the last play that should have been a quick out type of play to get the 5 yards back plus maybe a few more to give you a shot at a winning FG.  Instead they wasted 18 seconds on a scramble and pass well inside the field so the guy is tackled with 4 seconds left and the clock expires.  That was the mistake and they had time to talk about it and get set up.

[chapelbull]

13 hours ago, brybull1970 said:

Maybe I am not speaking your native language. Memphis struggles in the rain. That rain magnifies some of their weakness that you mentioned. They were clearly the better team before it began raining and they struggled once it began to pour. This is the same issue that occurred in Annapolis when they lost to Navy. To say they lost the game due to a single event means you weren’t watching the game where any number of other mistakes - some rain impacted (e.g. fumble deep in UCF territory when they were up 6) - contributed to them blowing a double digit lead. They didn’t lose because it rained, they lost because they didn’t handle the rain well once they had a big lead.

If you can’t understand that distinction then you should probably follow another sport.

I understand your distinction just fine.  It applies to 90% of football teams.  I also understand that they still should have won if they didn't blow it at the end when it wasn't pouring. I also understand that it wasn't pouring the entire second half.   I also understand that they blew a halftime lead to ucf last year when it wasn't pouring.

[MikeG]

1 hour ago, chapelbull said:

They should have been moving to the line fast as possible anyway.  It's only OBVIOUS and a no brainer because the guy jumped.  I've seen teams not spike the ball plenty of times in similar situations.  There was around 30 seconds on the clock when the guy was tackled.  Plenty of time to call a play especially when you are in FG range.  All you had to do was gain a few more yards and set up the kicker.  There was no need to rush and the players shouldn't be confused.   If you do spike and something goes wrong on the next play (loss of yards) you are scrambling on 3rd down to run a play or spike it to kick. They could have spiked it, but it wasn't a no brainer and not a good excuse for the guy to jump. 

You really want to question something?  Question the last play that should have been a quick out type of play to get the 5 yards back plus maybe a few more to give you a shot at a winning FG.  Instead they wasted 18 seconds on a scramble and pass well inside the field so the guy is tackled with 4 seconds left and the clock expires.  That was the mistake and they had time to talk about it and get set up.

The clock killing play is a no brainer in that all the players have to do is line up and not move- center hikes it, qb dumps it-- SIMPLE. If you call a play in a rushed situation-- they have to think, move, everything else. Now you yourself mentioned that the lineman was probably TIRED. Why force him and everyone else (who also might be tired or confused) to do another play immediately? Have him and the rest of the offense line up, snap the ball and spike it. Now you get the full play clock to prepare for a play where everyone is on the same page, more rested, and without any confusion or anxiousness whatsoever. This isn't about downs. You just got four and have time for maybe two decent plays to get you better FG position. Also-- when you take the  time to spike the ball-- you call the next two plays and remind the players what they need to be doing as far as the clock is concerned.

NONE of this would matter one bit if the stupid WR goes to get out of bounds instead of turning inward to the field for a handful of meaningless yards. Once again- coaching. He made it worse by strutting around like a fool after the play to boot.

Don't agree?-- fine-- agree to disagree. This is no more the linemans fault than anyone else on that team but especially the coaches who did not prepare them properly to run a two minute drill or communicate what to do when it mattered. I do not care if you've seen it done some other way-- and it worked. It is not an ideal way to handle the series of mistakes.

Mistake 1-- receiver doesn't get out of bounds to stop the clock (not just freeze it for the chains to move for the first down)

Mistake 2 - Not spiking the ball, taking far too long to put in a shotgun play that ends up making the entire team hustle to the line and try to perform with almost no time to get their brain set for the play-- boom - line man jumps/ 10 second penalty runoff and out of FG range.

Mistake 3 - On this we agree-- not running plays to the sideline to at least get back in potential FG range and can stop the clock.

Those coaches should be ashamed of how they blew that opportunity. It is completely on them