@Trevan I suggest you not to make changes if you don't know what's the matter about it, especially in the moment that the change is not going to fix any known problems. The auto-elimination steps should rather be generally revised, maybe from scratch, so to solve the known problems and creating a system actually enforcing the correct rules (that will need to be interpreted, to some extent). Thinking hard about this, the only situation of only infrastructures remaining needing auto-elimination of non-infrastructure units I can think of is the case of defending units refusing to partake in air battles.

After intensively thinking I decided to make world map because it will be already possible to turn it into European map if somebody intend. Different aspects which will separated it from most other WWII maps but mostly it will be with v3 units and rules. More realistic incomes: Germany and USA will be relatively more stonger Double Sea zones in English Channel: Giving Germany opportunity threataning Allies shippings with submarines and air units considering Germany will start with French factory and most sea territores will be blockade zones. German Mediterranean: Germany will touch Adriatic. Russian's "life of road": Lake Ladoga is connected to lake of Onega which connects to Barents sea. Russia will need naval presence on the lake to reinfore easily Leningrad. Russia will have a specific cheap naval unit for this task which transports and defends. Siberians: Russian special unit with 2/3 stats and 3 Pus cost but can be placed on only south siberian factories and Russia starts with Mongolia. The issue is I'am undecided about the starting date. First option is Germany-Italy starts on prior of Barbarossa and Japan prior of the attack on Pearl harbour timelines the other one is either December 1941 or May 1942.

@LaFayette said in Should we support YAML for Maps?: In essence, XML was an early standardized format that grew out of HTML that was meant for structuring data for one computer to send data to another. It was never really intended for humans to interact with it and write it by hand (the idea was there would be GUIs to help you do that). Most likely this has always been the case for TripleA too. Ideally, you would have a map creator covering everything, and you would use that for creating and modifying the XML, never actually opening it with a text editor or anything. I believe this was the plan, except that it never happened (there have been several aborted attempts over the years).

@Cernel said in Zero movement cost to enter transports.: @Panther said in Zero movement cost to enter transports.: @Cernel said in Zero movement cost to enter transports.: @Panther Do you think that a mobility 0 unit that can be loaded onto a transport can be actually loaded onto the transport or is the mobility 0 making this impossible unless something gives a mobility bonus to the unit? I know that all units that are transportable have mobility 1 or more in the basic games. So, for example, I'm saying how about if I change the infantry mobility to 0, rest the same. The rules say that loading/offloading of a unit counts as the unit's entire move. Moving requires movement points. So I would conclude that a unit with "movement 0" can't move at all (unless - as you say - it receives a mobility bonus by whatever) . How would an infantry with "movement 0" physically move onto a transport? What we are talking about here is nothing else than moving a unit from a territory to a seazone and/or vice versa! I can't see how this could be allowed while movement between territories would be denied because of "movement 0" (again: unless - as you say - the unit receives a mobility bonus by whatever). Any considerations about the fact that TripleA requires units to be mobile to load onto transport ships, but allows offloading immobile units, instead? How can this be explained? For example, if a transport starts the game with mobility 0 infantries on board, does it make sense that they can be offloaded? Why should a mobility 0 infantry be unable to load onto a transport, while an already loaded mobility 0 infantry is able to offload from the same? It cannot be explained- at least not by the rules. From a rules perspective - as stated before - that does not make any sense. I can only recommend that a setup of a game does not include this constellation (again: unless - as you say - the unit receives a mobility bonus by whatever).

