@stevenJTripleA G40 EXP StevenJ vs JohnnyCat RUSSIA END _Turn 31.tsvg

@beelee Good morning. Sorry but still having trouble getting this battle set up. So I started all over for Combat Move and set up G but it still won't let me add in via Edit the red dot SS PG. It won't let me add it to Ukraine or the box. This is where I am at. Have G all set up except for the red dot SS PG 32f3781f-0cb7-4daf-bdb9-f03cc4dc0721-exp-game-12-trout-r7.tsvg

@beelee kill the factory.

Got A-Bomb sorted. Just need to get the right turn sequences and get the yanks up to speed with jerry. They will auto place now but still need to fight in edit. [image: 1780383267376-screenshot-from-2026-06-02-01-49-20.png] I used Moscow for testing purposes. They go right after Germany and I like the visual results.

@Nothingtoseehere .tsvg time

@Alexander Good Afternoon Well Jerry wasn't very light footed and stepped on all 3 LMs lol [image: 1780352001509-screenshot-from-2026-06-01-17-12-10.png] Game History Round: 16 Research Technology - Germans Purchase Units - Germans Trigger HvyCVBmbrs: Setting canBeGivenByTerritoryTo to British:Germans for unitAttachment attached to JPNbomber Trigger HvyCVBmbrs: Setting canBeGivenByTerritoryTo to British:Germans for unitAttachment attached to USAbomber triggerAttachmenLate1947EXP43Invert: has removed 1 Early1947_red owned by Changer in D-Day triggerAttachmenLate1947EXP43Invert: Changer has 1 Late1947_red placed in D-Day Trigger Wolfpack at112 SeaZones: Germans has 1 Wolfpack placed in 112 Sea Zone Germans buy 1 Escort, 1 GAirCommander, 1 German_LCV, 6 TotalWar_Tanks, 1 Waffen_Para, 1 carrier, 1 elite, 2 infantry and 1 waffen_infantry; Remaining resources: 0 PUs; Place Units - Germans Units in Germany being upgraded or consumed: 1 german_para and 1 infantry 1 Waffen_Para and 1 waffen_infantry placed in Germany Combat Move - Germans Trigger RailMovementAutoPlaceGermans: Germans has 2 G_Rails placed in Germany Turning on Edit Mode EDIT: Turning off Edit Mode 2 Me_262s moved from Belarus to Archangel 2 Me_262s moved from Belarus to Smolensk 1 LuftwaffeAce, 1 Me_262 and 1 bomber moved from Belarus to Bryansk EDIT: 1 1stPanzerArmy moved from Belarus to 1st Panzer EDIT: 1 Panzer_General and 5 armour moved from 1st Panzer to Belarus EDIT: 1 armour moved from Belarus to Archangel EDIT: 1 armour moved from Belarus to Smolensk EDIT: 2 armour moved from Belarus to Bryansk 2 infantry moved from Belarus to Archangel 1 elite and 1 infantry moved from Belarus to Smolensk 2 infantry moved from Belarus to Bryansk 1 waffen_infantry moved from Ukraine to Tambov Germans take Tambov from Russians 5 Type_XXI_UBoats moved from 112 Sea Zone to 110 Sea Zone 4 Me_262s moved from Southern Italy to Holland Belgium 4 Me_262s and 4 mech_infantrys moved from Western Germany to Holland Belgium Combat - Germans Trigger Wolfpack at112 SeaZones: Germans has 1 Wolfpack placed in 112 Sea Zone Turning on Edit Mode EDIT: Removing units owned by Germans from Archangel: 1 infantry EDIT: Removing units owned by Changer from Archangel: 1 R_mine_ARCH_Belarus EDIT: Removing units owned by Germans from Smolensk: 1 infantry EDIT: Removing units owned by Changer from Smolensk: 1 russian_mine_Red EDIT: Removing units owned by Germans from Bryansk: 1 infantry EDIT: Removing units owned by Changer from Bryansk: 1 R_mine_Bryansk_Belarus EDIT: Turning off Edit Mode Turning on Edit Mode EDIT: Battle in 110 Sea Zone EDIT: Germans attack with 5 Type_XXI_UBoats EDIT: British defend with 1 Escort EDIT: 3/5 hits, 3.33 expected hits EDIT: 0/1 hits, 0.33 expected hits EDIT: 1 Escort owned by the British lost in 110 Sea Zone EDIT: Germans win EDIT: Battle casualty summary: Battle score (TUV change) for attacker is 6 EDIT: Turning off Edit Mode Battle in Archangel Germans attack with 2 Me_262s, 1 armour and 1 infantry; Changer loiter and taunt Changer defend; Russians defend with 1 infantry Germans roll dice for 2 Me_262s, 1 armour and 1 infantry in Archangel, round 2 : 1/4 hits, 2.00 expected hits Russians roll dice for 1 infantry in Archangel, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Archangel Germans win, taking Archangel from Russians with 2 Me_262s, 1 armour and 1 infantry remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Battle in Smolensk Germans attack with 2 Me_262s, 1 armour and 1 elite Russians defend with 1 infantry Germans roll dice for 2 Me_262s, 1 armour and 1 elite in Smolensk, round 2 : 4/5 hits, 2.17 expected hits Russians roll dice for 1 infantry in Smolensk, round 2 : 0/1 hits, 0.33 expected hits 1 infantry owned by the Russians lost in Smolensk Germans win, taking Smolensk from Russians with 2 Me_262s, 1 armour and 1 elite remaining. Battle score for attacker is 3 Casualties for Russians: 1 infantry Battle in Bryansk Germans attack with 1 LuftwaffeAce, 1 Me_262, 2 armour, 1 bomber and 1 infantry Russians defend with 1 elite and 1 infantry Germans roll dice for 1 LuftwaffeAce, 1 Me_262, 2 armour, 1 bomber and 1 infantry in Bryansk, round 2 : 3/7 hits, 3.50 expected hits Russians roll dice for 1 elite and 1 infantry in Bryansk, round 2 : 1/3 hits, 1.00 expected hits 1 infantry owned by the Germans lost in Bryansk 1 infantry owned by the Russians and 1 elite owned by the Russians lost in Bryansk Germans win, taking Bryansk from Russians with 1 LuftwaffeAce, 1 Me_262, 2 armour and 1 bomber remaining. Battle score for attacker is 3 Casualties for Germans: 1 infantry Casualties for Russians: 1 elite and 1 infantry Battle in Holland Belgium Germans attack with 8 Me_262s and 4 mech_infantrys British defend with 1 UK_LCV, 1 elite and 1 infantry Germans roll dice for 8 Me_262s and 4 mech_infantrys in Holland Belgium, round 2 : 4/12 hits, 6.00 expected hits British roll dice for 1 UK_LCV, 1 elite and 1 infantry in Holland Belgium, round 2 : 2/3 hits, 1.00 expected hits 2 mech_infantrys owned by the Germans lost in Holland Belgium 1 UK_LCV owned by the British, 1 infantry owned by the British and 1 elite owned by the British lost in Holland Belgium Germans win, taking Holland Belgium from British with 8 Me_262s and 2 mech_infantrys remaining. Battle score for attacker is 1 Casualties for Germans: 2 mech_infantrys Casualties for British: 1 UK_LCV, 1 elite and 1 infantry Non Combat Move - Germans Turning on Edit Mode EDIT: Turning off Edit Mode Turning on Edit Mode EDIT: Turning off Edit Mode Turning on Edit Mode EDIT: Turning off Edit Mode Trigger RailMovementAutoPlaceRemoveGermans: has removed 1 G_Rail owned by Germans in Western Ukraine Trigger RailMovementAutoPlaceRemoveGermans: has removed 1 G_Rail owned by Germans in Western Germany Trigger Remove All Wolfpack: has removed 3 Wolfpacks owned by Germans in 112 Sea Zone Trigger Urals Tank Unit: Russians has 1 armour placed in Urals 1 Escort_Convoy moved from 112 Sea Zone to 104 Sea Zone EDIT: 5 Type_XXI_UBoats moved from 110 Sea Zone to 112 Sea Zone 2 Me_262s moved from Holland Belgium to Norway 2 Me_262s moved from Holland Belgium to 112 Sea Zone 4 Me_262s moved from Holland Belgium to Western Germany 1 Panzer_Grndrs moved from Western Germany to 112 Sea Zone 1 infantry moved from Denmark to 112 Sea Zone 1 Panzer_Grndrs and 1 infantry moved from 112 Sea Zone to Norway 1 Panzer_Grndrs, 1 SP_Artillery and 1 elite moved from Karelia to Novgorod 1 infantry moved from Novgorod to Karelia 2 Me_262s moved from Archangel to Novgorod 1 aaGun moved from Belarus to Novgorod 1 Waffen_Para moved from Romania to Germany 4 G_air_transports moved from Belarus to Western Germany EDIT: 1 Panzer_General moved from Belarus to Western Germany 1 bomber moved from Bryansk to Romania 1 LuftwaffeAce and 1 Me_262 moved from Bryansk to Belarus 2 Me_262s moved from Smolensk to Belarus 4 G_air_transports, 1 elite and 3 infantry moved from Germany to Belarus 1 G_Rail and 1 waffen_infantry moved from Germany to Western Ukraine 1 G_Rail moved from Germany to Southern Italy 1 G_Rail and 1 King_Tiger moved from Southern Italy to Western Germany EDIT: 1 Panzer_General moved from Western Germany to 1st Panzer Place Units - Germans 6 TotalWar_Tanks placed in Western Germany 1 Escort and 1 carrier placed in 112 Sea Zone 1 GAirCommander, 1 German_LCV, 1 elite and 2 infantry placed in Germany Trigger GermansTotalWarTankPlaceWesternGermany6: has removed 6 TotalWar_Tanks owned by Germans in Western Germany Trigger GermansTotalWarTankPlaceWesternGermany6: Germans has 6 armour placed in Western Germany Turn Complete - Germans Trigger Germans RemoveConvoySZ112Invert: has removed 1 Escort owned by Germans in 112 Sea Zone Trigger Germans RemoveConvoySZ104: has removed 1 Escort_Convoy owned by Germans in 104 Sea Zone Trigger Wolfpack at112 SeaZones: Germans has 1 Wolfpack placed in 112 Sea Zone Trigger Germans RemoveConvoySZ112Invert: Germans has 1 Escort_Convoy placed in 112 Sea Zone Trigger Germans RemoveConvoySZ104: Germans has 1 Escort placed in 104 Sea Zone Germans collect 50 PUs; end with 50 PUs Trigger Germans AdvancedProduction: Germans met a national objective for an additional 12 PUs; end with 62 PUs Trigger Germans 5 Swedish Iron Ore: Germans met a national objective for an additional 5 PUs; end with 67 PUs Objective Germans 2 Control Novgorod Or Volgograd Or Russia: Germans met a national objective for an additional 5 PUs; end with 72 PUs Combat Hit Differential Summary : Russians regular : -0.67 Germans regular : -1.67 EDIT: : -0.67 British regular : 1.00 EXP Game 2 Multi APbT G 16 .tsvg The PG wouldn't fly via A Trprt, hence the edit move. I will fix for next update. Edit Actually the PG is Air Transportable but I believe that when I used edit to remove 1st Panzer and then move the (Inactive) blue dot Pnzr and the 5 Pnzrs it commands into Belarus, triplea doesn't allow it to be then Air Trprtd. So just need to use edit when that happens. I will clarify in Game Notes.

