if the server and editor included a converter, it wouldn't be a big deal
the most important benefit would be extendability I think
however, one could try to improve the current format to be more extendable as well
@Dune It won't make the update unpopular except for a couple goofs trying to make a statement. If the major mods move along, so will the community. The players don't care what the map format is
0.8 will already be network incompatible, so a map format upgrade would really not matter for the players. ddnet can break map compatibility right now if backwards compatibility wasn't a concern
16:51
Besides a converter being bad is not evidence that all converters are bad
16:52
Through proper testing, we could make a conveter that does not suffer from issues of the past
Again, seems reasonable. Maps for the most part are hosters concern. Also having a converter that deal with map version does sounds better than having both servers and clients to deal with versions.
@Learath2 you say that, yet tileset compatibility was a huge problem in 0.7, so unless there is a very accessible and visible solution to convert maps there is no reason 0.8 would be any different
Well I don't really know what you changed between 0.6 and 0.7 about the tilesets but the proposed changes to the map format would all be restructuring. As long as the client unpacks the thing correctly I don't see how any issue can occur
17:02
Besides any mistake we make will be quite obvious when ddnet migrates the hundreds of maps we have. We had tileset and quad issues too when making our 0.7 converter and it took like a week to iron out the mistakes. Community size really helps with testing
Isn't having the converter directly in server the point of being accessable? Just have the any version of map loaded and the server does the magic auto magically.
So it is just me or do our conversation sometimes goes in circles where everyone is having the almost the same idea but still having an argument back and forth.
Right. If we can find a way to identify 0.5 maps then we can assume the tileset. If not, we don't have to support 0.5 tilesets, like Learath2 said, there aren't many that haven't been ported and still being used.
17:23
Also I think most mods doesn't change the standard part so vanilla clients can read it.
17:23
For vanilla server I think it is enough to simply deal with the part we know.
17:24
Devs that does format extension will definately have their own solutions.
I think Learath2's idea is to identify the version when doing the convertion for future tileset update, we can always just load the existing ones if the hash does trigger the map converter
Enough of this hypothetical that will never happen. Realistically we'll be stuck with undefined behaviour, unextendable map format and an unextendable datafile format for the forseeable future
I wish we can have a hash that can describe the tilesets formations tho. But I'm probably just imagining, since we don't have that data anywhere to hash.