Is is possible to make active combatans unselectable and default hardAI?

TripleA Turn Summary: Finland round 19 TripleA Turn Summary for game: Total World War: December 1941 3.0, version: 3.0.0.6 Game History Round: 19 Reconnaissance Missions - Finland Finland collect 0 PUs; end with 10 PUs Reinforcing - DanubeAxis DanubeAxis collect 0 PUs; end with 13 PUs Counter Intelligence Operations - VichyFrance VichyFrance collect 0 PUs; end with 15 PUs Research Technology - Germany Germany spend 0 on tech rolls Germany roll 3,2,12,9,10,6,12,4,12 and gets 3 hits Germany removing all Technology Tokens after successful research. Germany discover ImprovedMechanization Combat Move - Germany Trigger germanAL4: Setting transportCapacity to 7 for unitAttachment attached to Train Trigger germanAirtraninfra1: Setting isInfrastructure to false for unitAttachment attached to germanAirTransport Trigger germanAirtraninfra1: Setting attack to 1 for unitAttachment attached to germanAirTransport Trigger germanAirtraninfra1: Setting destroyedWhenCapturedBy cleared for unitAttachment attached to germanAirTransport Trigger germanL4: Setting movement to 6 for unitAttachment attached to Train Trigger germanL2: Setting movement to 3 for unitAttachment attached to Truck Trigger germanHvyTank1: Setting isLandTransportable to false for unitAttachment attached to germanHeavyTank Trigger germanTank1: Setting isLandTransportable to false for unitAttachment attached to germanTank Trigger germanMecht3: Setting isLandTransportable to false for unitAttachment attached to germanMech.Infantry Trigger germanMecht4: Setting isLandTransportable to true for unitAttachment attached to germanMech.Infantry Trigger germanHvyTank2: Setting isLandTransportable to true for unitAttachment attached to germanHeavyTank Trigger germanTank2: Setting isLandTransportable to true for unitAttachment attached to germanTank 1 germanInfantry moved from Southern Ukraine to Eastern Ukraine Germany take Eastern Ukraine from Russia 3 germanStrategicBombers moved from Hungary Slovakia to Southern Caucasus Combat - Germany Strategic bombing raid in Southern Caucasus Bombing raid in Southern Caucasus rolls: 3,4,0 and causes: 6 damage to unit: Rail Bombing raid in Southern Caucasus causes 6 damage total. 1 Rail owned by the Russia lost in Southern Caucasus Non Combat Move - Germany Trigger germanIL2: Setting isAirTransportable to true for unitAttachment attached to germanCombatEngineer Trigger germanMecht1: Setting isLandTransport to true for unitAttachment attached to germanMech.Infantry Trigger germanAL6: Setting isAirTransportable to true for unitAttachment attached to germanInfantry Trigger germanAL6: Setting isAirTransportable to true for unitAttachment attached to germanMarine Trigger IncomeRegulationVichy1: Setting switch to true for conditionAttachmentYesVichy attached to VichyFrance Trigger germanAL5: Setting transportCapacity to 5 for unitAttachment attached to Train Trigger germanAirtraninfra2: Setting isInfrastructure to true for unitAttachment attached to germanAirTransport Trigger germanAirtraninfra2: Setting attack to 0 for unitAttachment attached to germanAirTransport Trigger germanAirtraninfra2: Setting destroyedWhenCapturedBy to FROM:Germany for unitAttachment attached to germanAirTransport Trigger germanL5: Setting movement to 5 for unitAttachment attached to Train Trigger germanL3: Setting movement to 2 for unitAttachment attached to Truck Trigger germanIL3: Setting isAirTransportable to false for unitAttachment attached to germanCombatEngineer Trigger germanAL7: Setting isAirTransportable to false for unitAttachment attached to germanInfantry Trigger germanAL7: Setting isAirTransportable to false for unitAttachment attached to germanMarine Trigger germanMecht2: Setting isLandTransport to false for unitAttachment attached to germanMech.Infantry Trigger germanAP2: Germany has 1 Material placed in Berlin Trigger germanProd: Germany has 1 Material placed in Berlin 3 germanStrategicBombers moved from Southern Caucasus to Southern Ukraine 1 germanAntiAirGun and 1 germanMech.Infantry moved from Orel Kursk to Kharkov 2 Trucks moved from Orel Kursk to Belorussia 2 Trucks, 1 germanArtillery and 1 germanCombatEngineer moved from Belorussia to Kharkov 1 germanInfantry moved from Western Ukraine to Kharkov 1 germanInfantry moved from Romania to Bessarabia 1 germanAntiTankGun and 1 germanMech.Infantry moved from Hungary Slovakia to Western Ukraine 1 germanArtillery, 1 germanMech.Infantry and 1 germanTank moved from Eastern Poland to Kharkov 1 germanAirTransport and 2 germanInfantrys moved from Eastern Poland to Kharkov 1 germanAirTransport moved from Kharkov to Poland 1 germanAirTransport and 2 germanInfantrys moved from Poland to Kharkov 1 germanAirTransport moved from Kharkov to Eastern Poland 1 germanArtillery moved from Eastern Poland to Western Ukraine 1 germanInfantry moved from Poland to Eastern Poland 1 germanSubmarine moved from 9 Sea Zone to 4 Sea Zone 1 germanSubmarine moved from 10 Sea Zone to 7 Sea Zone 1 germanSubmarine moved from 24 Sea Zone to 6 Sea Zone 1 germanAlpineInfantry, 2 germanArtillerys, 1 germanCombatEngineer, 6 germanInfantrys and 3 germanParatroopers moved from Western Sahara to Morrocco 1 germanTacticalBomber moved from Northern France to Romania 2 germanTacticalBombers moved from Low Countries to Romania 4 germanFighters moved from Western France to Bessarabia 1 germanArtillery and 3 germanInfantrys moved from Low Countries to Northern France 3 germanInfantrys moved from Northern France to Western France 4 germanInfantrys moved from Northern Germany to 25 Sea Zone 2 germanBattleships, 6 germanCruisers, 11 germanDestroyers, 4 germanInfantrys and 13 germanTransports moved from 25 Sea Zone to 23 Sea Zone 4 germanInfantrys moved from 23 Sea Zone to Northern France 4 germanInfantrys moved from Western France to Northern Spain 1 germanInfantry moved from Bulgaria to Romania 1 germanArtillery and 1 germanMech.Infantry moved from Eastern Germany to Eastern Poland 1 Truck moved from Orel Kursk to Eastern Poland 1 Truck moved from Orel Kursk to Romania 2 germanMech.Infantrys moved from Orel Kursk to Western Ukraine 3 germanMech.Infantrys moved from Orel Kursk to Kharkov 1 germanInfantry moved from Orel Kursk to Belorussia 1 germanInfantry moved from Leningrad to Lativa Estonia 11 germanAntiTankGuns, 20 germanArtillerys, 2 germanCombatEngineers, 36 germanInfantrys, 2 germanParatroopers and 14 germanTanks moved from Orel Kursk to Kharkov 1 germanFighter moved from Southern Germany to Morrocco 4 germanNavalFighters moved from Western France to Northern France 1 germanNavalFighter moved from Southern Germany to Northern France 4 germanFighters moved from Low Countries to Western France 4 germanFighters moved from Low Countries to Western France 1 Train moved from Eastern France to Berlin 1 Material, 1 Train and 1 germanCombatEngineer moved from Berlin to Poland 1 Train moved from Poland to Berlin 1 germanAntiTankGun and 2 germanInfantrys moved from Finland to Eastern Finland 1 germanAlpineInfantry, 3 germanArtillerys, 4 germanCombatEngineers and 10 germanInfantrys moved from Leningrad to Eastern Finland 2 germanTransports moved from 29 Sea Zone to 27 Sea Zone 2 germanInfantrys moved from Vichy France to Western France 2 germanMech.Infantrys and 2 germanTanks moved from Morrocco to Algeria 1 germanArtillery moved from Algeria to Morrocco 1 Material and 1 Truck moved from Algeria to Morrocco 1 Truck moved from Morrocco to Algeria 1 Truck moved from Morrocco to Algeria 2 germanInfantrys moved from Morrocco to Algeria 1 germanInfantry moved from Morrocco to Algeria 1 Train and 1 germanAntiAirGun moved from Vichy France to Northern Spain 1 Train moved from Northern Spain to Vichy France 1 germanFighter moved from Northern France to Northern Spain 3 germanInfantrys moved from Western France to Northern Spain 1 Train moved from Paris to Low Countries 1 Train and 2 germanAntiAirGuns moved from Low Countries to Northern Spain 1 Train moved from Northern Spain to Vichy France 2 germanInfantrys moved from Northern France to Western France Purchase Units - Germany Trigger germanAdvD: buygermanHeavyDestroyer added to germanProduction Germany buy 1 germanAntiAirGun, 3 germanArtillerys, 1 germanCruiser, 1 germanHull, 5 germanInfantrys, 1 germanSubmarine and 1 germanTacticalBomber; Remaining resources: 0 PUs; 0 techTokens; Place Units - Germany 1 germanCruiser placed in 23 Sea Zone 2 germanArtillerys placed in Low Countries Germany undo move 2. 1 germanAntiAirGun and 1 germanArtillery placed in Low Countries 1 germanHull placed in 27 Sea Zone 1 germanSubmarine placed in 22 Sea Zone 2 germanInfantrys placed in Poland 3 germanInfantrys placed in Northern Germany 2 germanArtillerys and 1 germanTacticalBomber placed in Eastern Germany Activate Technology - Germany Germany activating ImprovedMechanization Trigger germanImpMech: Setting defense to 4 for unitAttachment attached to germanMech.Infantry Trigger germanImpMech: Setting receivesAbilityWhenWith to canBlitz:germanTank for unitAttachment attached to germanMech.Infantry Turn Complete - Germany Germany collect 69 PUs; end with 69 PUs Trigger germanAP1: Germany met a national objective for an additional 3 PUs; end with 72 PUs Trigger germanIP: Germany met a national objective for an additional 3 PUs; end with 75 PUs Units generate 9 techTokens; Germany end with 9 techTokens Units Change Ownership Some Units in Algeria change ownership: 1 germanCombatEngineer Some Units in Eastern Finland change ownership: 4 germanCombatEngineers Some Units in Morrocco change ownership: 1 Material and 1 germanCombatEngineer Some Units in Vichy France change ownership: 1 Material and 1 germanCombatEngineer Purchase Units - VichyFrance Trigger VichyMaterial: 1 Material gained by PlayerID named:VichyFrance VichyFrance buy 1 germanEntrenchment, 1 germanFighter and 1 germanInfantry; Remaining resources: 0 PUs; Place Units - VichyFrance Units in Morrocco being upgraded or consumed: 1 Material 1 germanEntrenchment placed in Morrocco 1 Material, 1 germanFighter and 1 germanInfantry placed in Vichy France Turn Complete - VichyFrance VichyFrance collect 12 PUs; end with 12 PUs Objective Algeria: VichyFrance met a national objective for an additional -2 PUs; end with 10 PUs Objective Morrocco: VichyFrance met a national objective for an additional -2 PUs; end with 8 PUs Units Change Ownership Some Units in Algeria change ownership: 1 germanCombatEngineer Some Units in Morrocco change ownership: 1 germanCombatEngineer Some Units in Vichy France change ownership: 2 Materials, 1 germanCombatEngineer, 1 germanFighter and 1 germanInfantry Purchase Units - DanubeAxis DanubeAxis buy 2 germanInfantrys and 1 germanTank; Remaining resources: 1 PUs; Place Units - DanubeAxis 2 germanInfantrys placed in Romania 1 germanTank placed in Hungary Slovakia Turn Complete - DanubeAxis DanubeAxis collect 12 PUs; end with 13 PUs Units Change Ownership Some Units in Hungary Slovakia change ownership: 1 germanTank Some Units in Romania change ownership: 2 germanInfantrys Purchase Units - Finland Finland buy 1 germanArtillery and 2 germanInfantrys; Remaining resources: 0 PUs; Place Units - Finland 1 germanArtillery and 2 germanInfantrys placed in Finland Turn Complete - Finland Finland collect 10 PUs; end with 10 PUs Units Change Ownership Some Units in Eastern Finland change ownership: 4 germanCombatEngineers Some Units in Finland change ownership: 1 germanArtillery and 2 germanInfantrys Combat Hit Differential Summary : Savegame

