@Cernel oh right i’ve used esc for long long i don't even think abt it now lol thanks

@beelee Game History Round: 12 Purchase Units - Russians Russians buy 1 Soviet_Partisan, 1 TankDestroyerFS, 1 elite and 10 infantry; Remaining resources: 0 PUs; 3 AirLendLease; 3 TankLendLease; Combat Move - Russians Trigger RailMovementAutoPlaceRussians: Russians has 1 R_Europe_Rail and 2 Russian_Rails placed in Russia Turning on Edit Mode EDIT: Turning off Edit Mode EDIT: 10 Russian_Rocketss moved from Belarus to Slovakia Hungary EDIT: 1 russian_para moved from Belarus to Slovakia Hungary 1 fighter and 1 tactical_bomber moved from Belarus to Baltic States 2 armour moved from Belarus to Eastern Poland 1 FighterAce moved from Karelia to Eastern Poland 1 armour moved from Belarus to Baltic States 1 armour moved from Belarus to Eastern Poland 1 russian_para moved from Belarus to Baltic States 1 fighter moved from Belarus to Eastern Poland 1 bomber moved from Belarus to Eastern Poland 1 bomber moved from Russia to Eastern Poland 1 infantry moved from Kazakhstan to Novosibirsk 1 elite moved from Urals to Evenkiyskiy 1 armour moved from Urals to Evenkiyskiy 1 armour moved from Urals to Novosibirsk 2 armour, 1 guard_infantry and 2 infantry moved from Shensi to Kansu Chinese take Kansu from Japanese 1 armour moved from Shensi to Kansu 1 bomber moved from Russia to Novosibirsk Combat - Russians Battle in Novosibirsk Russians attack with 1 armour, 1 bomber and 1 infantry Japanese defend with 1 infantry Russians roll dice for 1 armour, 1 bomber and 1 infantry in Novosibirsk, round 2 : 0/3 hits, 1,33 expected hits Japanese roll dice for 1 infantry in Novosibirsk, round 2 : 0/1 hits, 0,33 expected hits Russians roll dice for 1 armour, 1 bomber and 1 infantry in Novosibirsk, round 3 : 2/3 hits, 1,33 expected hits Japanese roll dice for 1 infantry in Novosibirsk, round 3 : 1/1 hits, 0,33 expected hits 1 infantry owned by the Russians lost in Novosibirsk 1 infantry owned by the Japanese lost in Novosibirsk Russians win, taking Novosibirsk from Japanese with 1 armour and 1 bomber remaining. Battle score for attacker is 0 Casualties for Russians: 1 infantry Casualties for Japanese: 1 infantry Battle in Baltic States Russians attack with 1 armour, 1 fighter, 1 russian_para and 1 tactical_bomber Germans defend with 2 armour Russians roll dice for 1 armour, 1 fighter, 1 russian_para and 1 tactical_bomber in Baltic States, round 2 : 2/4 hits, 1,83 expected hits Germans roll dice for 2 armour in Baltic States, round 2 : 1/2 hits, 1,00 expected hits 1 russian_para owned by the Russians lost in Baltic States 2 armour owned by the Germans lost in Baltic States Russians win, taking Baltic States from Germans with 1 armour, 1 fighter and 1 tactical_bomber remaining. Battle score for attacker is 6 Casualties for Russians: 1 russian_para Casualties for Germans: 2 armour Battle in Slovakia Hungary Russians attack with 10 Russian_Rocketss and 1 russian_para Germans defend with 1 elite; Italians defend with 1 aaGun Russians roll dice for 10 Russian_Rocketss in Slovakia Hungary, round 2 : 6/10 hits, 3,33 expected hits 1 elite owned by the Germans and 1 aaGun owned by the Italians lost in Slovakia Hungary 10 Russian_Rocketss owned by the Russians lost in Slovakia Hungary Russians win, taking Slovakia Hungary from Germans with 1 russian_para remaining. Battle score for attacker is -2 Casualties for Italians: 1 aaGun Casualties for Germans: 1 elite Casualties for Russians: 10 Russian_Rocketss Battle in Eastern Poland Russians attack with 1 FighterAce, 3 armour, 2 bombers and 1 fighter Germans defend with 1 ElitePanzer and 1 elite Russians roll dice for 1 FighterAce, 3 armour, 2 bombers and 1 fighter in Eastern Poland, round 2 : 3/8 hits, 4,33 expected hits Germans roll dice for 1 ElitePanzer and 1 elite in Eastern Poland, round 2 : 2/4 hits, 1,67 expected hits 2 armour owned by the Russians lost in Eastern Poland 1 elite owned by the Germans and 1 ElitePanzer owned by the Germans lost in Eastern Poland Russians win, taking Eastern Poland from Germans with 1 FighterAce, 1 armour, 2 bombers and 1 fighter remaining. Battle score for attacker is -2 Casualties for Russians: 2 armour Casualties for Germans: 1 ElitePanzer and 1 elite Battle in Evenkiyskiy Russians attack with 1 armour and 1 elite Japanese defend with 1 mech_infantry Russians roll dice for 1 armour and 1 elite in Evenkiyskiy, round 2 : 0/3 hits, 0,83 expected hits Japanese roll dice for 1 mech_infantry in Evenkiyskiy, round 2 : 0/1 hits, 0,33 expected hits Russians roll dice for 1 armour and 1 elite in Evenkiyskiy, round 3 : 2/3 hits, 0,83 expected hits Japanese roll dice for 1 mech_infantry in Evenkiyskiy, round 3 : 0/1 hits, 0,33 expected hits 1 mech_infantry owned by the Japanese lost in Evenkiyskiy Russians win, taking Evenkiyskiy from Japanese with 1 armour and 1 elite remaining. Battle score for attacker is 4 Casualties for Japanese: 1 mech_infantry Trigger Remove All ItaliansParaBoost: has removed 1 italian_paraBoost owned by Italians in Rhodesia Non Combat Move - Russians Trigger ItaliansParaBoost atRhodesia: Italians has 1 italian_paraBoost placed in Rhodesia Trigger RailMovementAutoPlaceRemoveRussians: has removed 1 Russian_Rail owned by Russians in Russia Trigger RailMovementAutoPlaceRemoveRussians: has removed 1 R_Europe_Rail and 1 Russian_Rail owned by Russians in Urals Trigger Remove All RussiansParaBoost: has removed 1 russian_paraBoost owned by Russians in Iraq 1 bomber moved from Novosibirsk to Russia 2 bombers moved from Eastern Poland to Russia 1 fighter and 1 tactical_bomber moved from Baltic States to Belarus 1 FighterAce and 1 fighter moved from Eastern Poland to Belarus 4 infantry moved from Bryansk to Belarus 2 infantry moved from Rostov to Bryansk 3 infantry moved from Volgograd to Rostov 1 elite moved from Bryansk to Belarus 3 armour moved from Russia to Belarus 1 R_Europe_Rail and 1 elite moved from Russia to Urals 1 Russian_Rail moved from Russia to Karelia 1 Russian_Rail and 1 infantry moved from Karelia to Urals Place Units - Russians 1 Soviet_Partisan, 1 TankDestroyerFS and 1 elite placed in Russia 3 infantry placed in Karelia 3 infantry placed in Bryansk 3 infantry placed in Volgograd 1 infantry placed in Russia Turn Complete - Russians Trigger RussiansParaBoost atSlovakia Hungary: Russians has 1 russian_paraBoost placed in Slovakia Hungary Trigger RussiansParaBoost atIraq: Russians has 1 russian_paraBoost placed in Iraq Russians collect 35 PUs; end with 35 PUs Objective Russians 2 Spread Of Communism: Russians met a national objective for an additional 9 PUs; end with 44 PUs Combat Hit Differential Summary : Japanese regular : -0,33 Germans regular : 0,33 Russians regular : 1,17 exp-game-10-straw-r-12.tsvg

