AI regressions when switching from classic to civ2civ3 ruleset
Some AI problems come up more prominently with civ2civ3 ruleset than with classic ruleset. Some of those are serious enough to be consider blockers of releasing freeciv-3.0 with civ2civ3 as default ruleset. This ticket is for collecting those cases, and following the development.
The ideal solution for these problems would be making AI to behave, but since the problems typically are very hard to solve, in some cases we may need to adjust the civ2civ3 ruleset. If we can't make AI behavior acceptable for civ2civ3 as default ruleset even then, as last resort we have to revert back to classic ruleset as default ruleset.
#1 Updated by David Fernandez (bard) about 2 years ago
I'm interested to know the main AI regressions that you noticed with civ2civ3 rules, and possible suggestions to improve the AI behaviour by changing the ruleset.
I agree that civ2civ3 should not be the default rules if the AI is clearly inferior than with classic rules.
#2 Updated by Jacob Nevins about 2 years ago
I've got a S2_6 civ2civ3 autogame I ran recently; I intend to upload selected details to a new ticket for people to pick over.
One continuing theme is AI getting stuck on 100% tax and making no progress in science for thousands of years. (Admittedly I haven't run a classic-ruleset autogame to compare, I should do that.)
#4 Updated by David Fernandez (bard) about 2 years ago
I suspect that AI does not take into account food upkeep either.
In civ2civ3, if the population of a city is lower than the number of units supported by the city, the extra units have to pay upkeep of food. I thought this would limit the units built by the AIs, but they seem to continue building units even at starving cities that can not support new units.
I have also noticed that AI does not seem to take into account the penalties due to tired attack. In my latest games, the AI tend to attack my units in situations where the odds are clearly against the AI, but would be favourable to AI without the tired attack. I was waiting for confirmation before opening a new ticket.