Doc: Map Population on website and download list
-
@LaFayette An error message should go out if there is a non-unique map name in any map.yml
-
@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.
-
L LaFayette moved this topic from Maps & Mods
-
@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.
-
I would like to go back to the old system of having a distinct "mapName".
FWIW, the old system didn't enforce a unique map name. Windows has a case insensitive file system, and because the old system tied the map name to the folder name, you couldn't install two maps with the same name without overwriting. Except, there still was no guarantee that globally across all maps, that the names were unique. Mac and Linux have case sensitive file names, so in the old system you could still have a duplicate name installed so long as the casing was different. Using 'mapName' overall is essentially the design flaw.
-
@LaFayette Can I definitely stop updating triplea_map.yaml?
-
@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 pageI would like to see the reason why and try to fix them
1888A Steam and Steel for one. -
You'll notice the table contains essentially all of the the same data fields that the previous 'triplea_maps.yaml' contained.
Is the triplea_maps.yaml still needed - for which purpose?
Or can it be removed? -
I think the yaml has already been removed.
-
I think the yaml has already been removed.
It's not used any longer, but still there (Screenshot from seconds ago):
-
Oh well .. yea I stand erected
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login