TripleA Turn Summary: UK_Pacific round 3 TripleA Turn Summary for game: World War II Global 1940 2nd Edition, version: 4.0.0 Game History Round: 3 Purchase Units - Americans Americans buy 1 carrier, 2 destroyers, 1 fighter and 1 tactical_bomber; Remaining resources: 1 PUs; Politics - Americans Trigger Americans War Production Eastern: has removed 1 factory_minor owned by Americans in Eastern United States Trigger Americans War Production Central: has removed 1 factory_minor owned by Americans in Central United States Trigger Americans War Production Western: has removed 1 factory_minor owned by Americans in Western United States Trigger Americans War Production Eastern: Americans has 1 factory_major placed in Eastern United States Trigger Americans War Production Central: Americans has 1 factory_major placed in Central United States Trigger Americans War Production Western: Americans has 1 factory_major placed in Western United States Combat Move - Americans Trigger Americans Unrestricted Movement: Setting movementRestrictionTerritories cleared for rulesAttachment attached to Americans 1 submarine moved from 54 Sea Zone to 44 Sea Zone 1 destroyer moved from 37 Sea Zone to 19 Sea Zone Americans take 20 Sea Zone from Japanese Americans take 19 Sea Zone from Japanese 1 submarine moved from 26 Sea Zone to 16 Sea Zone 1 fighter moved from 26 Sea Zone to 16 Sea Zone 1 fighter moved from 26 Sea Zone to 16 Sea Zone 1 infantry moved from Hawaiian Islands to 26 Sea Zone 1 artillery moved from Hawaiian Islands to 26 Sea Zone 1 fighter moved from Hawaiian Islands to 16 Sea Zone 1 tactical_bomber moved from Hawaiian Islands to 16 Sea Zone 1 fighter moved from Hawaiian Islands to 16 Sea Zone 1 fighter moved from Hawaiian Islands to 16 Sea Zone 1 artillery, 1 battleship, 1 carrier, 2 cruisers, 2 destroyers, 1 infantry and 1 transport moved from 26 Sea Zone to 7 Sea Zone 1 armour moved from Western United States to 10 Sea Zone 1 infantry moved from Western United States to 10 Sea Zone 1 armour, 1 battleship, 2 carriers, 1 destroyer, 1 infantry, 2 submarines and 1 transport moved from 10 Sea Zone to 7 Sea Zone 1 bomber moved from Eastern United States to Midway Combat - Americans Battle in 44 Sea Zone Americans attack with 1 submarine Japanese defend with 1 destroyer and 1 transport Americans roll dice for 1 submarine in 44 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits Japanese roll dice for 1 destroyer and 1 transport in 44 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits Americans roll dice for 1 submarine in 44 Sea Zone, round 3 : 0/1 hits, 0.33 expected hits Japanese roll dice for 1 destroyer and 1 transport in 44 Sea Zone, round 3 : 1/1 hits, 0.33 expected hits 1 submarine owned by the Americans lost in 44 Sea Zone Japanese win with 1 destroyer and 1 transport remaining. Battle score for attacker is -6 Casualties for Americans: 1 submarine Battle in 16 Sea Zone Americans attack with 5 fighters, 1 submarine and 1 tactical_bomber Japanese defend with 1 destroyer Americans roll dice for 1 submarine in 16 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits Americans roll dice for 5 fighters and 1 tactical_bomber in 16 Sea Zone, round 2 : 2/6 hits, 3.17 expected hits Japanese roll dice for 1 destroyer in 16 Sea Zone, round 2 : 0/1 hits, 0.33 expected hits 1 destroyer owned by the Japanese lost in 16 Sea Zone Americans win with 5 fighters, 1 submarine and 1 tactical_bomber remaining. Battle score for attacker is 8 Casualties for Japanese: 1 destroyer Non Combat Move - Americans 5 fighters and 1 tactical_bomber moved from 16 Sea Zone to 7 Sea Zone 1 artillery moved from Central United States to 101 Sea Zone 1 artillery and 1 transport moved from 101 Sea Zone to 86 Sea Zone 1 mech_infantry moved from Central United States to 101 Sea Zone 1 mech_infantry and 1 transport moved from 101 Sea Zone to 86 Sea Zone 1 artillery moved from 86 Sea Zone to Brazil Americans take Brazil from Neutral_Allies 1 mech_infantry moved from 86 Sea Zone to Brazil 1 mech_infantry moved from Central United States to 101 Sea Zone 1 mech_infantry and 1 transport moved from 101 Sea Zone to 86 Sea Zone 1 mech_infantry moved from 86 Sea Zone to Brazil Place Units - Americans 1 carrier and 2 destroyers placed in 101 Sea Zone 1 fighter and 1 tactical_bomber placed in 101 Sea Zone Turn Complete - Americans Americans collect 52 PUs; end with 53 PUs Objective Americans 1 Homeland: Americans met a national objective for an additional 10 PUs; end with 63 PUs Objective Americans 3 Defense Obligations: Americans met a national objective for an additional 5 PUs; end with 68 PUs Objective Americans 2 Outer Territories: Americans met a national objective for an additional 5 PUs; end with 73 PUs Purchase Units - Chinese Trigger Chinese Loses Burma Road: Chinese has their production frontier changed to: productionChinese_Burma_Road_Closed Chinese buy 3 infantry; Remaining resources: 0 PUs; Combat Move - Chinese Place Units - Chinese 3 infantry placed in Kansu Turn Complete - Chinese Chinese collect 4 PUs; end with 4 PUs Purchase Units - UK_Pacific UK_Pacific buy 4 artilleries; Remaining resources: 2 PUs; Combat Move - British 3 infantry moved from Malaya to Shan State 1 tactical_bomber moved from India to Shan State 1 fighter moved from India to Shan State 1 submarine moved from 95 Sea Zone to 98 Sea Zone 1 bomber moved from Morocco to Egypt 1 infantry moved from Belgian Congo to Anglo Egyptian Sudan Combat - British Battle in Shan State British attack with 1 fighter, 3 infantry and 1 tactical_bomber Japanese defend with 2 infantry British roll dice for 1 fighter, 3 infantry and 1 tactical_bomber in Shan State, round 2 : 1/5 hits, 1.67 expected hits Japanese roll dice for 2 infantry in Shan State, round 2 : 0/2 hits, 0.67 expected hits 1 infantry owned by the Japanese lost in Shan State British roll dice for 1 fighter, 3 infantry and 1 tactical_bomber in Shan State, round 3 : 2/5 hits, 1.67 expected hits Japanese roll dice for 1 infantry in Shan State, round 3 : 1/1 hits, 0.33 expected hits 1 infantry owned by the Japanese and 1 infantry owned by the British lost in Shan State British win, taking Shan State from Japanese with 1 fighter, 2 infantry and 1 tactical_bomber remaining. Battle score for attacker is 3 Casualties for Japanese: 2 infantry Casualties for British: 1 infantry Non Combat Move - British 1 fighter moved from Shan State to India 1 tactical_bomber moved from Shan State to India 1 destroyer moved from 39 Sea Zone to 79 Sea Zone 1 infantry moved from Tanganyika Territory to 72 Sea Zone 1 armour moved from Kenya to 72 Sea Zone 1 armour, 1 battleship, 1 cruiser, 1 infantry and 1 transport moved from 72 Sea Zone to 79 Sea Zone 1 infantry moved from 79 Sea Zone to West India 1 armour moved from 79 Sea Zone to West India 1 mech_infantry moved from Persia to Eastern Persia British take Eastern Persia from Neutral_Allies 1 infantry moved from Persia to Northwest Persia 1 infantry moved from Persia to Northwest Persia 1 infantry moved from Egypt to 81 Sea Zone 1 artillery moved from Egypt to 81 Sea Zone 1 tactical_bomber moved from Anglo Egyptian Sudan to Eastern Persia 1 fighter moved from Anglo Egyptian Sudan to Eastern Persia 1 artillery, 2 destroyers, 1 infantry and 1 transport moved from 81 Sea Zone to 79 Sea Zone 1 infantry moved from 79 Sea Zone to West India 1 artillery moved from 79 Sea Zone to West India 1 fighter moved from Morocco to Malta 1 tactical_bomber moved from Morocco to Malta 1 fighter moved from Morocco to Malta Place Units - UK_Pacific 4 artilleries placed in India Turn Complete - UK_Pacific UK_Pacific collect 10 PUs; end with 12 PUs Some Units in India change ownership: 4 artilleries Combat Hit Differential Summary : Americans regular : -2.17 Japanese regular : 0.00 British regular : -0.33 Savegame

