Seeing strange black holes, missing blocks, or does your server crash when loading a specific area? This can point to a corrupted chunk. In this article, we explain how to fix this.

How does a corrupted chunk happen?

Corrupted chunks usually occur due to:

• a hard server crash while the world is being saved,
• a power outage or hard shutdown of the server while writing to disk,
• a plugin or mod that modifies the world files in an incorrect way.

Step 1. Always make a backup first

Before changing anything in your world files: make a backup via Backups → Create Backup in the Game Panel. This way, you can always go back if the repair doesn't go well.

Step 2. Identify the corrupted chunk

Look in the startup or crash log for messages such as:

Exception ticking world
Corrupt NBT tag

This usually also shows the coordinates of the problem area.

Step 3. Use a chunk repair tool

Use a tool such as MCASelector to find and remove damaged chunks without losing the rest of your world.

1. Download your world folder via the File Manager or SFTP.
2. Open the folder in MCASelector.
3. Locate the problem area based on the coordinates from the crash log.
4. Remove only the specifically damaged chunk(s).
5. Upload the adjusted world folder back to the server.

Note: A removed chunk regenerates as soon as a player travels there again, but all builds in that specific chunk will be lost.

How do you prevent this in the future?

• Always shut down the server cleanly via the Game Panel, not by hard-killing the process or pulling the plug (on your own hardware).
• Make regular backups, so you can quickly go back to a working state in case of problems.
• Keep your server software (Paper/Spigot) up to date, newer versions often have more stable storage logic.

Still stuck, or would you like help repairing a corrupted chunk? Feel free to reach out via Discord or create a support ticket.