@black-order I'd probably recommend putting the huge map on pause and create a much smaller map either version of avatar or something else. That way you can learn the map making process end to end and many of the gotchas that can be very difficult to change once you get to a certain point in the map making process. That way you can make sure you do the giant Avatar map the right way and not realize half way through that you need a bunch of rework that would be incredibly painful at that huge scale.
@roiex Ok, then I've closed my pull example in here:
Cernelius created this issue in triplea-maps/classic_variations
@redrum I think updating the pos2 makes sense for now since @Mahks says he will be the caretaker of XOB. He can copy them over to XOB until others can do it. The only issue would be he has to find the changes in the xml. Hmm, are you keeping an update log updated for POS2?
@elreigh Yes, without seeing the actual XML this is just a guess... but by what you described.... the game is trying to create and then subsequently render the image for an "Allied" Arcadia Motor Pool. The game is attempting to change the "Arcadia Motor Pool" into a unit of the Ally, but since the unit is designed as a national specific unit... it is trying to capture the unit as it is defined.
This is not really a bug. I think it is just how you have designed the units. I have come across the same thing while designing.
The other thing that is causing the conflict is that as Allies the game does not view the changing of the territory when the Capital is liberated as a "Capture" strictly speaking.
Would really have to see your XML to figure it out.
@mahks Here is a pretty good list of things it doesn't handle now: https://forums.triplea-game.org/topic/105/ai-development-discussion-and-feedback
The further from traditional A&A features you use generally the AI will perform more poorly as most of them it doesn't understand.
@theredbaron Yep, that's the general approach I like to take as otherwise I end up spending time making changes that might never get used But it should be relatively easy to replace the existing logic with something a bit less random.
Best guess 'Sea Zone' ownership. Water territories do not have ownership, give 'SZ Sea of Japan' an 'originalOwner' option in its 'territoryAttachment' and use 'alliedPresenceTerritories' in the trigger.
Also check the property:
<property name="Use Triggers" value="true" editable="false">
Hope this helps