If you have a corrupt world from using the new 12w21a - 12w21b test updates, this page is for you!
I had my world corrupt and i had spent ages on it, like 14 weeks. I ended up deleting it and having a ***** about it. But today i started another project (no back-up, just like the other one), and it went corrupt. I was getting worried, i decided to check the save folder to find what was wrong. I checked the save that had just went corrupt and found there was a file that wasn't there before. I went and deleted it and booted up Minecraft again, and it worked.
So if you are using the new pre-update and your world gets corrupt, this is what you have to do:
1; go to the Minecraft system file (.minecraft) located in %appdata% file (%appdata% is for Windows XP)
1a; if you can't find the file, go to your Minecraft launcher and click options, then the link below the force update button.
2; go to the saves folder, and then the file with the same name as the world that got corrupted.
3; delete the file call "level.dat_mcr"
4; done.
Please comment and tell me if this worked for you, and if it doesn't work then don't you dare call names or hate on me. I am only trying to help.
EDIT: This only works if you load your world and your person falls continually into the void and commands won't work.
I tried this and it works getting me into the map but my player keeps falling in black nothingness. Its weird. I had a lot of diamonds . But tanx anyway.
It was supposed to stop THAT from happening, that's really weird.
It's a shame boats will no longer work correctly from now on. (Among other things)
Yes yes, I understand it's a SNAPSHOT, I get it. But the simple matter is, client to server lag can never be fixed, only optimized.
The boat is just one example, and the most easy to observe.
As long as this type of personal server-to-client architecture problems like this will always exist. Minecraft will never run as smooth as it once did, because now every action has to be synced with the server.
I won't complain until the actual update is out, but I guarantee a lot of these bugs we see will still persist, as there is no real way to circumvent them.
I had my world corrupt and i had spent ages on it, like 14 weeks. I ended up deleting it and having a ***** about it. But today i started another project (no back-up, just like the other one), and it went corrupt. I was getting worried, i decided to check the save folder to find what was wrong. I checked the save that had just went corrupt and found there was a file that wasn't there before. I went and deleted it and booted up Minecraft again, and it worked.
So if you are using the new pre-update and your world gets corrupt, this is what you have to do:
1; go to the Minecraft system file (.minecraft) located in %appdata% file (%appdata% is for Windows XP)
1a; if you can't find the file, go to your Minecraft launcher and click options, then the link below the force update button.
2; go to the saves folder, and then the file with the same name as the world that got corrupted.
3; delete the file call "level.dat_mcr"
4; done.
Please comment and tell me if this worked for you, and if it doesn't work then don't you dare call names or hate on me. I am only trying to help.
EDIT: This only works if you load your world and your person falls continually into the void and commands won't work.
P.S. The new snapshots are 12w21a and 12w21b, not 12w12a and 12w12b
It was supposed to stop THAT from happening, that's really weird.
I will fix that, thank you.
Yes yes, I understand it's a SNAPSHOT, I get it. But the simple matter is, client to server lag can never be fixed, only optimized.
The boat is just one example, and the most easy to observe.
As long as this type of personal server-to-client architecture problems like this will always exist. Minecraft will never run as smooth as it once did, because now every action has to be synced with the server.
I won't complain until the actual update is out, but I guarantee a lot of these bugs we see will still persist, as there is no real way to circumvent them.