So I was on my map teleporting around when I saw a weird glitch. There was a chunk in the middle of the ocean that looked like terrain from another world I was playing on just a little while ago. No transition, just this chunk suddenly jutting out of the ocean. If you think I am making this up, just look at the attached screenshot of what I saw. What caused this, and does this only happen when generating new chunks?
It happens when you create a newer world with the same name as an older world you deleted. When you delete a world, you aren't actually deleting the save data and it's not actually gone forever like it says on-screen. Every single bit of your world data is still there on your computer, there's just no convenient way to access it via the Single Player index of worlds to choose from.
It happens when you create a newer world with the same name as an older world you deleted. When you delete a world, you aren't actually deleting the save data and it's not actually gone forever like it says on-screen. Every single bit of your world data is still there on your computer, there's just no convenient way to access it via the Single Player index of worlds to choose from.
That is not quite true; when the game deletes a save it is really deleted - the game means it when it says it is gone forever. However, because the client runs on a separate thread form the sever it is possible that the server is still running when you try to delete the world, which will fail because you can't delete a file that is in use; alternatively, the game deletes the region files and the server recreates them when it saves - note that the server thread says it is saving chunks just before the client tries to delete the world, which is still saving as seen by the lines about saving the Nether and End after the client's failed deletion attempt:
The fix for this is so obvious I have absolutely no idea why Mojang has not fixed it yet - make the client wait for the internal server to shut down before it can do anything else:
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) {}
}
}
this.theIntegratedServer = null;
With this code (originally take from Forge) I have never been able to reproduce this, or any of the other world corruption issues that this causes (not only does this cause issues with deleting saves, it lets you quit the game while the server is still saving - resulting in world corruption, which, among other things, includes swapping chunks (a chunk is copied form one area and moved elsewhere). I actually think that the OP may have experienced the latter since there is a single chunk by itself, while the deletion bug usually has more chunks (in vanilla the code above simply sets the server object to null immediately after telling it to shut down, which is like pulling the plug on your computer while saving; if you've ever seen a stacktrace starting with "java.io.IOException: Stream Closed" and referring to files in the game output when quitting a world this is what happened).
So I was on my map teleporting around when I saw a weird glitch. There was a chunk in the middle of the ocean that looked like terrain from another world I was playing on just a little while ago. No transition, just this chunk suddenly jutting out of the ocean. If you think I am making this up, just look at the attached screenshot of what I saw. What caused this, and does this only happen when generating new chunks?
Check out my YouTube channel at https://www.youtube.com/channel/UC4B9cOO6KxTDVnnbvRbDJGw
It happens when you create a newer world with the same name as an older world you deleted. When you delete a world, you aren't actually deleting the save data and it's not actually gone forever like it says on-screen. Every single bit of your world data is still there on your computer, there's just no convenient way to access it via the Single Player index of worlds to choose from.
That is not quite true; when the game deletes a save it is really deleted - the game means it when it says it is gone forever. However, because the client runs on a separate thread form the sever it is possible that the server is still running when you try to delete the world, which will fail because you can't delete a file that is in use; alternatively, the game deletes the region files and the server recreates them when it saves - note that the server thread says it is saving chunks just before the client tries to delete the world, which is still saving as seen by the lines about saving the Nether and End after the client's failed deletion attempt:
The fix for this is so obvious I have absolutely no idea why Mojang has not fixed it yet - make the client wait for the internal server to shut down before it can do anything else:
With this code (originally take from Forge) I have never been able to reproduce this, or any of the other world corruption issues that this causes (not only does this cause issues with deleting saves, it lets you quit the game while the server is still saving - resulting in world corruption, which, among other things, includes swapping chunks (a chunk is copied form one area and moved elsewhere). I actually think that the OP may have experienced the latter since there is a single chunk by itself, while the deletion bug usually has more chunks (in vanilla the code above simply sets the server object to null immediately after telling it to shut down, which is like pulling the plug on your computer while saving; if you've ever seen a stacktrace starting with "java.io.IOException: Stream Closed" and referring to files in the game output when quitting a world this is what happened).
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?
I did not delete any worlds before I saw this glitch.
Check out my YouTube channel at https://www.youtube.com/channel/UC4B9cOO6KxTDVnnbvRbDJGw