CAFORADocs
Troubleshooting

World Corruption

Identify, fix, and prevent world corruption on your Cafora Minecraft server.

Illustrated procedure

Screenshots show the current application with demonstration data. Use your own service details; click an image to inspect it at full size.

Check the console

Open Essentials → Console. Check the current state, startup output and errors before making changes. Wait for Done or your software’s ready message before joining.

Check the console
Check the console2026-11-11 · Current application interface · demonstration data · Open full-size image

Locate the file log

Under Files, double-click logs and locate latest.log. Check modification times. Preserve the relevant file before a restart replaces or rotates it.

Locate the file log
Locate the file log2026-11-11 · Current application interface · demonstration data · Open full-size image

Read the complete error context

Open the log in the editor and inspect the earliest relevant error and surrounding lines. Remove tokens, passwords and private player details before sharing. Do not diagnose from the last line alone.

Read the complete error context
Read the complete error context2026-11-11 · Current application interface · demonstration data · Open full-size image

Describe the request to support

Open a support ticket with the service or invoice ID and the requested action. For connection issues include time, error and MTR evidence. Never include passwords, tokens or card details.

Describe the request to support
Describe the request to support2026-11-11 · Public page · no private account data · Open full-size image

Signs of Corruption

  • Server crashes when loading specific chunks
  • Missing or swapped chunks (ocean where land should be)
  • Entities behaving erratically in certain areas
  • Error messages about chunk loading in the console
  • Server fails to start with world-related errors

Common Causes

  • Improper server shutdown (kill command, power loss)
  • Running out of disk space during a save
  • Mod or plugin that corrupts chunk data
  • Transferring world files incorrectly
  • Hardware issues on the host

Fixing Minor Corruption

Stop the server immediately.

Create a backup of the current state.

Try restarting the server — sometimes Paper/Purpur can auto-repair minor issues.

If the crash persists, identify which region file is corrupt from the error log.

Delete the corrupt region file — the affected area will regenerate as new terrain.

Alternatively, restore that region from a known-good backup.

Deleting a region file permanently removes all builds and changes in that area. Only do this if you have a backup or are willing to lose that region.

Full Recovery

For severe corruption, restore your entire world from a recent backup:

  • See Restoring Backups for step-by-step instructions
  • Always keep multiple backup snapshots in case one is also corrupt

Prevention

  • Always stop the server gracefully with /stop
  • Enable automatic backups
  • Maintain enough free disk space
  • Update server software regularly

Service information · Backups · Support

On this page