@beelee Game History Round: 1 Purchase Units - Japanese Japanese buy 1 Japanese_LCV, 1 air_transport, 1 elite, 1 factory_minor and 1 transport; Remaining resources: 0 PUs; 6 SuicideAttackTokens; Combat Move - Japanese Trigger RailMovementAutoPlaceJapanese: Japanese has 2 J_Rails placed in Kiangsu 1 artillery and 2 infantry moved from Jehol to Chahar Japanese take Chahar from Chinese 1 artillery and 3 infantry moved from Shantung to Anhwe Japanese take Anhwe from Chinese 1 artillery and 3 infantry moved from Kwangsi to Yunnan 1 fighter and 1 tactical_bomber moved from Kiangsu to Yunnan 1 artillery and 3 infantry moved from Kiangsi to Hunan 1 fighter and 1 tactical_bomber moved from Manchuria to Hunan 1 fighter and 1 tactical_bomber moved from Manchuria to Hunan 2 JPNbombers moved from Japan to Yunnan 1 fighter moved from Formosa to Hunan Combat - Japanese Battle in Hunan Japanese attack with 1 artillery, 3 fighters, 3 infantry and 2 tactical_bombers Chinese defend with 2 infantry Japanese roll dice for 1 artillery, 3 fighters, 3 infantry and 2 tactical_bombers in Hunan, round 2 : 6/9 hits, 3,83 expected hits Chinese roll dice for 2 infantry in Hunan, round 2 : 0/2 hits, 0,67 expected hits 2 infantry owned by the Chinese lost in Hunan Japanese win, taking Hunan from Chinese with 1 artillery, 3 fighters, 3 infantry and 2 tactical_bombers remaining. Battle score for attacker is 6 Casualties for Chinese: 2 infantry Battle in Yunnan Japanese attack with 2 JPNbombers, 1 artillery, 1 fighter, 3 infantry and 1 tactical_bomber Chinese defend with 4 infantry Japanese roll dice for 2 JPNbombers, 1 artillery, 1 fighter, 3 infantry and 1 tactical_bomber in Yunnan, round 2 : 3/8 hits, 3,50 expected hits Chinese roll dice for 4 infantry in Yunnan, round 2 : 1/4 hits, 1,33 expected hits 1 infantry owned by the Japanese lost in Yunnan 3 infantry owned by the Chinese lost in Yunnan Japanese roll dice for 2 JPNbombers, 1 artillery, 1 fighter, 2 infantry and 1 tactical_bomber in Yunnan, round 3 : 5/7 hits, 3,33 expected hits Chinese roll dice for 1 infantry in Yunnan, round 3 : 0/1 hits, 0,33 expected hits 1 infantry owned by the Chinese lost in Yunnan Japanese win, taking Yunnan from Chinese with 2 JPNbombers, 1 artillery, 1 fighter, 2 infantry and 1 tactical_bomber remaining. Battle score for attacker is 9 Casualties for Japanese: 1 infantry Casualties for Chinese: 4 infantry Trigger Remove All Wolfpack: has removed 1 Wolfpack owned by Germans in 112 Sea Zone Non Combat Move - Japanese Trigger Wolfpack at112 SeaZones: Germans has 1 Wolfpack placed in 112 Sea Zone Trigger RailMovementAutoPlaceRemoveJapanese: has removed 2 J_Rails owned by Japanese in Kwangsi 2 JPNbombers, 1 fighter and 1 tactical_bomber moved from Yunnan to Kwangsi 2 fighters and 2 tactical_bombers moved from Hunan to Kwangsi 1 fighter moved from Hunan to Kwangsi 1 J_Rail and 1 infantry moved from Kiangsu to Kwangsi 1 J_Rail and 1 artillery moved from Kiangsu to Kwangsi 2 infantry moved from Kiangsu to Kiangsi 2 infantry moved from Formosa to 20 Sea Zone 1 cruiser, 2 infantry and 1 transport moved from 20 Sea Zone to 36 Sea Zone 2 infantry moved from 36 Sea Zone to Kwangsi 2 infantry moved from Okinawa to 19 Sea Zone 1 Japan_destroyer, 1 battleship, 2 infantry, 1 submarine and 1 transport moved from 19 Sea Zone to 36 Sea Zone 2 infantry moved from 36 Sea Zone to Kwangsi 1 armour and 1 infantry moved from Japan to 6 Sea Zone 1 Japan_destroyer, 1 armour, 1 infantry and 1 transport moved from 6 Sea Zone to 36 Sea Zone 1 armour and 1 infantry moved from 36 Sea Zone to Kwangsi 1 carrier, 1 fighter and 1 tactical_bomber moved from 6 Sea Zone to 36 Sea Zone 1 submarine moved from 6 Sea Zone to 36 Sea Zone 1 fighter moved from Okinawa to Japan 2 tactical_bombers moved from Japan to Manchuria 1 fighter moved from Korea to Manchuria 4 infantry moved from Korea to Manchuria 1 mech_infantry moved from Manchuria to Anhwe 3 infantry moved from Manchuria to Jehol 1 infantry moved from Manchuria to Jehol 1 Japan_destroyer moved from 6 Sea Zone to 16 Sea Zone 1 Japan_destroyer moved from 33 Sea Zone to 6 Sea Zone 1 carrier, 1 fighter and 1 tactical_bomber moved from 33 Sea Zone to 36 Sea Zone Place Units - Japanese 1 factory_minor placed in Kiangsu 1 transport placed in 6 Sea Zone 1 Japanese_LCV, 1 air_transport and 1 elite placed in Japan Turn Complete - Japanese Japanese collect 30 PUs; end with 30 PUs Trigger Japanese AdvancedProduction: Japanese met a national objective for an additional 8 Optional[PUs]; end with 38 Optional[PUs] Objective Japanese 1 Trade With America: Japanese met a national objective for an additional 10 PUs; end with 48 PUs Combat Hit Differential Summary : Chinese regular : -1,33 Japanese regular : 3,33 exp-game-11-dr.strangelove-J1.tsvg

