A massive chunk regeneration wiped out a huge section of a very highly detailed structure I had built. This had happened before, but the usually the chunks just disappear, and back then I was able to get everything back because I backup constantly.
This time the problem is far worse. This time the chunk didn't just disappear, but the biome changed, and a jungle was swapped out for half of the structure. Worsening matters, I had been building a large new structure elsewhere in the map, so if I load a backup, I will lose all my NEW work.
FYI, I am still on 1.2.5 because of all the bug issues reported with 1.3, so I haven't updated. My machine is already running hot as it is. Not running any mods except OptiFine.
The chunk problem is absolutely unforgivable. To release a game that invites you to build for hours on end, but then never fix a known problem that wipes a player's work without any possibility of restoring it is just outrageous. Imagine if MS Word wiped out a huge set of documents, and left you no way to get them back; or if Firefox or Chrome erased all your contacts and bookmarks, and there was no possible way of getting them back. People would be outraged.
The fact that is is a PAID product makes it more frustrating.
The risk now is that I spend time rebuilding the old structure, only to go back and find some new set of chunks wiped out elsewhere in the map.
And there's not a DAMN thing you can do about it, except delete Minecraft.
This is the first time I've ever heard of this when there wasn't a mod involved. Your getting flipped bits, so that rules out simple corruption on save (which would render the maps unreadable). And the fact that your aware that your system runs hot doesn't really speak well for data integrity.
What settiings are you using in optifine? I know for a fact that it handles chunk loading. But for corruption to occur in single chunks like that, you'd have to very selectively damage the region file data, or change the world seed and then delete a very specific piece of the region data.
Frankly the damage is just way too precise, and practically unheard of in 1.2.5 to be a vanilla code problem. Otherwise this would had been a top issue for the past 4 or 5 months.
This is the first time I've ever heard of this when there wasn't a mod involved. Your getting flipped bits, so that rules out simple corruption on save (which would render the maps unreadable). And the fact that your aware that your system runs hot doesn't really speak well for data integrity.
What settiings are you using in optifine? I know for a fact that it handles chunk loading. But for corruption to occur in single chunks like that, you'd have to very selectively damage the region file data, or change the world seed and then delete a very specific piece of the region data.
Frankly the damage is just way too precise, and practically unheard of in 1.2.5 to be a vanilla code problem. Otherwise this would had been a top issue for the past 4 or 5 months.
The problem first occurred under a known condition which has been reported for some time now. Chunks start to get corrupted when you travel a distance across a map and encounter randomly-generated abandoned mineshafts or strongholds. This results in game crashes when going near the mineshaft, which results in chunk corruption elsewhere on the map.
But that usually resulted in a chunk DELETED -- everything was replaced by air.
This one is weird, in that a jungle suddenly "encroached" on my buildings, as if the chunk was rewritten.
(For what it's worth, I am teaching myself MCEdit, and may have figured a way to repair the damage using cut and paste from an older game save.)
My settings in OptiFine aren't anything aggressive, just dialing down some features to get the game to run without overheating or crashing. Not sure what settings you would need to know about to better inform you...there's like a million of them.
The problem first occurred under a known condition which has been reported for some time now. Chunks start to get corrupted when you travel a distance across a map and encounter randomly-generated abandoned mineshafts or strongholds. This results in game crashes when going near the mineshaft, which results in chunk corruption elsewhere on the map.
Never heard of that one.
This one is weird, in that a jungle suddenly "encroached" on my buildings, as if the chunk was rewritten.
If your world is old then the seed may generate a completely different world in the current version of minecraft.
Let me rephrase.
If your world is older than the version of minecraft you are currently running, then the seed may generate a completely different world in the version of minecraft you are currently running.
Anvil or not.
Anvil format persisted the biome into the saved chunk, which prevented random biome changes to an existing chunk.
Nevertheless, if you deleted the chunk file off disk, you would see the biome potentially change, along with the terrain, when the chunk was regenerated from scratch using only the seed and no persisted information
Let me rephrase.
If your world is older than the version of minecraft you are currently running, then the seed may generate a completely different world in the version of minecraft you are currently running.
Anvil or not.
Anvil format persisted the biome into the saved chunk, which prevented random biome changes to an existing chunk.
Nevertheless, if you deleted the chunk file off disk, you would see the biome potentially change, along with the terrain, when the chunk was regenerated from scratch using only the seed and no persisted information
Not sure I understand. If this were the case, then anyone who ever upgraded to Anvil would be having this problem: millions of users. My world is old, but upgraded to Anvil without problems, probably 80% of it was built post-Anvil, and has been running fine until recently. Anvil's been out for, what... 6 months now?
Having said that, your deleted chunk quote sounds like what is happening, except (of course) I am not intentionally deleting any chunks off disk. So something happened in this case to delete the chunk.
Chunk issues have existed since pre-beta, through version 1.1 and into Anvil, and seem only to be getting worse, reading the reports here. But Mojang doesn't address any of it. Really a shame the way they treat paying customers.
No, I"m saying that if a given chunk gets damaged / deleted in some unknown fashion, then what is happening is perfectly explainable from that point on.
I also have to say that I have never had any chunk problems of any kind whatsoever other than an occasional chunk not loading / rendering temporary thing in any of my worlds.
If you lose power, fail to exit the game cleanly, have a crash (see 'fail to exit cleanly'), then you can have all kinds of odd data corruption happen, and that's in any application including Windows itself (Blue Screen can lead to corrupted files on disk).
It's why backups are important. If your corrupt area and your 'new' construction not yet backed up are far apart, you could experiment with taking a copy of your backup and dropping individual mca anvil files into it. (Basically cutting and pasting one set of chunks from your corrupt world to your backup copy world.) An application like McEdit might let you be even more selective as to what you save from your corrupted world.
No, I"m saying that if a given chunk gets damaged / deleted in some unknown fashion, then what is happening is perfectly explainable from that point on.
I also have to say that I have never had any chunk problems of any kind whatsoever other than an occasional chunk not loading / rendering temporary thing in any of my worlds.
If you lose power, fail to exit the game cleanly, have a crash (see 'fail to exit cleanly'), then you can have all kinds of odd data corruption happen, and that's in any application including Windows itself (Blue Screen can lead to corrupted files on disk).
It's why backups are important. If your corrupt area and your 'new' construction not yet backed up are far apart, you could experiment with taking a copy of your backup and dropping individual mca anvil files into it. (Basically cutting and pasting one set of chunks from your corrupt world to your backup copy world.) An application like McEdit might let you be even more selective as to what you save from your corrupted world.
As I said above, I do backups, and have fixed the problem by using MCEdit and an old backup.
So to be clear, in order to use Minecraft, one has to (1) install an unapproved third party backup application (the in-app backup is useless), and (2) use another unapproved third party chunk editor to restore select areas when the program fouls up.
And, if there were any improper exits from the game, I can guarantee you it was due to a crash.
If everything has worked fine for you, that's awesome. I'm glad for you. But it also means you probably don't have a lot of advice for people who HAVE had problems, since you haven't cannot have worked out a solution for something you never encountered.
If I sound a little rankled, it is because it is absolutely exhausting to be confronted with the ages-old PEBKAC meme, which automatically blames the guy paying the check, and simultaneously disavows any responsibility on the part of the guy cashing the check. Everytime I see a Creeper plush toy or a MC t-shirt, I am reminded how far off the ball they have taken their focus. Imagine if when your car broke, the mechanic just blamed the driver and said, "Stuff has been breaking since they invented the wheel, so we're not responsible."
Little update: I repaired my structure as best I could with MCEdit, so at least that's taken care of.
I explored my world a bit further in another direction, building railways very far out so that I can travel back and forth quickly. Tonight I encountered a village in a completely unexplored area of the world, and the village had clearly had it's OWN "chunk apocalypse" -- the buildings on ocean-facing side of the village had been sliced open, and the ocean water had just "stopped" where the slice occurred -- floating in air, a typical sign of corrupt chunk.
I'll be searching for an updated chunk verification app, since that seems to be what I need next. So far the only ones I've seen have been dropped and are no longer supported.
I "feel" like the problem is exacerbated because I explore very vast distances of my world, and use these rail systems to travel across the distance faster. I have no data to support that, but maybe I'm making things worse by "using" so much of the world, rather than constraining my activities to a smaller area?
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
This time the problem is far worse. This time the chunk didn't just disappear, but the biome changed, and a jungle was swapped out for half of the structure. Worsening matters, I had been building a large new structure elsewhere in the map, so if I load a backup, I will lose all my NEW work.
FYI, I am still on 1.2.5 because of all the bug issues reported with 1.3, so I haven't updated. My machine is already running hot as it is. Not running any mods except OptiFine.
The chunk problem is absolutely unforgivable. To release a game that invites you to build for hours on end, but then never fix a known problem that wipes a player's work without any possibility of restoring it is just outrageous. Imagine if MS Word wiped out a huge set of documents, and left you no way to get them back; or if Firefox or Chrome erased all your contacts and bookmarks, and there was no possible way of getting them back. People would be outraged.
The fact that is is a PAID product makes it more frustrating.
The risk now is that I spend time rebuilding the old structure, only to go back and find some new set of chunks wiped out elsewhere in the map.
And there's not a DAMN thing you can do about it, except delete Minecraft.
Very, very frustrating.
What settiings are you using in optifine? I know for a fact that it handles chunk loading. But for corruption to occur in single chunks like that, you'd have to very selectively damage the region file data, or change the world seed and then delete a very specific piece of the region data.
Frankly the damage is just way too precise, and practically unheard of in 1.2.5 to be a vanilla code problem. Otherwise this would had been a top issue for the past 4 or 5 months.
The problem first occurred under a known condition which has been reported for some time now. Chunks start to get corrupted when you travel a distance across a map and encounter randomly-generated abandoned mineshafts or strongholds. This results in game crashes when going near the mineshaft, which results in chunk corruption elsewhere on the map.
But that usually resulted in a chunk DELETED -- everything was replaced by air.
This one is weird, in that a jungle suddenly "encroached" on my buildings, as if the chunk was rewritten.
(For what it's worth, I am teaching myself MCEdit, and may have figured a way to repair the damage using cut and paste from an older game save.)
My settings in OptiFine aren't anything aggressive, just dialing down some features to get the game to run without overheating or crashing. Not sure what settings you would need to know about to better inform you...there's like a million of them.
Never heard of that one.
If your world is old then the seed may generate a completely different world in the current version of minecraft.
I didn't upgrade to 1.3, so this is happening under Anvil.
If your world is older than the version of minecraft you are currently running, then the seed may generate a completely different world in the version of minecraft you are currently running.
Anvil or not.
Nevertheless, if you deleted the chunk file off disk, you would see the biome potentially change, along with the terrain, when the chunk was regenerated from scratch using only the seed and no persisted information
Not sure I understand. If this were the case, then anyone who ever upgraded to Anvil would be having this problem: millions of users. My world is old, but upgraded to Anvil without problems, probably 80% of it was built post-Anvil, and has been running fine until recently. Anvil's been out for, what... 6 months now?
Having said that, your deleted chunk quote sounds like what is happening, except (of course) I am not intentionally deleting any chunks off disk. So something happened in this case to delete the chunk.
Chunk issues have existed since pre-beta, through version 1.1 and into Anvil, and seem only to be getting worse, reading the reports here. But Mojang doesn't address any of it. Really a shame the way they treat paying customers.
I also have to say that I have never had any chunk problems of any kind whatsoever other than an occasional chunk not loading / rendering temporary thing in any of my worlds.
If you lose power, fail to exit the game cleanly, have a crash (see 'fail to exit cleanly'), then you can have all kinds of odd data corruption happen, and that's in any application including Windows itself (Blue Screen can lead to corrupted files on disk).
It's why backups are important. If your corrupt area and your 'new' construction not yet backed up are far apart, you could experiment with taking a copy of your backup and dropping individual mca anvil files into it. (Basically cutting and pasting one set of chunks from your corrupt world to your backup copy world.) An application like McEdit might let you be even more selective as to what you save from your corrupted world.
As I said above, I do backups, and have fixed the problem by using MCEdit and an old backup.
So to be clear, in order to use Minecraft, one has to (1) install an unapproved third party backup application (the in-app backup is useless), and (2) use another unapproved third party chunk editor to restore select areas when the program fouls up.
And, if there were any improper exits from the game, I can guarantee you it was due to a crash.
If everything has worked fine for you, that's awesome. I'm glad for you. But it also means you probably don't have a lot of advice for people who HAVE had problems, since you haven't cannot have worked out a solution for something you never encountered.
If I sound a little rankled, it is because it is absolutely exhausting to be confronted with the ages-old PEBKAC meme, which automatically blames the guy paying the check, and simultaneously disavows any responsibility on the part of the guy cashing the check. Everytime I see a Creeper plush toy or a MC t-shirt, I am reminded how far off the ball they have taken their focus. Imagine if when your car broke, the mechanic just blamed the driver and said, "Stuff has been breaking since they invented the wheel, so we're not responsible."
I explored my world a bit further in another direction, building railways very far out so that I can travel back and forth quickly. Tonight I encountered a village in a completely unexplored area of the world, and the village had clearly had it's OWN "chunk apocalypse" -- the buildings on ocean-facing side of the village had been sliced open, and the ocean water had just "stopped" where the slice occurred -- floating in air, a typical sign of corrupt chunk.
I'll be searching for an updated chunk verification app, since that seems to be what I need next. So far the only ones I've seen have been dropped and are no longer supported.
I "feel" like the problem is exacerbated because I explore very vast distances of my world, and use these rail systems to travel across the distance faster. I have no data to support that, but maybe I'm making things worse by "using" so much of the world, rather than constraining my activities to a smaller area?