Originally posted by TrevJo
Originally posted by cwisler
Cincinnati Terror was set to run it 100%. I noticed 1 play where that same exact thing was noticeable: http://test.goallineblitz.com/game/replay.pl?game_id=1401&pbp_id=304553
To me, it looks more like a speed/agility issue and not a bug. The rest of the game, the FB seemed to make the blocks every time.
Input is welcome. 
It's a bug. It's triggered by a speed/agility issue, but it's a bug. There is no way in hell the player should be doing that.I can see how one can interpret it as a bug. If we could find more instances of this with a FB that has higher speed, agility, and vision -- that'd be great. The more examples I have, the better of an idea I have on what to test to see how the blocking pathing
could be fixed to not go in reverse. I think a lot of stuff at Pee Wee looks sloppy to begin with because of how under-developed the players are.
I don't know how the blocking is coded, so I don't know how major a change like that would be. The play looks horrible, but I personally think the only effect it would have on the play is if the HB broke the first tackle.
This is how I see the play break down:
FB begins vision check for 'top threat' to lead block. By the time he passes that vision check, his lead block is out of reach. Therefore his pathing is towards his own endzone because that would be the ideal 'block' intersection. The FB didn't have enough speed and agility to block ahead of the HB because he couldn't meet up with the SS any time before that intersection spot behind the HB. The SS could have continued moving left to avoid the FB's block.
tl;dr versionCould be considered a bug. Would be nice to have blocking paths fixed to
not go behind the ball carrier. I'm unsure how much of an effect it would have on other blocking logic.