@beelee I guess before my next J turn, I can ask Captain for clarification on whether sweeping LMs during NCM limits an engineer to stopping after he does his little LM removal gig. Yes, I think we have all defeated each other so could be random who wins. It seems as if all of us are better Axis players than Allies, so that may skew who actually wins our tourney. Although maybe playing Tournament rules will even that out a bit since some of the G special units won't be available. For myself and I suspect the same for all of you, whichever one of us wins will have my full support against the Danish Mafia. It might be a Miracle on Ice situation - if Panzer/Alex are familiar with that story.

@beelee 8b0b5558-575e-453b-a7bc-68ccf0893c7f-exp-game-12-trout-uk9.tsvg Allies finished. Over to Italy now. Okay, another weird wrinkle. So I noticed that my USA bomber was still in SZ 16, I guess because he could land on the Heavy Carrier. But it was my intention to put him back at the Midway air base. So when I did that, the elite stopped eating rice in Manchuria and went back to his correct location in SZ 16. But the tank in SZ 16 decided to take its place in Manchuria. Again, if you hover over SZ 16, it shows the tank being there so I think all is correct except the tank appearing in Manchuria. I think you're right about it being an overflow issue

@beelee thanks will check it out as soon as i am able 🫡

@wc_sumpton The production value of 0 is probably confusing the AI.

Late fighters are balanced around with other units and techs.

@TheDog I have a specirfic TripleA version with some specific xml files for games like TWW and I have 2/3 curent games so it is not so easy....

@Kindwind A neural net certainly makes more sense than a LLM. I didn't see anything obviously illegal in the play, but you didn't document the non-combat moves which caused a problem with your previous model As you noted, your neural net is inferior to your algorithmic WeakAI, which is itself comparable to TripleA's Easy AI. However it does attack and would beat TripleA's Do Nothing AI, which is something. (I have seen a GGP (Ludii) that plays Chess so poorly that it has trouble against random play). However, that it can't beat the training AI seems to point to a fundamental weakness with this sort of neural net. Note that AlphaZero played 44,000,000 games of Chess in its training process (600 years on your computer), and Chess is much simpler game computationally.

@Nothingtoseehere gotcha 🫡

@malmessi It is in game in the usual place Help> Game Notes

