@beelee Thanks, Yeah I've mostly just been adding and removing that air fleet units as required for combat but I think that I missed adding them back when we had our first big battle

@Nothingtoseehere gotcha 🫡

@Trout Tornado this morning Flash Flood watch thru staurday. Gotta do a quick hack on the window wells. Wanted to do a nice pro job but not gonna have time. Yea If you conquer one of the Capitals all of yours need to be in your control. So the game would continue. It's one full turn after the fall you check to see if the Victory conditions are met. So if Moscow falls to G then on G's next turn you see if they're met. You take Tokyo same turn, game would go on. Anyway I'll look later tonight. Gotta hit store and start work on those windows

@wc_sumpton Thanks! I will will experiment.

Let's handle the Battle of the Atlantic in the same way as it is handled in Big World 2. It will be named Handelskrieg instead of Wolfpack. It spawns 1 German submarine each round. It will have a unique submarine appearance (slightly different from regular subs) with 0/4/2 stats and 2 HP. I drew 3 new territories in the South Atlantic just in case the Allies try to kill it, so that "Handelskrieg" will have more space to escape. [image: 1785075450210-wwieurope_names_values-copy.jpg]

Sorry I don't know how to doit. Ii'll try tomorrow

@Trout oogly moogly !!!! This isnt even our game ! Sorry

@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....

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]

Hi Dog thanks for the latest version. The game seems to play a little more challengingly. A few more land/ sea territories would be great. I still keep Russia and Japan allied until the time is right for War between them, AI Russia still seems a little tentative to move the Siberian based units though. I move them manually but do you think there is an issue with the stacking restrictions on the old 2 hit tanks? Even I find them hard to move through other units.. The US does tend to evacuate the Pacific automatic placed units to the Atlantic and it does throw the Atlantic battles a little more in the allied favour. Tricky one. I still think random PT boat spawns may help if they were confined to Pacific only. Would there also be any way to look at factories. IE enemy factories are destroyed on capture and you can only build light industry on non sovereign territory? Also do you think the Russian player should be immune to Winter as they were more better prepared for it historically. Maybe also a Rasputitsa effect could block all movement on the Eastern front (all player) for one turn after Winter. Lastly, when any player wants to build an aircraft carrier they have to manually enter the quantity as there is no selector arrow for the box like other units. Took me a while to figure that one out in my first game. Apologies for the ramble and once again the game is playing well.

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

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

Interesting video, and welcome back! I think the changes are interesting. Regarding tactics I do think that having 5 levels is a lot. I think that @shorogyth 's system seems reasonable. I'd also pull the plains bonus out of the tactics system (call it "defensive tactics") and have a separate plains attack bonus. That way horses can have a bonus there, and rangers won't automatically be good attacking on plains. I know it's a third number, but I think it'll be less confusing than tactics being mostly defense bonuses but also one attack bonus. Also, can you have more than a +-1bonus on some terrains? I feel like most flying units would need more than a -1 bonus on caves, especially because tactics give them bonuses. I agree with the relentless issue. I think it's cool for some units to ignore your defensive terrain advantage, but they should be rare and therefore scary. Having basically all orcs be relentless is pretty silly and makes plains better for defense than cities. Regarding unit abilities, I don't think rock paper scissors is necessarily bad, especially because not all factions are equally strong in each. If each faction has different strengths and weaknesses, it forces factions to collaborate more, and stops things from snowballing as much if one faction falls. Eg Gondor would spam rangers because they have good defense bonuses and would kill the winged nazgul (thereby denying mordor's leadership), so you could send flanking cavalry from Rhun or harad to eliminate them. Elven archers were much stronger than the spearmen, but fell very quickly to wargs, which forced the elves to diversify more. In particular, Isengard had no ranged units, so Rohan's flank cavalry was especially dangerous since it would directly target the fires of orthanc, and so isengard had to spend a lot of effort screening its siege forces. I think ranged support feels reasonable. I like all abilities that encourage using a variety of units. Eg the galadhrim archers are one of the most powerful units in the game, but they require you to buy the weaker elven spearmen to unlock their full value. I like the change to charge, since before formation made those units a liability because you couldn't make them not charge. Eg the warg riders were essentially useless for angmar because of this and rohan suffered hard. I do like the new ambush mechanic since it encourages more diversity in unit selection. I do think it should be allowed in cities though (that was the whole siege of osgilliath), and the fact that only a certain number of units can ambush will balance it. I'm not sure I like scouting as it is though. If scouting eliminates ambush, then you just need 1-2 units with scouting in your army and you're fine. And if those units are otherwise useful (eg rangers) then it makes ambushers useless. Maybe scouting should be like spearwall? Just decreasing the effectiveness of ambush so it's less good but still useful? So maybe barrow wights would have an ambush of 6, then eg warg scouts could have a scouting of 2, rangers 3, and wizards 6x2 or sth? I feel like something missing in the game is some notion of hit and run tactics for cavalry. Cavalry is expensive and strong and excels at taking out small groups, but you often can't take advantage of this because if you do it exposes your cavalry to counterattack where they won't make up their PU values. Meanwhile air units can do this which gives angmar and mordor a big advantage. Maybe some cavalry could have an ability wherein they (and only they) can independently retreat after the first round of combat, even if there's a win? This still requires some thought, since if you don't have a win in your first round you have to decide if it's worth leaving your cavalry open to guarantee the win, and cavalry is still worse than flying units since they don't get the whole combat or a noncombat move. But it makes cavalry much more tactically interesting Also a general thought, but I think rangers need to be a higher tier of ranged unit. They have excellent tactics, mountaineer, high movement, anti-flying, scouting, ambush, support, and maybe more. And given the lore this makes sense, but also in the lore they aren't common at all - the Dunedain are solitary and dying out. So I think buffing them and treating them more like weak creatures than elite infantry would make more sense. And then you could maybe have some weaker version for gondor representing Faramir's rangers which are just elite infantry

@VictoryFirst said: So if I understand correctly, you can use Place with NoAirCheckPlaceDelegate and this would solve the problem of the AI not purchasing anything and it would prevent fighters that cannot land from being killed by the engine in the placement phase? The problem is not the delegate, NoAirCheckPlaceDelegate, but what the AI is coded for when doing purchasing, that being 'place' or 'endStep'. Because there is no 'place' the AI disregards the purchase. <delegate name="place" javaClass="games.strategy.triplea.delegate.NoAirCheckPlaceDelegate" display="Place Units"/> Works with <step name="AustroHungariansPlace" delegate="place" player="AustroHungarians"/> And fighters can stay 'isAir'. Cheers...

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

@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.

wtf !!!! This is the wrong place !!! I can't play anymore. What is wrong !!! What has happened to me !!! F this

@djggml So here is a working map.yml (remove the .txt to use it. map.yml.txt map_name: the_pact_of_steel games: - {game_name: Pact of Steel, file_name: pact_of_steel.xml} - {game_name: Pact of Steel 2, file_name: pact_of_steel_2.xml} - {game_name: Pact of Steel 233, file_name: pact_of_steel_233.xml} Note it has the version line removed.

@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.

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