How does chunk loading work, and how do I avoid world corruption?
Chunks are the blocks of terrain your server loads around each player as they move. Understanding how that works — and shutting down cleanly — is the key to keeping your world healthy, because corruption almost always traces back to an unclean shutdown.
How chunk loading works
As players move through the world, the server loads the chunks around them and unloads ones no one is near. The more players spread out (and the higher your view and simulation distance), the more chunks are active at once. When the server stops, it writes all of those loaded chunks back to disk — and that final write is exactly where things can go wrong if the shutdown isn't clean.
How to avoid world corruption
- Keep view distance and simulation distance reasonable in
server.propertiesso the server isn't holding excessive chunks in memory. - Always stop the server cleanly — use the Stop button in the Console tab, never Kill — so loaded chunks finish writing to disk.
- Back up before big changes (download your world via Files or SFTP) so a corrupted world can be rolled back.
Warning: Forcing a Kill, or losing power mid-save, is the number-one cause of chunk and world corruption. A graceful Stop gives the world time to write safely — always prefer it.
Frequently asked questions
My chunks are already corrupted — now what? Restore an earlier copy of the world from before the corruption. If you have a download saved, re-upload it via Files or SFTP; if not, open a ticket and we'll see what's possible.
How do I reduce lag from chunk loading? Lower your view and simulation distance, and pre-generate the world so movement loads existing terrain rather than generating it on the fly.