@beelee said:

I will ping @panther for you, as he is a rules heavyweight.

I am happy to assist in case anything rules-related might be unclear.

Is this what should happen?
Components of this problem

rulesAttachment has placementCapturedTerritory" value="true"
This allows for the placement of units in the same turn as they were captured.

Order of delegates in xml speak
A&A style Purchase before Combat
Purchase> Combat move>Combat> Non-Combar move> Place> End Turn
or
New style Purchase after Combat
Combat move>Combat> Non-Combat move> Purchase> Place> End Turn

For Purchase before Combat
The AI tries to purchase what it thinks it needs based on its current TT and then Places them.
If PlacementCapturedTerritory=true then it should re-evaluate its Purchases/Place based on its new TT gains, yes? (As the gains might be better, closer to the enemy etc)

Purchase after Combat
If PlacementCapturedTerritory=true or false
The logic is simpler, the AI purchases what it can place, yes?

In the above mix, if the AI have been given units/factories from isAI/xml it should test for these first and not Purchase them,

Is the above what should happen?

@beelee

To sum up what WC is pointing out here - basically the AI is stupid here in that it tries to purchase units for territories it can't place in. And it is also unable to place unplaced factories because it tries to place them in territories with factories.

This needs to be fixed on the engine level. Two fixes are needed:

When making purchases, the AI simulates it turn first and then uses that information to make its purchase. However, it then correctly needs to identify that it cannot place in conquered territories because right now it thinks it can.

When the AI tries to place unplaced factories, it needs to use a different set of territories than those for regular units.

@wc_sumpton said:

So, the AI can purchase to place factories, but can still lose them because it can always try to purchase for captured territories even if they can't be placed there.

Not sure what all this means. Does new code need to be written for the AI not to do this ? Or does a new map property need to be added to the xml so one can turn it off depending on what game they're playing ?

I'm not real clear on all the different rulesets, as it's been so long since I've played anything other than G 40.

Anyway, I won't be of any help here but Good Luck for getting it corrected I will ping @panther for you, as he is a rules heavyweight.