What if we keep the past as is for a while, but provide the new structure for new maps, new blender models etc. ? (Mods are already hosted on mod.io so they are managed elsewhere.) Many maps and models of the past are either already part of the current release version, some are part of a mod (community maps, delenda est etc.), and a third group is abandoned. I believe we could put up a map repository thread underneath the Game Modification | ScenarioDesign/MapMaking . We could subsequently copy (or link) converted old maps there.

I suppose, it needs a PR

Apologies, had to fix one important thing and update to Mercator 0.17.0 . It holds everything of 0.16.0 (the lock on the versions of a map, The whole map refused when it would mix two versions, the tidied code) and one thing more: each Edit in Mercator started another Mercator, and each Check or convert in post-Atlas another post-Atlas. The new version is available from the initial post ofd this thread in  https://wildfiregames.com/forum/topic/169940-new-atlas-helper-tool-mercator/ New The tools switch between their running windows. If the other tool is open, the map is sent to it and its window comes forward; a new copy is started only when none runs. Keep both open for the whole project. A tool that is open when the other saves the map reads it again when you come back to it. With nothing unsaved in the window it simply follows the files and says so in the status bar; with unsaved work it asks which side wins, once for each change. (Not while the map is with Atlas: the hand-over follows its return.) What to try Open a map in Mercator, choose Check or convert in post-Atlas... on the Summary tab, fix something there, and switch back: Mercator should show the map as post-Atlas left it. Then Edit in Mercator in post-Atlas again - it should bring the open Mercator forward, not start another. Try it with unsaved changes in the window you come back to. The windows are not locked against each other yet: if you edit the same map in both at once, the one you come back to asks - please say what you saw. Needs atlas-common 1.19.0 (included). post-Atlas 1.19.0 goes with it.

Had to fix and update to post-Atlas 1.19.0, with atlas-common 1.19.0 (Mercator 0.17.0 goes with it). It holds everything of 1.18.0 and one thing more, from testing: each Edit in Mercator started another Mercator instance (and vice versa).  New The tools switch between their running windows. Convert > Edit in Mercator sends the map to the Mercator that is open and brings it forward; a new Mercator is started only when none runs. Mercator's Check or convert in post-Atlas... does the same the other way. post-Atlas checks the map again when you come back to it after Mercator saved it (not while a job runs or the map is with Atlas). It writes at once, so there is nothing to ask. What to try Keep both tools open on one map, save in Mercator, switch to post-Atlas, and check that the findings are those of the saved map; fix something, switch back, and check that Mercator shows it. If something differs from 1.18.0, please say what you did and what you saw. post-atlas-1.19.0.zip README.md CHANGELOG.md

Can we include this in R29?