Hello everyone yesterday I loaded my survival world and it took quite a while to load successfully (~ 3-5 minutes), when i got into the world i found some really odd misplaced chunk areas (check out the screenshots in the attachments to see better).
I am really afraid the same thing will happen to my base area, so please explain why this happened and show me how to fix or recover the world if it continues to occur. Thank you
If you know where the misplaced chunks belong you could probably use MCEdit or something to move them back but the best thing would be to take regular backups, preferably on a USB-drive or online/network drive, just in case.
Don't worry, this is a bug they currently have. Mojang has already spotted this, so in the official 1.9 update, this glitch should be patched. Have a good day
Don't worry, this is a bug they currently have. Mojang has already spotted this, so in the official 1.9 update, this glitch should be patched. Have a good day
He doesn't say what version he's playing. If it is 1.8 I've never encountered this. From past experience usually this means there is some world corruption. Often this will happen if the game crashes or the power goes out while your playing. The world doesn't save properly and chunks start getting messed up or regenerated.
It is odd that it looks like the chunks that I'm assuming regenerated look like a different biome than the savannah nearby. Was the world generated in a version prior to 1.7?
He doesn't say what version he's playing. If it is 1.8 I've never encountered this. From past experience usually this means there is some world corruption. Often this will happen if the game crashes or the power goes out while your playing. The world doesn't save properly and chunks start getting messed up or regenerated.
It is odd that it looks like the chunks that I'm assuming regenerated look like a different biome than the savannah nearby. Was the world generated in a version prior to 1.7?
I am playing 1.8.4 and generated the world in 1.8.4 too. I dont think the chunks you mentioned was regenerated, but rather misplaced, because i found a chunk in a plain biome nearby that looked exactly like the one in the savannah biome. Back when i played in 1.7, chunks used to swap for each other, but this time the world is generating copies of one chunk and then place it in the wrong position. I have another screenshot to show you this (check attachment: the floating platform on the right is a 'misplaced copy' of the one on the left)
I've only had this happen during a complete power outage. The game will generally still save correctly after a simple crash but a complete power outage that also shuts down your computer will give you some problems.
This is what happened during such a power outage on my world, I've dubbed it "Glitch Peak".
It's actually a nearby chunk(less than 10 chunks away) which was superimposed to where it now sits. The original terrain is still in it's proper chunk but has simply been copied. You can also see a slight bit of netherbrick on the left side of the screen where another chunk was also superimposed.
Quote from rodabon »
It is odd that it looks like the chunks that I'm assuming regenerated look like a different biome than the savannah nearby. Was the world generated in a version prior to 1.7?
I've seen all kinds of crazy things happen with power outages, chunks do not always regenerate. I've actually never had them regenerate come to think of it... During power outages something always ends up superimposed, swapped, or completely missing.
Rollback Post to RevisionRollBack
Quote from Swingerzetta »
This forum has made me decide that I now want kids, so that when they get old enough, I can forbid them from coming here. it's a terrible place.
It is possible to get chunk corruption even without crashes; for example, have you ever seen the following error in the game output (with obfuscated names, this was within MCP)?
java.io.IOException: Stream Closed
at java.io.RandomAccessFile.seek(Native Method)
at net.minecraft.src.RegionFile.setOffset(RegionFile.java:328)
at net.minecraft.src.RegionFile.write(RegionFile.java:253)
at net.minecraft.src.RegionFileChunkBuffer.close(RegionFileChunkBuffer.java:23)
at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:241)
at java.io.FilterOutputStream.close(FilterOutputStream.java:160)
at net.minecraft.src.AnvilChunkLoader.writeChunkNBTTags(AnvilChunkLoader.java:177)
at net.minecraft.src.AnvilChunkLoader.writeNextIO(AnvilChunkLoader.java:162)
at net.minecraft.src.ThreadedFileIOBase.processQueue(ThreadedFileIOBase.java:39)
at net.minecraft.src.ThreadedFileIOBase.run(ThreadedFileIOBase.java:27)
at java.lang.Thread.run(Thread.java:724)
That's due to poor coding; specifically, the internal server runs on a separate thread and the client does not wait for it to shut down before you can load another world, the same world (which causes massive corruption/overwritten chunks and save errors), or quit the game.
The fix is also incredibly simple, one that Forge added to the game long ago (that's why it displays "Shutting down internal server" when you quit), and I've added to my own mods:
if (this.theIntegratedServer != null)
{
this.theIntegratedServer.initiateShutdown();
if (loadingScreen != null)
{
this.loadingScreen.resetProgresAndWorkingMessage("Shutting down internal server...");
}
while (!theIntegratedServer.isServerStopped())
{
try
{
Thread.sleep(10);
}
catch (InterruptedException ie) {}
}
}
Here are some bugs that result from this improper shutting down:
And others, including no doubt many causes of world corruption since improperly shutting down the internal server is not much different from pulling the plug on your computer. In fact, the first error that I posted says it failed to write the offset to a chunk, which tells the game where the chunk is located within a region file - presto, a chunk that is now in the wrong location (likely accompanied by errors about a chunk being in the wrong location and being relocated, or possibly not since that error occurs for different reasons, when the actual x and z coordinates don't match).
For example, this (MC-15820) occurred when I saved and quit and reloaded a world before the internal server instance from the first session had shut down (note that only one instance of the game was running, the errors in the console are usually associated with two or more instances open and accessing the same world at once):
With the simple fix I provided the internal server has to fully shut down before you can access the main menu, completely avoiding this problem unless the game is force-quit or the computer crashes/shuts down.
Hello everyone yesterday I loaded my survival world and it took quite a while to load successfully (~ 3-5 minutes), when i got into the world i found some really odd misplaced chunk areas (check out the screenshots in the attachments to see better).
I am really afraid the same thing will happen to my base area, so please explain why this happened and show me how to fix or recover the world if it continues to occur. Thank you
I build stuffs like the cathedral in my avatar
Check out my survival journal if you want :
Part 1
http://www.minecraftforum.net/forums/minecraft-discussion/survival-mode/2485490-duythemcers-ssp-journal
Part 2
http://www.minecraftforum.net/forums/minecraft-discussion/survival-mode/2704381-duythemcers-survival-singleplayer-journal-part-2
I don't know enough to say why that happens.
If you know where the misplaced chunks belong you could probably use MCEdit or something to move them back but the best thing would be to take regular backups, preferably on a USB-drive or online/network drive, just in case.
Just testing.
Don't worry, this is a bug they currently have. Mojang has already spotted this, so in the official 1.9 update, this glitch should be patched. Have a good day
He doesn't say what version he's playing. If it is 1.8 I've never encountered this. From past experience usually this means there is some world corruption. Often this will happen if the game crashes or the power goes out while your playing. The world doesn't save properly and chunks start getting messed up or regenerated.
It is odd that it looks like the chunks that I'm assuming regenerated look like a different biome than the savannah nearby. Was the world generated in a version prior to 1.7?
by c0yote
I tried it with terrible results. I gave my wife my glasses for a second, a creeper showed up and now my wife is pregnant.
Stupid 3D..
I am playing 1.8.4 and generated the world in 1.8.4 too. I dont think the chunks you mentioned was regenerated, but rather misplaced, because i found a chunk in a plain biome nearby that looked exactly like the one in the savannah biome. Back when i played in 1.7, chunks used to swap for each other, but this time the world is generating copies of one chunk and then place it in the wrong position. I have another screenshot to show you this (check attachment: the floating platform on the right is a 'misplaced copy' of the one on the left)
I build stuffs like the cathedral in my avatar
Check out my survival journal if you want :
Part 1
http://www.minecraftforum.net/forums/minecraft-discussion/survival-mode/2485490-duythemcers-ssp-journal
Part 2
http://www.minecraftforum.net/forums/minecraft-discussion/survival-mode/2704381-duythemcers-survival-singleplayer-journal-part-2
I've only had this happen during a complete power outage. The game will generally still save correctly after a simple crash but a complete power outage that also shuts down your computer will give you some problems.
This is what happened during such a power outage on my world, I've dubbed it "Glitch Peak".
It's actually a nearby chunk(less than 10 chunks away) which was superimposed to where it now sits. The original terrain is still in it's proper chunk but has simply been copied. You can also see a slight bit of netherbrick on the left side of the screen where another chunk was also superimposed.
I've seen all kinds of crazy things happen with power outages, chunks do not always regenerate. I've actually never had them regenerate come to think of it... During power outages something always ends up superimposed, swapped, or completely missing.
The BEST way to mine diamond, layer 12 and you.
It is possible to get chunk corruption even without crashes; for example, have you ever seen the following error in the game output (with obfuscated names, this was within MCP)?
That's due to poor coding; specifically, the internal server runs on a separate thread and the client does not wait for it to shut down before you can load another world, the same world (which causes massive corruption/overwritten chunks and save errors), or quit the game.
The fix is also incredibly simple, one that Forge added to the game long ago (that's why it displays "Shutting down internal server" when you quit), and I've added to my own mods:
Here are some bugs that result from this improper shutting down:
MC-10976 Single player: "java.io.IOException: Stream Closed" when quitting game
MC-315 Chunks do not delete properly remaining in a newly created world if the same world name is reused
MC-15820 Reloading a world during terrain generation causes some parts of the world to be generated in stripped parts
And others, including no doubt many causes of world corruption since improperly shutting down the internal server is not much different from pulling the plug on your computer. In fact, the first error that I posted says it failed to write the offset to a chunk, which tells the game where the chunk is located within a region file - presto, a chunk that is now in the wrong location (likely accompanied by errors about a chunk being in the wrong location and being relocated, or possibly not since that error occurs for different reasons, when the actual x and z coordinates don't match).
For example, this (MC-15820) occurred when I saved and quit and reloaded a world before the internal server instance from the first session had shut down (note that only one instance of the game was running, the errors in the console are usually associated with two or more instances open and accessing the same world at once):
With the simple fix I provided the internal server has to fully shut down before you can access the main menu, completely avoiding this problem unless the game is force-quit or the computer crashes/shuts down.
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?