Took a detour on game development and added a dungeon module to the automated scripts with dirt, rubble, water, and of course lava.

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.

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

It takes a little while for the support server to come back to re-index the map. I updated the DB directly to speed that process up, should appear fixed now.

triplea_support_server=# select map_name from map_index where repo_url = 'https://github.com/triplea-maps/ww2v5_variants'; map_name ---------------------- world_war_ii_v5_1942 (1 row) triplea_support_server=# update map_index set map_name = 'ww2v5_variants' where repo_url = 'https://github.com/triplea-maps/ww2v5_variants'; UPDATE 1 triplea_support_server=# select map_name from map_index where repo_url = 'https://github.com/triplea-maps/ww2v5_variants'; map_name ---------------- ww2v5_variants

@LaFayette This is really odd. The link in triplea_maps.yaml is correct

url: https://github.com/triplea-maps/world_war_ii_v5_1942/archive/refs/heads/master.zip

And here it is on GitHub

I see that @DanVanAtta just made some changes to ww2v5_variants, so maybe he has already fixed the issue.