MC-32622Major chunk errors when switching from 1.6.4 to 13w18c
I read the snippet about update 1.6.4 and about how I should load worlds with it before I play with 1.7. I updated and created a world, then x-ed out and loaded up Minecraft again, except with snapshot 13w38c. I got into the world I had made and I was burried in dirt. I was in an ocean before and now i was swimming in dirt (and drowning in it XD). I got out of that and looked around and there were huge chunk errors in many places. I tested this with a few other worlds (create in 1.6.4 and then play in 13w38c) and it seemed to have the same effect, though not always did the chunk errors happen near. Some happenned at the very edge of the loaded chunks i had loaded in 1.6.4. This may just be from changing between them but still needs to be fixed.
Environment
intel i5 + integrated graphics, 6 gigs ram, windows 8, java latest update
Linked Issues
Created Issue:
Major chunk errors when switching from 1.6.4 to 13w18c
I read the snippet about update 1.6.4 and about how I should load worlds with it before I play with 1.7. I updated and created a world, then x-ed out and loaded up Minecraft again, except with snapshot 13w38c. I got into the world I had made and I was burried in dirt. I was in an ocean before and now i was swimming in dirt (and drowning in it XD). I got out of that and looked around and there were huge chunk errors in many places. I tested this with a few other worlds (create in 1.6.4 and then play in 13w38c) and it seemed to have the same effect, though not always did the chunk errors happen near. Some happenned at the very edge of the loaded chunks i had loaded in 1.6.4. This may just be from changing between them but still needs to be fixed.
Environment
intel i5 + integrated graphics, 6 gigs ram, windows 8, java latest update
Attachments3
![[Mod] CubeTheThird](../../../data/assets/gravatar/cubethethird.jpeg){kind=small}
is duplicated by
is duplicated by
is duplicated by
This bug is very similar to MC-32622, however, this world was created AFTER the 1.7 update and is showing the chunk generation errors. The world was created using the amplified generation technique, but I am unsure if that is the cause of this problem.
It is not exactly a bug. For this to be "corrected", the world generator would have to analyse all the previously generated chunks in order to mesh with them. This is impractical. For that reason this is considered working as intended. See MC-32622 for details.
Yeah... making this change look good would be practically impossible.
Duplicate of MC-32622
Yes this is the expected behaviour. Because of the drastic changes in the world generator, ungenerated chunks will load with the new one instead of the old one, creating the walls and separations that you see. The reason for the suggestion to use 1.6.4 before switching to 1.7 is for the generated structures to function properly.
ok well it makes for some fairly cool worlds with their own sense of extra uniqueness, and it makes exploring extra fun!
"One reason why we rarely do changes to the world generator is because every little change off-sets the world seed and causes noticeable borders between new and old terrain."
https://mojang.com/2013/08/minecraft-world-generator-update/