@trout Have you updated triplea and switched to the new dice server ? Here are the links again. Let me know if you are having trouble. New triplea https://github.com/triplea-game/triplea/releases/tag/2026-06.16.15640 New Dice Roller https://dice.triplea-game.org/ You will need to confirm your Dice registration in your email. When you install the new triplea I would just overwrite what you have. Don't need the old ones anymore. Edit You can also download from the Home Page now. The new triplea https://triplea-game.org/

@malmessi post the save here maybe we can provide additional insight

@RogerCooper Yea I haven't looked at the new map process closely yet. I have updated a preexisting map twice and both times it has updated to the latest in the lobby fwtiw

@drumstick919 @lafayette i’m wondering if this might have something to do with the new skin engine?

@Kindwind Any further progress on this. I would like to see a report of an actual game. Even seeing the first turn would be enough to see whether you are getting somewhere. Note that OOB Axis & Allies 1942 (2nd edition) strongly favors the Axis. It would be better to use the Larry Harris alternate setup.

@beelee I got rid of all the TripleA versions on my comp.....6 in total. the latest was from 2023 The error message looks different, but more clearly. Seems that Mr. Trout needs to register to the ne dice server. [image: 1781815998065-c6f3d83f-7d00-4267-a7ff-e85fd6f1c41e-image.jpeg]

