Map naming and versioning
Hi, I’m porting some maps from Tremulous but I don't want to do mistakes.
1. Versioning
Unvanquished allows us to versionize pk3, which is a good thing. So we have for example:
Code: Select all
map-plat23_b13+1.pk3
map-spacetracks_1.0+1.pk3
map-station15_1.0.pk3
Is a future map-plat23_1.0.pk3 will supersede map-plat23_b13+1.pk3, unless b13+1 > 1.0 on a “sort” side ?
Some maps from Tremulous were previously versioned trem, for exemple : map-orion_trem+2.pk3.
So, when I updated them, I just increased the number, for example map-orion_trem+3.pk3, keeping the trem part since trem is a very high “number”.
The problem is here: if someone wants to update them, he must keep this “high number”.
So, for maps that already have this versioning, it's too late since some servers and players already uses it, but what to do for other maps? For example I have fixed right now another map. Which version I must give? “trem” is not a good Idea, imagine if the mapper wants to update it in the future, he will be forced to use the silly versioning I used before him (and will be angry against me).
I must use a version the mapper can update after I ported his map.
2. Naming
On the other hand, I like the _trem versioning because it shows if the map is the tremulous version or an Unvanquished map, for example see map-spacetracks-r1_trem+1.pk3 tremulous map and the updated official map-spacetracks_1.0+1.pk3. It's nice.
What do you think about using a trem- prefix while naming maps from Tremulous?
For example, the map map-vega-beta1.pk3 from tremulous can be named map-trem-vega_b1.pk3, and in server list, called trem-vega, so the user knows he is voting for a trem map.
If the mapper wants to update it officially for Unvanquished, the new one will be named map-vega_1.0.pk3 for example, so there will be no conflict between the map I ported, and the map he improves, even if the version number of the ported map is higher than the version number of his official release for Unvanquished.
For example, I will be able to rename map-meep_trem.pk3 to map-trem-meep_b2+1.pk3, (map name: trem-meep), so I can reset the versioning with a meaning one, without conflicting with the _trem versioning. What do you think about it?
3. Defining good practices
The idea is to define good practices now to prevent future mess, before more people try to port and create unofficial maps for Unvanquished.