@LaFayette said:
It's on my roadmap to create a HTML status page so we can see the status of map indexing. If a new duplicate map_name is introduced then that status page would reflect the error. I'm not sure if we have to disable the duplicate entirely.

That sounds like a good solution.

If we are changing things, I would like to go back to the old system of having a distinct "mapName". That way, if a mod uses an existing map, there would be no need to copy all the map files over.

@RogerCooper How, when and where to flag that error message are all open questions. My thoughts on how to solve that - It's on my roadmap to create a HTML status page so we can see the status of map indexing. If a new duplicate map_name is introduced then that status page would reflect the error. I'm not sure if we have to disable the duplicate entirely.

Similarly it's on the roadmap to use IDs as well instead of map names. In which case the map name would appear duplicated in download maps, but the description would be unique and the download would download the right thing.

I'd even like for each map to be stored under its commit-ID on disk as well, then TripleA could finally have a concept of different map versions. Another flaw in TripleA's map handling design is TripleA assumes not only that the map name uniquely identifies a map, but that there is actually just one and only one version of that map.

If TripleA used Map-ID + Commit, TripleA could have multiple versions of a map installed, could use the right one, and could precisely and always download the correct version as needed.

With all that said, the status page is pretty high priority compared to everything, the indexing is an opaque process right now.

@LaFayette An error message should go out if there is a non-unique map name in any map.yml

@RogerCooper Another aspect to duplication of 'map.yaml' - when we fork the repo into 'triplea-maps', (we being the map admins), the map admins should check that 'map.yml' has been updated.