@LaFayette Please list the urls for the error reports, as; Some of the maps from GitHub map repositories are not making it to the Map Server map listing page I would like to see the reason why and try to fix them 1888A Steam and Steel for one.

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

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

@VictoryFirst Oh ? I hadn't noticed that with Dracula. I like the slightly larger Font as the latest old one I could barely read I guess it's hardwired into the w/e it is that does it then I just thought Dracula sounded cool so I tried it lol

@Alexander I will try registering my second email. It's a proton as well. See what I get. I haven't heard back from Panzer but the rolls went through. Previously it would throw a error if your opponent wasn't registered when you rolled the battle. @trout I would go here and register and see what happens https://dice.triplea-game.org/ Edit I just registered my protonmail and didn't get any error message. So Idk what's up. I guess we'll just have to see if it works for you guys. I might try a test game with my gmx mail and see if it works Edit 2 Looks as if the Dice Registration error has been fixed. I tried to reregister and it said I was already registered. So I suspect you and Panzer are too. You can try it and see what it says. Edit 3 Back working on the ABomb. Looks as if it drifted off target a bit [image: 1781621730664-screenshot-from-2026-06-16-09-53-53.png] hmm 2nd one was offshore a little bit. Lets see where number 3 ends up [image: 1781622131252-screenshot-from-2026-06-16-10-01-04.png] [image: 1781622393135-screenshot-from-2026-06-16-10-05-57.png] OK I'll quit spamming our Game Well just one more Looks as if the Reich has improved their targeting system [image: 1781625670820-screenshot-from-2026-06-16-10-59-09.png]

@Nothingtoseehere hey there didn’t really have any time to look at my move today tomorrow is screwed too but i think i know what i need to do so should be able to have it ready for spain on wednesday (for me)

@stevenJTripleA G40 EXP StevenJ vs JohnnyCat A54End.tsvg

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

Took a detour on game development and added a dungeon module to the automated scripts with dirt, rubble, water, and of course lava. [image: 1781619320183-tripleacave.png] Ya'll have made TripleA diverse and feature rich. A cave system brings up some questions. Please educate me if these adaptations already exist. Otherwise, please consider their addition/discussion. Remember, you are making a toolbox, not a game; that's for the map makers. And they need more tools. A dungeon crawler could be played by standard tripleA territorial battles. However, it would be more open to RPG style with specialized units and item distribution. Not trivial upgrades but some form of menu system is required to add and remove found items to units. Tech/triggers affect all units of a type. I dont expect DOOM style gaming, but some form of treasure hunt would be nice. Currently, a single hero-unit could satisfy the RPG side of the game, absorbing all found items. The Production Menu is a sore spot. It needs greater control by the map. The engine provides a default, but let the map override it with col/row size and access (add/replace cells by col/row). Treat it like the table it is with Rules and Notes. A specialized Rule could allow item distribution but would wreak havoc on the battle calculator and battle menu to have so many unique units. Relief Tiles remain as the default display, but consider a territory tile with x,y alignment offset. It might ease the burden of border/corner overlaps on fully wrapped XY maps. It would also usher in territory animations and unleash the FOG OF WAR. Current script status is close to release. They will generate random terrain and cave maps along with a generic game.xml to hog out the bulk of the work. Finished speeding up the territory carver that works like a bubble machine. It tracks terrain changes reasonably well. The tricky bit remains narrow edges and corner horns/spear like structures. Mostly cleaned up. Dungeon module running slow. It be nice to integrate both surface and subterranean maps together for a 3Dish stacked hive affect but access points would require a lot of scrolling.

@TheDog You might get more bang for your buck by deleting the 'Xmx' and 'Xms' memory settings. The lobby window will occupy 4GB and then any game you launch will occupy another 4GB. Each game is its own instance, the memory settings AFAIK carry over. Generally Java uses very good defaults, so overriding those defaults can hurt. Specifically 'Xms', which is a minimum, so you're forcing the lobby window and any game to initially take more memory than it would need. I would personally set 'Xms' at 500m or remove entirely to let the JVM handle it. If we find some really good tunings, we can adopt those settings to be more built in. FWIW, Moon-Man was doing some experimentation with JVM settings here: https://github.com/triplea-game/triplea/discussions/14467