@Jason-Green-Lowe heh heh friendly advice was just saying you could have it included in the original map for a one click activation instead of an entirely separate map

@LaFayette Thanks. Although it is curiouser and curiouser (to quote Lewis Carroll) why onezingy could get on but not others. He did text he downloaded the latest game engine if it matters. You can close the this thread then.

Now for the last thing for these units. How can i place them in allied territories (assuming i have a rookie there)?

@LaFayette not sure how i would but regardless even if the thing is using curves to match a gamut it will not be 100% as good an originally colored graphic some information is always lost when you do it it's just a matter of degrees and again often times the unit is not of one hue to begin with so yeah… maybe we've talked this one past death at this point.

@Numetalfan The saved game carries a copy of the xml used to create the game. Any changes made to the xml will not show in a saved game. To test changes you have to always start a new game. Cheers...

@wc_sumpton That was it, thanks!

@RogerCooper first, thx for the hints. I cleaned up my xml removed all the double entries for connections secondly, thx for the compliment. We are still busy working on that szenario, it is not yet finished. The idea of a sploit of the US is a nice thing, it makes the game much more interesting as there is always action in both the Atlantic and the Pacific, however there is al lot to do too. new national objectives, balancing the map and the units, the starting income etc.

@RogerCooper thanks, I will check that map out!

