Excellent thread! Any tips for locating specific chunks in the world that are referenced within error messages generated in the MCEdit java console due to corrupt chunks?
Example:
ERROR:Error reading compressed data, assuming uncompressed: Not a gzipped file
ERROR:Malformed NBT data in file: C:\Users\manux\AppData\Roaming\.minecraft\save
s\World5\b\1n\c.b.-5.dat (Not an NBT file with a root TAG_Compound (found 31))
Malformed or deleted chunk: (11, -5) , C:\Users\manux\AppData\Roaming\.minecra
ft\saves\World5\b\1n\c.b.-5.dat
ERROR:Error reading compressed data, assuming uncompressed: Not a gzipped file
ERROR:Malformed NBT data in file: C:\Users\manux\AppData\Roaming\.minecraft\save
s\World5\b\8\c.b.8.dat (Not an NBT file with a root TAG_Compound (found 31))
Malformed or deleted chunk: (11, 8) , C:\Users\manux\AppData\Roaming\.minecraf
t\saves\World5\b\8\c.b.8.dat
Thanks in advance for any assistance rendered.
EDIT: Further research appears to have helped on this matter. I'm sure this isn't revolutionary info (especially to OP!), but I hate searching for answers to a problem that I've run into, and then seeing threads where folks post the exact problem I have, then update their post saying, "I fixed it!" without explanation, so here goes.
I got my current location within MCEdit by holding the Alt key and the right mouse button. With that info, I took the chunk coordinates that were referenced in the error message, and multiplied them by 16 to get the coordinates of a block that was part of the chunk in question. With the block coordinates in hand, it was easy to navigate to the problem area to remove the error producing chunk. I hope this helps anybody else out there, I'm recovering from map corruption due to an unexpected outage at my hosting provider.
0
Example:
Thanks in advance for any assistance rendered.
EDIT: Further research appears to have helped on this matter. I'm sure this isn't revolutionary info (especially to OP!), but I hate searching for answers to a problem that I've run into, and then seeing threads where folks post the exact problem I have, then update their post saying, "I fixed it!" without explanation, so here goes.
I got my current location within MCEdit by holding the Alt key and the right mouse button. With that info, I took the chunk coordinates that were referenced in the error message, and multiplied them by 16 to get the coordinates of a block that was part of the chunk in question. With the block coordinates in hand, it was easy to navigate to the problem area to remove the error producing chunk. I hope this helps anybody else out there, I'm recovering from map corruption due to an unexpected outage at my hosting provider.