When CPU teams spike the ball the down and distance gets set to 2nd and 10, and they often gain yardage, very dangerous.

Must be a display/play by play issue either replacing the previous play, or overwriting the play so that you don't see the results. In the code the spike play works like a timeout, so there is no yardage applied, only a pass attempt and down change.

huh, OK. well several times I've seen the CPU spike the ball on 2nd down and then it will be 2nd down again, but and 10, and they will have moved forward. totally skipping first and/or third. So maybe the AI is calling a play for me too?

No play is called, it's just like a timeout and happens instantly. Maybe what ever play is getting them to 1st and 10 is getting lost in the PBP/replay.

Alrighty. must have mis-read it. Sorry for crying wolf.

No, it's good info, and something I can look at to fix, but I don't think it's affecting stats.