@Jason-Drake From PoS2: isSub values: allows the unit to roll dice before other units and submerge or retreat from battle even on defense this is a shortcut option that sets the below 6 unit options based on the global sub properties specifically: sets canEvade and isFirstStrike to true sets canNotTarget to all air units sets canNotBeTargetedBy to all air unit types if "Air Attack Sub Restricted" sets canBeMovedThroughEnemies to true if "Ignore Sub In Movement" sets canMoveThroughEnemies to true if "Submersible Subs" canEvade values: whether the unit can submerge or escape battle isFirstStrike values: whether to roll dice and take casualties before regular units canNotTarget values: colon delimited list of units that this unit can't target in battles, ex. subs not being able to target air units canNotBeTargetedBy values: colon delimited list of units that can't target this unit, ex. air units not being able to target subs canMoveThroughEnemies values: whether unit is unblockable and treats hostile territories as friendly canBeMovedThroughByEnemies values: whether enemies can move through territories if only these types of units are present (would also need blitz for enemy land territories) Hope this helps. Cheers...

TripleA Turn Summary: ANZAC round 5 TripleA Turn Summary for game: World War II Pacific 1940 Original, version: 2.7 Game History Round: 5 Purchase Units - ANZAC ANZAC buy 1 destroyer and 1 fighter; Remaining resources: 0 PUs; Combat Move - ANZAC 1 infantry moved from Philippines to 35 Sea Zone 1 infantry moved from Philippines to 35 Sea Zone 1 infantry moved from Philippines to 35 Sea Zone 1 artillery moved from Philippines to 35 Sea Zone 2 infantry and 1 transport moved from 35 Sea Zone to 36 Sea Zone 1 artillery, 1 infantry and 1 transport moved from 35 Sea Zone to 36 Sea Zone 1 infantry moved from 36 Sea Zone to French Indo China 1 artillery moved from 36 Sea Zone to French Indo China 1 infantry moved from 36 Sea Zone to French Indo China 1 infantry moved from 36 Sea Zone to French Indo China 1 submarine moved from 35 Sea Zone to 43 Sea Zone Combat - ANZAC Battle in French Indo China ANZAC attack with 1 artillery and 3 infantry Japanese defend with 1 artillery and 1 mech_infantry ANZAC roll dice for 1 artillery and 3 infantry in French Indo China, round 2 : 0/4 hits, 1.00 expected hits Japanese roll dice for 1 artillery and 1 mech_infantry in French Indo China, round 2 : 0/2 hits, 0.67 expected hits ANZAC roll dice for 1 artillery and 3 infantry in French Indo China, round 3 : 0/4 hits, 1.00 expected hits Japanese roll dice for 1 artillery and 1 mech_infantry in French Indo China, round 3 : 0/2 hits, 0.67 expected hits ANZAC roll dice for 1 artillery and 3 infantry in French Indo China, round 4 : 1/4 hits, 1.00 expected hits Japanese roll dice for 1 artillery and 1 mech_infantry in French Indo China, round 4 : 0/2 hits, 0.67 expected hits 1 mech_infantry owned by the Japanese lost in French Indo China ANZAC roll dice for 1 artillery and 3 infantry in French Indo China, round 5 : 0/4 hits, 1.00 expected hits Japanese roll dice for 1 artillery in French Indo China, round 5 : 0/1 hits, 0.33 expected hits ANZAC roll dice for 1 artillery and 3 infantry in French Indo China, round 6 : 1/4 hits, 1.00 expected hits Japanese roll dice for 1 artillery in French Indo China, round 6 : 0/1 hits, 0.33 expected hits 1 artillery owned by the Japanese lost in French Indo China ANZAC win, taking French Indo China from Japanese with 1 artillery and 3 infantry remaining. Battle score for attacker is 8 Casualties for Japanese: 1 artillery and 1 mech_infantry Non Combat Move - ANZAC 1 destroyer moved from 54 Sea Zone to 35 Sea Zone 1 infantry moved from New South Wales to Queensland 1 fighter moved from Queensland to Philippines Place Units - ANZAC 1 destroyer and 1 fighter placed in 62 Sea Zone Turn Complete - ANZAC ANZAC collect 15 PUs; end with 15 PUs Objective ANZAC1 Control Strategic Islands: ANZAC met a national objective for an additional 5 PUs; end with 20 PUs Combat Hit Differential Summary : ANZAC : -3.00 Japanese : -2.67 Savegame

