-
Notifications
You must be signed in to change notification settings - Fork 101
Chunk and region problems
Here you will find a small explanation of all the problems region-fixer can detect
Chunk inside a region-file are stored compressed. A corrupted chunk is a chunk that can't be decompressed anymore (usually a CRC error).
Solution: Once a chunk is corrupted can't be decompressed and it's lost. When minecraft finds a chunk like this it will silently delete it a regenerate it. Region-fixer can also remove these chunks but it can also replace them using a backup of your world.
The region file has a header and in there is where it's written where the chunks are in the minecraft world. But inside the chunks there is also two coordinates with the same information. Sometimes these coordinates doesn't match, and when this happen, the server will complain about a wrong located stuff.
Solution: This chunks can be read. Region-Fixer can remove them or replace them using a backup, extacly the same way as is done with corrupted chunks. This chunks can be much better fixed but for the moment is not implemented.
This is not a problem by himself, is not like a corrupted chunk or a wrong located chunk. This problem happens when there is a lot of entities in the same chunk. Although it doesn't look like a problem, the server has to move all the entities in every in game tick. This can make the server lag or even make it non working (when the amount of entities is really big... thousands).
Solution: Region-Fixer can delete all the entities in that chunk. Please note that entities are things like items in the ground (no in chests or users), mobs, animals... etc. See http://www.minecraft...net/wiki/Entity to know all the things that entities are.
Sharing offset: Region files are like small file systems. A region file has a header (like the index in a book) where it stores where all the chunks are. Sometimes, in the region file herader there are two (or more) headers pointing to the same chunk (with the book, two chapters that are in the same pages) and this is not good.
Solution: One of the chunks, is not really there, it jus has a reference in the region header. The solution is to remove the false reference from the region header.
It's a region file that it's so small in size that it doesn't have space to store the header. Any region file smaller than 8KiB is considered 'too-small'.
Solution: Removing or replacing it with a backup are the only real solutions. The region file has almost no info in it, I would say it's not even ar egion file! [/spoiler]