So if your QB makes a hot read on a blitz, I doubt the best course of action was to take a sack. Is this supposed to be happening? Hit me 2-3 times in this game alone.

https://ncaa-football.myfootballnow.com/gamecenter/view/268#49932

Oh, you have an excellent point. That sack took forever to happen.

My initial thought before clicking on it was well the QB was swarmed fast....

What's worse is taking a sack on a play where the WR5 is always open when the defense runs a default call against the play.

I still think the worst part was the SS. He read was to cover man. Instead he took a nap. I am pretty sure something was put in the game (recently )to prevent that wide open deep throw(though it does happen sometimes ) . Only cause there is a defensive coverage glitch in the first place .

I bet the hot read was overridden due to the nature of both the other things stated. That offensive play was money a bit ago....then suddenly you get sacked or a throw would be forced to the TE 1 or 2. The coverage defense has been broke vs. That offensive play for over 2 real years. This is the result of a hot read on a previously glitched set of plays.

I think JDB's "fix" was that the QB no longer looks to the FB2 on the play during his read progression because I still haven't seen that player covered. (Not that I use that offensive play and I use rules to make sure that player is covered for sure against teams that do use it.)

Again......Somebody call a Waaaaaaambulance
So basically, you are saying if you cannot get your entitled way, it is wrong because you can't bot a win.

Huh? It is broke....Look at the SS . ..his assignment and what he actually did. Nothing has ever matched up. Now or before the hot read. Like seth said routinely the FB2 is left open. So was the FB 1 on this set of play matchups.

I have still seen qbs target the FB2. It is less often,