Latest version v275 ready for download with in TripleA. In TripleA Click Download Maps Button Click Installed tab Click 1941 Global Command Decision Click Remove Button Click Yes button to remove Click Ok button (Successfully removed) Click Close (To force the map list to refresh) Click Download Maps Button Find & Click 1941 Global Command Decision Click Install button Enjoy! . v275 Previously the Non Aggession Pact between USSR and Japan starts to fail arounf Turn 15, only because its Turn 15, this is illogical. So to improve on it, this applies to Players & AI The USSR and Japan have a Non Aggression Pact that prevents both sides from attacking each other. When Japan or allies owns Chungking/Industry-Med there will be skirmishes on the Japan-USSR border When Japan or allies owns Chungking/Industry-Med & Urumchi-Kansu/Industry-Lgt it will declare war on USSR When USSR retakes 3 of its lost territories held before Operation Barbarossa there will be skirmishes on the Japan-USSR border When USSR retakes 5 of its lost territories held before Operation Barbarossa it will declare war on Japan Gemrnay & Italy will now have a harder time vs USSR, as USSR will be focusing on their attacks and not distracted by Japan to the south. Japan AI needs help to play better When Japan or allies owns Chungking/Industry-Med, for each turn up to 9 times it will purchase 3x Destroyers, 1x Cruiser, 1x Convoy When Japan or allies owns Urumchi-Kansu/Industry-Lgt, for each turn up to 9 times it will purchase 3x Destroyers, 1x Cruiser Having achieved some of its primary objectives Japan can divert resources to ships. China Player & AI As Japan and USSR will not go to war around turn 15 and Japan was conquering China too easily/quickly. China has a small free increase of a Bunker per turn, this simulates its massive population digging in and resisting its invaders USA AI needs help to play better Turns 2,4,8,12,16,20,24 AI purchases 2x Fighter, Bomber-Tac, Carrier-Fleet, 2x Cruiser, Battleship and places in 010 B Sea Zone This is a small increase of a Cruiser & Battleship and it makes the USA AI more aggressive when using Fast-AI This is big, I think I finally understand Sea Zone ownership and PU production Each Sea Zone generates 1-2pu per turn for the original owner only, just like Convoy Centers. Enemy occupation denies the original owner of the PU income. The current owner has its national flag in the Sea Zone. . v275 documentation, last page has winter turn on instructions. 1941_Global_Command_Decision_Manual.pdf Suggested TripleA version https://github.com/triplea-game/triplea/releases . Link to 1st post that has; Downloads for new Players https://forums.triplea-game.org/topic/3326/1941-global-command-decision-official-thread

@panzerstahl-helm-0 Hallo sent you a PM about the Captain's tournament Prost [image: 1785885528106-prost.png]

