Greetings! I have just downloaded the 1.3 pre, and I have been trying to setup a new decent world for me and my little 7 year old cusion to play on.. However, while doing this I have noticed many chunk errors, I have started roughly 9 worlds and pretty much all of them have terrain like this... Does anyone know how to fix it, or is this just a normal bug?
Edit: Note, this is all new world, not an old world changed into a new.
I was able to recreate something like this. May not be this though. Just a hypothesis.
I recreated it by deleting the dat files that were used to generate the world. I did this on a server . Not in singleplayer. I didn't completely delete the world folder. So next time it created a world it had errors.
My thought is that it might be a security program doing this. Something may be keeping files from changing or saving at all.
I was able to recreate something like this. May not be this though. Just a hypothesis.
I recreated it by deleting the dat files that were used to generate the world. I did this on a server . Not in singleplayer. I didn't completely delete the world folder. So next time it created a world it had errors.
My thought is that it might be a security program doing this. Something may be keeping files from changing or saving at all.
The initial posting that you included looks like two biomes (forest and ...?) unexpectedly bumping into each other, without any transition. That's a fairly typical chunk error. The one that you manufactured is different, more like a translation of that sliver of land up about 8 blocks.
Rather than trying to manually create the error, just run test worlds and see if you find another chunk error, then post both seed and location for it. If other people see the same problem on their machines, it's not at your end.
When will terrain generation be without errors and definitive?
Amazing how people are always complaining about the terrain being "predictable" and how it needs to change, but when it does change or does something unexpected, they STILL complain.
Rollback Post to RevisionRollBack
The Internet is a big place, friend. I've been places you've n͍̺e̩v̦e̦̰͍͓̩ͅr̜̭̝̬̬͉̤̬ ͙ịm̖͇a͍͇̤͙̥g̤̘i͔͖̤̼̪̬n͖͔̳̬̯e̩̘ḓ͈͔̠̙͇̼̯.͎
I happen to think terrain errors like this are pretty fun to mess around with. I like to make large houses built into them when I find them, they make for a fantastic view of the surrounding area. However, they are errors, and shouldn't generate.
These things have a chance of happening if you delete a world and then create a new world with the same name shortly after. The faster you are the more probable it is to happen. It might also happen if you exit Minecraft shortly after deleting a world because that also prevents the game from cleaning the save folder.
It happens if there are still remains of an old world on your disk even if you can't select it in the world selection menu. When the World generator sees that there are files there already it believes that it has already generated those chunks during a previous run.
Either give the game plenty of time to clean up the save folder properly or delete the world folder manually to make sure the world is properly gone before reusing the name for a new world.
Edit: Note, this is all new world, not an old world changed into a new.
I recreated it by deleting the dat files that were used to generate the world. I did this on a server . Not in singleplayer. I didn't completely delete the world folder. So next time it created a world it had errors.
My thought is that it might be a security program doing this. Something may be keeping files from changing or saving at all.
"Shall we play a game?" - Joshua
Agreed.
The initial posting that you included looks like two biomes (forest and ...?) unexpectedly bumping into each other, without any transition. That's a fairly typical chunk error. The one that you manufactured is different, more like a translation of that sliver of land up about 8 blocks.
Rather than trying to manually create the error, just run test worlds and see if you find another chunk error, then post both seed and location for it. If other people see the same problem on their machines, it's not at your end.
Amazing how people are always complaining about the terrain being "predictable" and how it needs to change, but when it does change or does something unexpected, they STILL complain.
...but that's just like, my opinion, man.
It happens if there are still remains of an old world on your disk even if you can't select it in the world selection menu. When the World generator sees that there are files there already it believes that it has already generated those chunks during a previous run.
Either give the game plenty of time to clean up the save folder properly or delete the world folder manually to make sure the world is properly gone before reusing the name for a new world.
I had a similar chunk error (seed: resturgence, coordinates x 525, z 625, but stretches for a decend length!)