Brandon Slade
Assigned
Reported
Comments
Not really.
If they update 1.6.2 to 1.6.3, with a quick fix to save the structures, there are two problems. What if people skip 1.6.3, and go straight to 1.7? And even if they don't, what about the 1.6.2 maps that people don't open in 1.6.3, but they come back to it later?
If they "convert" the chunks on first load in 1.7: yes, technically they could do this, but this is neither a simple or a quick fix. It's probably a good idea to do it anyway, and it will need to be done at least once in preparation for the MCAPI, but unless Mojang is planning on doing much more extensive changes in 1.7 than they have already done, (and they have made some extensive changes,) it will most likely not be worth it.
This is not as simple a fix as people are saying. 1.6.2 is already out; any fix would only apply in the snapshots and future versions.
So while this could be fixed for 1.7, you will still not be able to keep the structures generated for 1.6.2 and before. All it means that when Minecraft changes in the future, structures generated in 1.7 will be preserved.
Sorry... 😞
I did search, I just searched for the wrong things, and apparently not for long enough.
@VasilBochev: This isn't a problem with rendering; it is a problem with client/server communications. The new rendering system will not remove this problem or make it obsolete.
They do save the biome data; and as for the structures, I suppose that they could keep some sort of "version" tag attached to each chunk, which may help decrease the load when converting the world, but that's asking for trouble, don't you think? (Not only are there different world save formats, but now a single save can contain data in many different formats.)