Investigation of AI reassessment upon reload

[Ramboost]

At the forum in twcenter (http://www.twcenter.net/forums/index...c=27076&st=108) Pode wrote an interesting discovery:

"The AI will almost always, upon a reload, abandon a siege and run as far away as possible. Unless you interrupt it again with another load, however, it almost always returns and lays siege again the next turn."

Has any of you had the same experience? It could be a workaround for the bug to minimize the negative effects, allthough it will not eliminate it.

[chef4fun2]

I never had any issues with the orginally and the first patch on this sieging of cities bug. Now that I have put in the last patch this issue shows it ugly head. I think it is pretty simple: they fixed one issue and created this issue. Now they say that the AI has changed its mind and wants to move the resources some place else. I have news for them I did the save game I was Seleucid and two of my cities were being sieged by Egypt. After I restarted the game the Egyptian left my cities and came right back in the same move. Now did they change there mind and than said no go back to the city!!! I can't see Alexander doing that at the sieging of tyre.

[drone]

Last night I ran a test using v1.1 to see if this was introduced with v1.2. The no-expansion issue is just as prevalent (didn't try the protectorate issue, that was bugged in 1.1 anyway). I played 20 turns for each, Med/Med, as the Britons (unlocked, not mod), FOG_OF_WAR:FALSE in preferences.txt.

With no saving/loading, the factions expanded normally, eating up the rebel provinces and fighting it out with each other.

With a save and load each turn, not much happened. Diplomats and stacks moved around, rebel stacks got pounded, but only one province changed hands, I think (Brutii took Thermon, no siege, just walked right in). It seemed like after a load, the AI would do whatever it could short-term within it's interests (mainly crushing rebels). I don't think I saw any sieges lifted, mainly because the AI never got around to sieging cities in the first place. This would probably be present if I waited 3-4 turns between saves/loads.

I have screenshots at each turn for both test cases, the end result is pretty much the same as Bromley's. These results lead me to think that the reassessment is an integral part of the game, just as the .com post said, not a new "feature".

On the FoW issue, it would be interesting if CA tries to use Heisenberg's Uncertainty Principle as an excuse.