save game bug still there?

[gardibolt]

The AI will sometimes reevaluate and break off a siege in 1.5/1.6; if that happened to occur in a turn after you reload, that would look like the save/load bug. Is it happening consistently?

[Nebuchadnezzar]

I have not seen the AI break a siege in 1.5/1.6 but I believe this can happen if a threat occurs elsewhere, particularly its capital.

Save/Load definately alters diplomacy. After reloading the AI is more likely to refuse offers which it would have accepted without the reload.

AI armies within enemy territory still seem to withdraw back to within their territory after reloading. The exception seems to be when the AI is absolutely determined to beseige you.

The AI seems to not want to repair or retrain after reloading. I'm not sure if building and recruiting is affected.

[Kaidonni]

This is the problem with 1.3/1.4 too - the AI is more likely to reject an offer if you reload than if you didn't. In my Pontus 1.3 H/H campaign, I've tried to play more than one turn if I was to use diplomacy...and have even loaded the previous turn if I screwed something up totally and hadn't saved since I had done the important diplomacy.

[Slaists]

well, probably gardibolt has got a point here. i was playing the game basically a couple turns per evening. for a few evenings, whenever i loaded the game, the horde (vandals) would break off their seige of one of my border forts just to return with a new seige in the next turn... but, i guess, it was due to the randome reevaluation since i did not notice the AI breaking off their seiges of my cities later in the game. apologies for the false alarm.

The AI will sometimes reevaluate and break off a siege in 1.5/1.6; if that happened to occur in a turn after you reload, that would look like the save/load bug. Is it happening consistently?