Direct answer

Back up the world before deleting or regenerating anything.

What it means

World-load crashes can come from damaged region/entity/POI data, incompatible datapacks/mods, or version downgrades.

If you are a player

  • Preserve the original world directory and error logs; do not ask an affected player to delete their client saves.
  • Record whether the crash occurs immediately on world load, during spawn loading, or only on entering one dimension.
  • If this is a modded server, note whether the world and modpack versions recently changed.

If you run the server

  1. Make a full offline backup of every dimension and player-data directory before isolating a failure.
  2. Find the first actionable exception in logs/latest.log or crash-reports/; note the dimension, chunk coordinates, missing registry ID or mod class involved.
  3. Test with a copy of the world and matching server/loader/mod versions; do not downgrade an upgraded world or delete region files to “repair” it.
  4. When a corrupt chunk or bad block entity is specifically identified, use a supported backup restore or targeted repair tool on a copy, then verify surrounding structures.

Verify the result: The copied world must load, allow travel through the affected area and save/restart cleanly before replacing a production world.

References

Use the documentation for the exact software and release you run. These sources support the settings or diagnostic behavior used in this fix.

Was this article helpful?
Help us improve this article

Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.

What could we improve?
Do not include passwords, server IPs, or other private information.0 / 1000