Split map_cache.dat into PRE-RE and RE

Originally posted by [b]JoWei[/b]
I don't think that's necessary since your server will be set either for PRE-RE or RE while clients have either files for old Alberta and/or old Izlude or new Alberta and/or new Izlude.
Further more, I don't think there's servers out there that keep switching between RE and PRE-RE except during testing phases because switching map cache would mean you will have to update client side files to keep files matching with server file caches anyways.

Originally posted by [b]EvilPuncker[/b]
bump since I'm often seeing topics in support section about ppl being stuck

Originally posted by [b]Judas[/b]
may be a good idea

Originally posted by [b]JulioCF[/b]
level up

Originally posted by [b]Vianna[/b]
I think it would be nice to have an option to let people choose, for instance, to keep the new Izlude but not the new Alberta without recreating the mapcache.
Something like a version flag in the map entry. And map_index.txt could look like

[code]// map[ re/pre-re/default][ index]
alberta re 0
yuno
einbroch
einbech
izlude pre-re
eclage
prontera default 1500[/code]
With RENEWAL_MAPS set, alberta, eclage and prontera use their renewal versions; izlude use it's renewal version; and yuno, einbroch and einbech fallback to their pre-renewal versions because there are no renewal versions of them.
With RENEWAL_MAPS not set, alberta will use it's renewal version; eclage will be deleted because there's no pre-renewal version; and yuno, einbroch, einbech, izlude and prontera will use their pre-renewal versions.

Originally posted by [b]EvilPuncker[/b]
fixed in 16867

Originally posted by [b]Ind[/b]
thank you for bringing this report up, EvilPuncker

Originally posted by [b]kyeme[/b]
Im trying to update my mapcache. But after the update, the [b]map_cache.dat [/b]directory creates in [b]trunk\db\[/b] not in [b]trunk\db\re[/b] (renewal mode)

Originally posted by [b]Ind[/b]
Fixed in [rev=16884] Thank you keyeme!