@Schulz The game logic isn't really designed to handle that. Basically the way the game currently works is that there's one state of the game (the savegame so to speak) and all clients just display this one state directly, a similar problem to simultaneous movement. The code assumes to know everything and the battles and the AI operate on that global knowledge. We'd not only have to hide certain territories, but change all code that shows the live actions of other players too. That's a lot of work, especially when we're only doing this in our free time. There are just some other things like fixing the bugs that are semi-automatically reported every day that have just higher priority.

@RogerCooper Are you saying that you don't have a '<relationshipInitialize>' section? It relationship are not initialize then there is nothing to set. That is why the trigger is falling. I have tried to set a tank unit to transport infantry, but if I didn't set "isLandTransport" then the trigger would fire but nothing would happen. But if I set "isLandTransport" to false then the trigger would change it to true. Hope this is helpful. Cheers...

@Zaroph First question is 'TrollTribes' a player? If so are you trying to check to see if 'TrollTribes' is being controlled by the AI, as selected on the chose player screen? If so lets try: <!-- TrollTribes Human Check Conditions --> <attachment name="conditionAttachmentTrollTribesAIPlayer" attachTo="TrollTribes" javaClass="games.strategy.triplea.attachments.RulesAttachment" type="player"> <option name="switch" value="true"/> </attachment> <!-- An invert of the previous condition --> <attachment name="conditionAttachmentTrollTribesHumanPlayer" attachTo="TrollTribes" javaClass="games.strategy.triplea.attachments.RulesAttachment" type="player"> <option name="conditions" value="conditionAttachmentTrollTribesAIPlayer"/> <option name="invert" value="true"/> </attachment> <!-- TrollTribes Human Player Trigger --> <attachment name="triggerAttachmentTrollTribesIsHuman" attachTo="TrollTribes" javaClass="games.strategy.triplea.attachments.TriggerAttachment" type="player"> <!-- This will never happen because 1 will always be true and the other false --> <option name="conditions" value="conditionAttachmentTrollTribesHumanPlayer:conditionAttachmentTrollTribesAIPlayer"/> <option name="playerAttachmentName" value="RulesAttachment" count="conditionAttachmentTrollTribesAIPlayer"/> <option name="playerProperty" value="switch" count="false"/> <option name="when" value="after:americanUserActions"/> <option name="uses" value="1"/> </attachment> <!-- TrollTribes User Action Is Human Check --> <attachment name="userActionAttachmentTrollTribesIsHuman" attachTo="TrollTribes" javaClass="games.strategy.triplea.attachments.UserActionAttachment" type="player"> <option name="conditions" value="conditionAttachmentTrollTribesAIPlayer"/> <option name="activateTrigger" value="triggerAttachmentTrollTribesIsHuman:1:false:false:false:false"/> <option name="text" value="HumanPlayer"/> </attachment> What this does is it set up to conditions: AI Player = True: Human Player = Invert AI Player. The trigger will change the switch of the AI Player depending on the Users action or inaction. The trigger can never fire on its own because the two conditions will never be true. You can place your troll selections after the conditions. If you are having trouble finding errors in you xml, try turning on the console. It is located by selecting "Engine Preferences" from the main screen. It is the third option under the 'Game' tab. Hope this is helpful. Cheers...

