On 4th and long, 26.5 yd line, we had an inside run take the place of a punt:
http://goallineblitz.com/game/replay.pl?game_id=180758&pbp_id=1572058
The AI tester clearly gives a punt result from the exact setting and score situation. I have been using the offensive AI for two seasons and never had a problem with this. If someone wants to check, I have not updated our AI since the game.
Why I think it went wrong:
-We had FG range manually set to 30 yards, due to an unreliable slow-build kicker
-I had plays set up for us going for it on most 4th downs within the 25, outside FG range, with the knowledge a punt in there is useless. However, this occurred on the 26.5 yd line.
-Perhaps there is some sort of conflict with punting so close to the endzone, with the auto FG range overridden?
-The other thing of note is that we were within the 25 yd line 2 plays earlier, and got TFL'd outside of it. Don't see how this would cause an issue.
http://goallineblitz.com/game/replay.pl?game_id=180758&pbp_id=1572058
The AI tester clearly gives a punt result from the exact setting and score situation. I have been using the offensive AI for two seasons and never had a problem with this. If someone wants to check, I have not updated our AI since the game.
Why I think it went wrong:
-We had FG range manually set to 30 yards, due to an unreliable slow-build kicker
-I had plays set up for us going for it on most 4th downs within the 25, outside FG range, with the knowledge a punt in there is useless. However, this occurred on the 26.5 yd line.
-Perhaps there is some sort of conflict with punting so close to the endzone, with the auto FG range overridden?
-The other thing of note is that we were within the 25 yd line 2 plays earlier, and got TFL'd outside of it. Don't see how this would cause an issue.
Last edited Sep 23, 2008 06:51:28






