I would love to see the ladder/statistics incorporated into the engine.

One challenge is having a mechanism to associate a game notes file with the game file. Having the two files with matching names and the notes file being suffixed with '-notes.html' might be easy enough. For example: world_at_war.xml world_at_war-notes.html

There were a few reasons to bring in 1.8 compatibility: we are getting about one error report a week for players launching 1.8 maps. The 1.8 maps keep coming up: https://github.com/triplea-game/triplea/issues/7132 https://forums.triplea-game.org/topic/2234/need-help-to-convert-an-old-game?_=1600642324318 we should never have assumed that we can upgrade all maps in bulk, we do not 'own' all maps. Not all maps are in the repositories it's been a long running design principle that maps should never be broken. The mechanisms to support this had some big problems and we dropped it in 1.9 as it was not scaling and really just was not cutting it. As mentioned, 2.3 has a new map parsing architecture that makes supporting 1.8 maps much easier. Adding in that support resolves the above problems and gives us a proving ground for being able to support more XML variations going forward. As a bonus, now that the map export is fixed, because players can launch 1.8 maps, if they want to upgrade them, they only need to now launch the map and can then re-export the XML.

@LaFayette said in Non-Combat Movement Bonus Tech: @Cernel Oh, gotchya, it's not a base ability to have different movement across phases. I'd agree that it should then be a base ability option and a technology would only then be a true bonus to add to that. Yes, this is what I was saying, but it's not a big deal. Mostly I feel it is unpolished that, for example, if I want to have a unit that is (always) a land transport, I am forced to give a tech to every player for that. The way @wc_sumpton is doing it is consistent with many other existent items, so my position against such things is general, not specific to this feature (and it's not a big deal just giving everyone the tech).

Yes but they are only useful against Japan if she decides to advance deeply into Russia. Siberian factories distance enough to German front to be massively used.

Thanks for finding that. I think the fix is for AA to not shoot at air transported units. On the flip side we should be sure they are removed as casualties if the transport is shot down.

@Panther the two HTML files are now updated to be MD, they'll render now.