Thank you!

@Panther @Cernel thanks i forwarded your answer to the OP on reddit.

do you have any specific maps in mind where this would be particularly useful? Any map that uses territory effects with combat like the large middle earth map. Terrain map modes in games are useful for a quick visual glance for planning out moves in games (certain tripleA maps and other games) where terrain influences combat. @Zaroph You mean like the special colour currently given to all "impassable" territories, which makes you unable to see ownership colours completely (I'm assuming this behaviour exists only on the (wrong) assumption that all impassable territories are non-owned (that is, owned by the "Neutral" (null) player)). How would you deal with the fact that, differently from ownership, you can have an unlimited number of effects per territory? Yeah thats what I mean, like a simple example would be making all sea/water territories blue and all mountain territories some sort of dull grey or brown colour. From what I see, if you have 2+ effects in a territory they will be ordered in the game according to the order youve specified in the xml. So I imagine the most simple way of doing it would be to just take the first effect and use that.

@Major-Arcana Yes. Don't be afraid to look at the xml. Look at existing mods and see how things are done.

It'll be hard to say more until we know more about this problem. FWIW, save games have always required parts of the original map (for example territory names IIRC). There has been an attempt over time to reduce the dependency on an existing map, but for sure you do need a map to load a save game for that map. Name hacking will be unreliable but could work if you know what you're doing.

@ff03k64 Check this post for how to find the game.dtd I suggest using an editor that specifically supports xml. I use XML Copy Editor.

One clear example how the AI behaves when it comes to purchase. Germany can build 2 air units from start: For the matter of simplicity, i only state the most important values (attack/defense/movement @ cost) Aircraft A = 2/2/4 @ 9 Aircraft B = 3/3/4 @ 13 In this setup, the AI is purchasing only Aircraft A (dozens of test rounds) If i either increase A to 10 or decrease B by 1, the AI will only purchase Aircraft B. The first thing which irritates me is, that the cost difference between those units seems rather high in comparison to land or sea units in my game, but it was needed to get to the tipping point where the AI recognizes that one or the other air unit is best purchase. Normally i would only up the cost by 2 PUs if a unit gets +1 att/def more. This works ok because the AI will purchase both more or less, but is never totally ignoring a purchase like with those air units i mentioned above. A couple of land and sea units that AI is purchasing both and never ignore it are the following ones: Light Tank = 2/2/2 @ 7 Med Tank = 3/3/2 @ 9 and Destroyer = 2/2/2 @ 12 Cruiser = 3/3/2 @ 14 Those the AI is purchasing both more or less. Do Air units have different AI purchase code/formula than land/sea units?