Game History Round: 6 Purchase Units - Japanese Note to players Japanese: It is Late 1942 and Prime Minister Tojo has Ordered All Japanese to Fight to the Death ! Banzai Attacks are Now Possible. Japanese buy 6 Fortifications, 1 Heavy_BB, 1 Japan_destroyer, 4 armour, 1 elite, 1 infantry and 2 mech_infantrys; Remaining resources: 0 PUs; 6 SuicideAttackTokens; Combat Move - Japanese Trigger Banzai: Japanese has 1 Banzai placed in Japan Trigger RailMovementAutoPlaceJapanese: Japanese has 2 J_Rails placed in Kiangsu 1 artillery and 2 infantry moved from Novosibirsk to Vologda 1 JPNbomber moved from Kansu to Vologda 1 armour, 1 fighter, 2 infantry and 1 tactical_bomber moved from Tsinghai to Kazakhstan 2 armour moved from Kansu to Kazakhstan 1 infantry moved from Novosibirsk to Vologda 1 artillery and 2 infantry moved from Timguska to Evenkiyskiy 1 artillery moved from Novosibirsk to Samara 1 armour moved from Novosibirsk to Samara 1 tactical_bomber moved from Kansu to Kazakhstan 1 fighter moved from Kansu to Samara 6 armour and 1 mech_infantry moved from Novosibirsk to Urals 1 JPNbomber moved from Tsinghai to Kazakhstan 1 elite and 2 infantry moved from Amur to Buryatia 1 fighter moved from 5 Sea Zone to Buryatia 1 infantry moved from Siberia to Sakha Japanese take Sakha from Russians Combat - Japanese Battle in Evenkiyskiy Japanese attack with 1 artillery and 2 infantry Russians defend with 1 infantry Japanese roll dice for 1 artillery and 2 infantry in Evenkiyskiy, round 2 : 1/3 hits, 0.83 expected hits Russians roll dice for 1 infantry in Evenkiyskiy, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Evenkiyskiy Japanese win, taking Evenkiyskiy from Russians with 1 artillery and 2 infantry remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Battle in Vologda Japanese attack with 1 JPNbomber, 1 artillery and 3 infantry Russians defend with 2 infantry Japanese roll dice for 1 JPNbomber, 1 artillery and 3 infantry in Vologda, round 2 : 3/5 hits, 1.67 expected hits Russians roll dice for 2 infantry in Vologda, round 2 : 0/2 hits, 0.67 expected hits 2 infantry owned by the Russians lost in Vologda Japanese win, taking Vologda from Russians with 1 JPNbomber, 1 artillery and 3 infantry remaining. Battle score for attacker is 6 Casualties for Russians: 2 infantry Battle in Samara Japanese attack with 1 armour, 1 artillery and 1 fighter Russians defend with 1 infantry Japanese roll dice for 1 armour, 1 artillery and 1 fighter in Samara, round 2 : 2/3 hits, 1.33 expected hits Russians roll dice for 1 infantry in Samara, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Samara Japanese win, taking Samara from Russians with 1 armour, 1 artillery and 1 fighter remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Battle in Kazakhstan Japanese attack with 1 JPNbomber, 3 armour, 1 fighter, 2 infantry and 2 tactical_bombers Russians defend with 4 Army_Conscripts, 1 Soviet_Commisar_3 and 1 armour Japanese roll dice for 1 JPNbomber, 3 armour, 1 fighter, 2 infantry and 2 tactical_bombers in Kazakhstan, round 2 : 6/9 hits, 4.33 expected hits Russians roll dice for 4 Army_Conscripts, 1 Soviet_Commisar_3 and 1 armour in Kazakhstan, round 2 : 2/8 hits, 3.33 expected hits 2 infantry owned by the Japanese lost in Kazakhstan 1 Soviet_Commisar_3 owned by the Russians, 1 armour owned by the Russians and 4 Army_Conscripts owned by the Russians lost in Kazakhstan Japanese win, taking Kazakhstan from Russians with 1 JPNbomber, 3 armour, 1 fighter and 2 tactical_bombers remaining. Battle score for attacker is 7 Casualties for Japanese: 2 infantry Casualties for Russians: 4 Army_Conscripts, 1 Soviet_Commisar_3 and 1 armour Battle in Urals Japanese attack with 6 armour and 1 mech_infantry Russians defend with 1 infantry Japanese roll dice for 6 armour and 1 mech_infantry in Urals, round 2 : 4/7 hits, 3.17 expected hits Russians roll dice for 1 infantry in Urals, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Urals Japanese win, taking Urals from Russians with 6 armour and 1 mech_infantry remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Battle in Buryatia Japanese attack with 1 elite, 1 fighter and 2 infantry Russians defend with 1 infantry Japanese roll dice for 1 elite, 1 fighter and 2 infantry in Buryatia, round 2 : 2/5 hits, 1.17 expected hits Russians roll dice for 1 infantry in Buryatia, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Buryatia Japanese win, taking Buryatia from Russians with 1 elite, 1 fighter and 2 infantry remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Trigger Remove All Wolfpack: has removed 1 Wolfpack owned by Germans in 110 Sea Zone Trigger Remove All Wolfpack: has removed 1 Wolfpack owned by Germans in 112 Sea Zone Non Combat Move - Japanese Trigger RemoveBanzai: has removed 1 Banzai owned by Japanese in Japan Trigger Wolfpack at110 SeaZones: Germans has 1 Wolfpack placed in 110 Sea Zone Trigger Wolfpack at112 SeaZones: Germans has 1 Wolfpack placed in 112 Sea Zone Trigger RailMovementAutoPlaceRemoveJapanese: has removed 2 J_Rails owned by Japanese in Novosibirsk 1 fighter moved from Buryatia to Amur 1 Japan_destroyer moved from 5 Sea Zone to 6 Sea Zone 1 infantry moved from Japan to 6 Sea Zone 1 Japan_destroyer and 1 infantry moved from 6 Sea Zone to 5 Sea Zone 1 infantry moved from 5 Sea Zone to Siberia 1 carrier, 1 fighter and 1 transport moved from 5 Sea Zone to 6 Sea Zone 2 Japan_Engineers, 1 elite and 1 infantry moved from Japan to 6 Sea Zone 4 armour and 1 mech_infantry moved from Kweichow to Tsinghai 2 armour and 1 mech_infantry moved from Shantung to Kweichow 2 armour and 1 mech_infantry moved from Kiangsu to Kweichow 1 JPNbomber moved from Vologda to Tsinghai 1 JPNbomber moved from Kazakhstan to Kwangsi 1 fighter and 2 tactical_bombers moved from Kazakhstan to Novosibirsk 1 fighter moved from Samara to Novosibirsk 1 infantry moved from Kansu to Timguska 1 infantry moved from Kansu to Novosibirsk 1 J_Rail moved from Kiangsu to Kweichow 1 J_Rail moved from Kweichow to Novosibirsk 1 aaGun moved from Novosibirsk to Urals 1 J_Rail moved from Kiangsu to Amur 1 J_Rail and 1 aaGun moved from Amur to Novosibirsk 1 pacific_cruiser moved from 6 Sea Zone to 36 Sea Zone 1 tactical_bomber moved from 6 Sea Zone to 19 Sea Zone 1 pacific_submarine moved from 6 Sea Zone to 36 Sea Zone 2 Japan_Engineers, 1 elite, 1 infantry and 2 transports moved from 6 Sea Zone to 19 Sea Zone 2 Japan_Engineers, 1 elite and 1 infantry moved from 19 Sea Zone to Kiangsu 1 carrier moved from 6 Sea Zone to 36 Sea Zone 1 carrier moved from 6 Sea Zone to 19 Sea Zone 1 fighter moved from 6 Sea Zone to 19 Sea Zone 1 Escort_Convoy moved from 6 Sea Zone to 19 Sea Zone 1 fighter moved from 6 Sea Zone to Japan 1 Japan_destroyer, 1 battleship and 1 cruiser moved from 5 Sea Zone to 6 Sea Zone Place Units - Japanese 6 Fortifications placed in Caroline Islands 2 armour and 1 mech_infantry placed in Shantung 2 armour and 1 mech_infantry placed in Kiangsu 1 elite and 1 infantry placed in Japan 1 Heavy_BB and 1 Japan_destroyer placed in 6 Sea Zone Turn Complete - Japanese Note to players Japanese: It is Late 1942 and Our Shipyards are Hard at Work. We will soon Launch 1 new Carrier with 2 new Naval Fighters. They may only Operate in the Pacific and Indian Oceans. Japanese collect 50 PUs; end with 50 PUs Trigger Japanese AdvancedProduction: Japanese met a national objective for an additional 8 Optional[PUs]; end with 58 Optional[PUs] Objective Japanese 1 Trade With America: Japanese met a national objective for an additional 10 PUs; end with 68 PUs Objective Japanese 5 Control China: Japanese met a national objective for an additional 5 PUs; end with 73 PUs Combat Hit Differential Summary : Japanese regular : 5.50 Russians regular : -3.33 EXP-bvsb-7-1-26 J .6tsvg.tsvg lol commies getting their ass kicked [image: 1785968892721-screenshot-from-2026-08-05-17-25-49.png] [image: 1785968904467-screenshot-from-2026-08-05-17-26-03.png] [image: 1785968914364-screenshot-from-2026-08-05-17-26-40.png]

