QB may hold back TE to block extra blitzers
If I don't check the box to allow the QB to hold back extra blockers I don't want to hold back extra blockers. I am suggesting they change this and make the option do exactly what it says. Not kind of what it says. Not sort of what it says. But exactly what it says. I hate this whole feature and if they don't want to fix it they should just remove it.
Here is an example. Down one 2nd and 7 on the opponent's 14 my BTE is held back for no good reason. The box wasn't checked. There was no blitz. There were no extra blitzers. There were just two hurries the entire half. Yet the BTE is held back. This led to a sack because the damn BTE didn't run his route so the QB held the ball forever. The QB should almost never be sacked on this play in this situation. As soon as I saw the BTE held back I knew something bad was about to happen.
http://glb2.warriorgeneral.com/game/replay/501338/2178238
I feel this feature may have cost me this game and it should never happened like that. This is not the first time this has happened but just another example.
I would just like this feature to work as described. "It has always sucked and we just live with it" just isn't good enough. It's not much better than losing a tight game due to a random false start in GLB1. I mean would anyone really be disappointed if it worked as described?
If I don't check the box to allow the QB to hold back extra blockers I don't want to hold back extra blockers. I am suggesting they change this and make the option do exactly what it says. Not kind of what it says. Not sort of what it says. But exactly what it says. I hate this whole feature and if they don't want to fix it they should just remove it.
Here is an example. Down one 2nd and 7 on the opponent's 14 my BTE is held back for no good reason. The box wasn't checked. There was no blitz. There were no extra blitzers. There were just two hurries the entire half. Yet the BTE is held back. This led to a sack because the damn BTE didn't run his route so the QB held the ball forever. The QB should almost never be sacked on this play in this situation. As soon as I saw the BTE held back I knew something bad was about to happen.
http://glb2.warriorgeneral.com/game/replay/501338/2178238
I feel this feature may have cost me this game and it should never happened like that. This is not the first time this has happened but just another example.
I would just like this feature to work as described. "It has always sucked and we just live with it" just isn't good enough. It's not much better than losing a tight game due to a random false start in GLB1. I mean would anyone really be disappointed if it worked as described?






























