AI blunders you would like to see fixed

[Chaingun]

Been working a lot on attrition lately since that has been an obvious problem with the AI. Maybe it will be better in the near future.

Might revisit AI DOWs for the reason you mention, thank you for making me aware of this problem.

 

[Chaingun]

@Beagá Also, if you have any save games showcasing ridiculous AI attrition you would like me to inspect, feel free to upload. I need to verify my new code works.

 

[Chaingun]

Sure



I´m afraid I didn´t get pic of 21k Mameluke stack on Cyprus however :/

On topic of CW, Lithuania and Moldavia are strangely passive regarding creation of claims on Crimea, Muscowy etc, something they did in the past... is there some option I must use in game to make them do it?

Also... dat Austria. Please do something about it too

Thank you. Yeah already trying to deal with the other things you mentioned.

Contesting moronic PU's

like this.

Might have a look if there's time, guess it's "not that tweaked" due to succession wars not being that common.

The excessive attrition is a tricky one because if the AI started spliting up their forces too much it would be easy just to stackwipe small armies.

Best fix would be for them to put just as many men as necessary on the siege and then leave the rest in an adjacent occupied province.

Recently implemented this, but it should be noted that AI also has to deal with cases of allies piling up along with them that are more difficult.

If/than statement:
If attrition = greater than monthly manpower increase, than move troops.

With all the Ai bonuses this should do the trick.

Or you could program it a bit further by having them account for nearby enemy armies.

AI attrition logic is a few thousand lines of code, AI movement logic is tens of thousands. Try to explain in human terms instead because there is no simple code that works.