@Ramon said: Let me know if you somehow find a fix! I have had two attempts at it, so will do, but it will not be soon, spare time goes on the new map.

@beelee Unfortunate, but its good to know its currently not working rather than something I was doing wrong, ty.

I put it onto github under https://github.com/triplea-maps/thehobbesians_1939. I will add to the in-game downloader tomorrow.

@TheDog said: @rogercooper Cant find Ansalon/Analon on Github maps Missing from your list, but on Github maps Settlers: Fallen Empire Shogun Advanced Ansalon was superseded. https://axisandallies.fandom.com/wiki/Master_of_Ansalon Settlers: Fallen Empire uses the Fallen Empire Map Shogun Advanced is under The Shogun Map

@Cernel When the Revised Ladder bots were crashing frequently, I moved them onto Amazon Web Services and reworked how they were launched and maintained. AWS is a cloud hosted Linux server, so the bots run remotely rather than depending on my own computer, home internet connection, or an open SSH window. I connect to the server through SSH, but the bots themselves run inside persistent tmux sessions. tmux is useful here because it separates the bot process from the temporary SSH connection. I can disconnect from the server, close my laptop, or lose my local connection without terminating the bot. Each bot has its own named session, which also makes it easier to inspect or restart one without affecting the other. The main upkeep commands are: tmux ls This shows whether the bot sessions are still present. tmux attach -t revised_ladder tmux attach -t revised_ladder2 These reconnect me to the live console output for either bot so I can inspect errors, freezes, or lobby disconnects. To leave a session while keeping the bot running: Ctrl+B, then D If the bot is frozen rather than fully gone, I can attach to the session, stop the process with Ctrl+C, and relaunch it using the relevant startup script. I also set up the launch process so that if a bot process actually disappears or exits, it is automatically started again. In other words, the server does not simply leave the bot offline after a crash. The surrounding startup or monitoring process detects that the bot is no longer running and relaunches it. That does not necessarily fix every possible freeze, since a frozen process may still technically exist, but it does handle ordinary crashes and unexpected exits without requiring me to log in immediately. So the overall setup has three layers: AWS provides the continuously available cloud server. tmux keeps the bot sessions alive independently of SSH. The restart logic relaunches a bot when its process exits or disappears. This is what I implemented when the bots were crashing a lot. Since then, the AWS and tmux setup has generally been stable, and the automatic restart behavior has reduced the amount of manual intervention needed.

@Cernel yes there's a temporary workaround which is to go to "show current game". i say it is attached to being online because it's ok with a local game.