Update to 2.58 [image: 1781724459933-screenshot-from-2026-06-17-14-26-44.png]

@JohnnyCat 354345234988-G40 EXP StevenJ vs JohnnyCat G56c End.tsvg RIP Japan

@GREGOREK You are bonkers trying to shoehorn a RPG style into TripleA. However I will join you in the Bonkers club, for I have thought of trying to do similar. For your consideration look at https://forums.triplea-game.org/topic/3264/arena-of-death-official-thread for multi wound heroes and different classes. For the levelling of the heroes a Tech tree could be used, see, each tree could be a hero? https://forums.triplea-game.org/topic/4056/1888a-steam-steel-official-thread For random distribution of monsters and treasures, see https://forums.triplea-game.org/topic/3666/shogun-advanced-official-thread and look for Kami, Japanese spirits. The Kami start out with lots of dots in their unit name, this so the player cannot count them, when found/revealed they change into stuff Ebbe and I are working on an Heroic FFA island map with Fates, using the ./dot principles above.

I like Darcula - except the politics panel - those colours are a pain, indeed.

@RogerCooper The wiki option was looked at some time ago, you may recall the thread. 'fandom' uses an older wiki syntax and would make a transition to it not awesome. We'd have to rewrite all of our docs in the that syntax. Axis and Allies meanwhile is a trademarked term owned by Hasbro and we can not, should not, have anything official for TripleA that is associated with that trademark. Hosting our documentation under a URL with a trade marked term that we do not own could create an incorrect perception of an affiliation.

I can confirm that it downloads fine now. That already was a good example for the workflow. Thank you

I suppose it is worth pointing out that a 'revert' in git is just an undo update. The code history in Git is write-once. Git never deletes anything. So, in a revert update, based on the reverted change: any lines that were added are removed, and any removed lines are re-added. So, a revert is a new update, it just an inverted update to cancel out a previous one. Revert PRs are not at all special to Git, it's just another update. Once a revert is merged, a person can revert the revert update, add more changes to it, and then merge all of that as one bundle. So, a flow might be like this (the letters on the left hand side represent the commit ID, AKA the commit SHA): a43ae Some update that introduced a bug 3ads2 Revert: Some update that introduced a bug fae54 Revert: Revert: Some update that introduced a bug + Bug Fix Changes to the code base are "squashed" together. When a person clicks the revert for the revert, that creates a new proposed change. Bug fixes can be added to that proposed change, then it'll all be squashed together as a single commit that is then released. For example, when reverting the revert, this change would be proposed: abc12 Revert: Revert: Some update that introduced a bug In that proposed change, we can add the bug fix, eg: abc12 Revert: Revert: Some update that introduced a bug fea23 Bug fix Then, when merged, that would land on the main branch and in the history as one commit, eg: fae54 Revert: Revert: Some update that introduced a bug + Bug Fix