In all seriousness, here's what I think is going on. Our blitz, and the one linked about for 5-man, are what I call "overload" blitzes, meaning you send more guys at the line or the segment of the line than there are blockers. The blockers commit to one guy, and someone is left unblocked. That may not seem apparent, because you think, "Hey, there's a RE and ROLB/FS, and there's a LT and LG, seems fair to me." But what is actually happening is the RE and blitzer are "overloading" the tackle 2 v 1, and the guard doesn't come into any of the pre-snap stuff. I am guessing that there is some sort of pre-snap determination for lineman where they "decide" who they are responsible for blocking based on proximity (you don't see lineman taking off after the CB or reacting cut off a potential CB blitz instead of going for the guy in front of them), and that the guard and tackle both decide that both the end and the blitzer "belong" to the tackle.
The key thing here is that the blitzer is "pathing" through the tackle, not the guard. The guard is not "watching" the blitzer, nor, and I think this is important, is the blitzer choosing his path based on the guard. They aren't "paired", if you will. The blitzer will choose his path based on how to beat the tackle, not the guard; but since the tackle gets pulled by the end, the best path for the blitzer is a straight line right through where the tackle was.
I can see how you think this is a bug if you're assuming the guard and blitzer are "paired"- if a blocker just stood there and let "his guy" run past him, that would he a "bug". Thing is though, the blitzer is not the guard's guy, he's the tackle's. Unfortunately, the tackle has to worry about the RE too here, and chooses the RE as the more immediate threat. The guard has to go through the normal rolls to say, "this blitzer got past the person that is supposed to take him and now he is the most immediate threat, I better engage him" but that comes too late most of the time. If the blitzer started closer to the guard than the tackle, I have a pretty good suspicion that the guard would behave exactly as you guys are demanding he react, sliding in front of the blitzer to engage him.
So yeah, this isn't a "bug", it's working as intended imo. This might be worthy of a suggestions thread to improve blocking assignments or something, but the guard isn't "bugged" or "glitching" or anything. Also, that 5 WR blitz is way, way closer to "unfair" than what we do (although neither is) but I bet you could torch it with quick slants.
The key thing here is that the blitzer is "pathing" through the tackle, not the guard. The guard is not "watching" the blitzer, nor, and I think this is important, is the blitzer choosing his path based on the guard. They aren't "paired", if you will. The blitzer will choose his path based on how to beat the tackle, not the guard; but since the tackle gets pulled by the end, the best path for the blitzer is a straight line right through where the tackle was.
I can see how you think this is a bug if you're assuming the guard and blitzer are "paired"- if a blocker just stood there and let "his guy" run past him, that would he a "bug". Thing is though, the blitzer is not the guard's guy, he's the tackle's. Unfortunately, the tackle has to worry about the RE too here, and chooses the RE as the more immediate threat. The guard has to go through the normal rolls to say, "this blitzer got past the person that is supposed to take him and now he is the most immediate threat, I better engage him" but that comes too late most of the time. If the blitzer started closer to the guard than the tackle, I have a pretty good suspicion that the guard would behave exactly as you guys are demanding he react, sliding in front of the blitzer to engage him.
So yeah, this isn't a "bug", it's working as intended imo. This might be worthy of a suggestions thread to improve blocking assignments or something, but the guard isn't "bugged" or "glitching" or anything. Also, that 5 WR blitz is way, way closer to "unfair" than what we do (although neither is) but I bet you could torch it with quick slants.
Edited by Track6Track7 on Sep 3, 2009 07:45:20






























