So I just spent a few hours today (the 26th) playing Minecraft on my current Survival world. It had been a classic project to make it to the End completely Vanilla, without using mods or even console commands. This world's a Large Biomes world, and has been around since 1.3.2, and has had no problem updating since then.
Then I get my third music disk by letting a skeleton kill a creeper, put ward, the recently achieved disk, into my jukebox, and it plays like it's expected to. Then it starts raining, so I take the disk out mid song and it vanishes. Not in my inventory, not on the floor or stuck inside the wall (I broke the surrounding blocks to check, including the Jukebox itself), just gone. Then I go to one of my chests, which have the Christmas skin that came with 1.4.6 (they've opened fine both with and without the skin before) and Minecraft crashes.
I log back in and I see the image below.
Half my house, most of my carrot farm, all the pathways and stuff around it, even the trees I planted there, have reverted back to their original state. In a blink of an eye, months of work have been undone. One chunk reverted, no other chunks in the world have been affected by the crash, and I have to wonder if the new chests are to blame.
What actually happened here, is it fixable, and what's to blame?
I'm afraid no crash report is availible at the moment.
Edit: I also understand, based on the picture, how easy it looks like it could have been to fake such an incident Honestly, the chunk reverted back to the state the game told it to by the seed, and I honestly have no idea why.
First thing I want to tell you: please put things like that in a spoiler tag.
Back on topic: I've seen a lot of people having this problem. I honestly don't know what to do. Do you have a backup save?
I don't think it was the christmas chests for this sole reason. Five of us (my friends and I) have been playing a vanilla world for the last 3 months at least and everything has been pretty much peachy. We have had blank chunks, but this has simply been a client side error where it would not load a chunk that was really there. __However__, we logged in today and found that ONE single chunk had reverted to its original state. My friend is now missing part of his house, from top to bottom, the chunk reverted to its original spawn state. He is not happy, since he put alot of work into his house. It is really wierd because this is only one chunk, and is the only chunk this seems to have happened to. My other friend and I have been in tech (servers, workstations, networks, and programming) for more than 10 years, so like good nerds we looked for errors in the log and did alot of digging for information to see what was up. We found nothing in the logs except the occasional "server can't keep up, has time changed or is server overload" ... though we get that very rarely.. any ideas ?
Then I get my third music disk by letting a skeleton kill a creeper, put ward, the recently achieved disk, into my jukebox, and it plays like it's expected to. Then it starts raining, so I take the disk out mid song and it vanishes. Not in my inventory, not on the floor or stuck inside the wall (I broke the surrounding blocks to check, including the Jukebox itself), just gone. Then I go to one of my chests, which have the Christmas skin that came with 1.4.6 (they've opened fine both with and without the skin before) and Minecraft crashes.
I log back in and I see the image below.
Half my house, most of my carrot farm, all the pathways and stuff around it, even the trees I planted there, have reverted back to their original state. In a blink of an eye, months of work have been undone. One chunk reverted, no other chunks in the world have been affected by the crash, and I have to wonder if the new chests are to blame.
What actually happened here, is it fixable, and what's to blame?
I'm afraid no crash report is availible at the moment.
Edit: I also understand, based on the picture, how easy it looks like it could have been to fake such an incident Honestly, the chunk reverted back to the state the game told it to by the seed, and I honestly have no idea why.
---- Minecraft Crash Report ----
First thing I want to tell you: please put things like that in a spoiler tag.
Back on topic: I've seen a lot of people having this problem. I honestly don't know what to do. Do you have a backup save?