Typical symptoms and possible solutions - Fenixin/Minecraft-Region-Fixer GitHub Wiki

NOTE: this page might be outdated

The world loads in the server but after that nothing happens and the cpu usage is 100%.

This is probably a too much entities problem. These problem have two forms:

1. A lot of entities (thousands) are stored in a very small amount of chunks (maybe 10 or 20 chunks). This can happens if you ignite a few thousands of TNT. Once ignited they are entities, and the server hangs trying to move all of them. The best solution is to use "--entity-limit' with a representative number (like 100 or so) and "--delete-entities".

2. A lot of entities are stored in one region file, but taking like a lot of chunks (maybe 300 chunks). This is much harder to detect, because the entity density is much lower. I don't know how this problem happens, but the server still have to move all the entities when those chunk are loaded in memory, and hangs trying to do so. A good way to solve this is to try with different --entity-limit (lowering the number) options until you get the desired effect, maybe you end up deleting all the entities (--entity-limit=1). Yeah, an option to only run region-fixer in a single region file would be helpful...

Please, make sure you know what these options do before running region fixer with them. Think that you are going to delete all the entities in those chunks that exceed the limit of entities.

The world has a too high cpu usage even when idling but the server works properly.

Look for redstone machines in the chunks loaded with the spawn... some of them make the server really CPU hungry when idling.

When the world loads the server spam a lot of text about wrong located stuff.

You probably have some wrong located chunks with their respective wrong located entities. Region-fixer should report them with the default scan and you can delete them using '--delete-wronglocated', or by providing a backup world directory with '--backups'.