CPU 4th down AI is broken

[deathsai]

This happens way too often, especially at the end of the game or the half. Example: With 1:30 left in the game, as the Jags I stop the Jets at the goal line. It is now 4th and goal, score is 14 Jags - 10 Jets.

The Jets decide to kick a field goal instead of going for it.

This is just plain stupid, and I don't know how EA missed it.

Happens a lot at the end of the 2nd half with only around a minute or less left, where the AI would rather punt it than go for it even if they're halfway down the field.

[inkcil]

Quote: Originally Posted by deathsai

This happens way too often, especially at the end of the game or the half. Example: With 1:30 left in the game, as the Jags I stop the Jets at the goal line. It is now 4th and goal, score is 14 Jags - 10 Jets. The Jets decide to kick a field goal instead of going for it. This is just plain stupid, and I don't know how EA missed it. Happens a lot at the end of the 2nd half with only around a minute or less left, where the AI would rather punt it than go for it even if they're halfway down the field.

how many to did jets have?

[deathsai]

All 3, but kicking a FG with only 1:30 left is ridiculous. And then they tried for an onside kick. All the offense needs to get in that situation is a single first down. There isn't a single NFL coach who wouldn't try for the TD for the win on 4th down with only 5 yards to go.

[jmurphy31]

I have this happen a few times. Im not sure how play calling can't be correct by now. I also don't think its limited just to this. Clock management and playcalling in certain situations have been one of the few low points from the AI this year.

[deathsai]

Yeah, really boggles me. I don't recall this being an issue last year.

CPU is still calling all-out blitzes on 3rd down leaving maybe 2 DBs to cover the outside and nobody in the middle.