@Roybot https://github.com/triplea-game/triplea/releases This should be on the downloads page, not hidden in the forum

@LaFayette Why is there chosen for this release strategy? What are the pros and cons? In other programs, there is a release strategy I like that notifies you every now and then of an update (like every 1-2 weeks). Then, as the user, you have the option to install the update, ignore it for now, or ignore it completely and not be reminded of it anymore. I think there are definitely people who would like to have the latest features and fixes, and if they get only notified like once every three or six months, they would have to go to the website themselves to see if there is a later version, somehow find out what has changed, and decide if it's worth updating. It would be better I think to have definitely not less than 4 releases a year. Probably more like 6 or 12 (simply every month). If we would do monthly releases, in an ideal world, players would get a pop-up the next time they start TripleA after a release, stating that there is a new recommended release, along with an overview of what has changed. Then, players have the option to install it (also ideally, let the program automatically uninstall the current version and install the new one instead of having to do that yourself), or to ignore the update for now and be reminded on the next start-up, or to ignore it completely and only be reminded once the next recommended release is out. There might be an argument against monthly releases that the program might not see enough updates in that time period. As I have started contributing only recently, I might have jumped in at a time that happened to have a lot of activity, but other than that I cannot imagine that in an entire month, nothing of importance has been done to the program. There is always some kind of improvement that would be nice to have for the user, regardless of how small it is. And once in a month is long enough that it wouldn't start feeling intrusive to a user, something that could happen with weekly releases. You don't want to bombard them with updates as that can become annoying over time. Twice a year sounds like way too little. A lot can happen during that time and might introduce too many changes and updates at once. Another argument would be that there wouldn't be enough new downloads that would prevent the TripleA installer from being flagged by Windows Defender when running. I can concur with that, but I think the majority of the downloads would come from users updating, not so much from new users downloading the program. So increasing the time period might not help as much as it might seem. But we would have to do some experimentation on that. Given everything, I would suggest simply starting with quarterly releases, that sounds like a good start, and then observe what the general feedback is from the users, and also keep an eye on the number of downloads.