My world reset, used the same seed, or cleared builds after an update — why?

Seeing your world "reset" after an update is alarming, but it usually doesn't mean the world is gone — more often the server generated a new world folder because it couldn't find the old one. Here's why it happens and how to get your real world back.

Why it looks like a reset

There are three common causes:

1. A version or software install replaced files — the Software page moves anything it replaces into a _previous folder (there's no "Wipe Data" box any more).
2. The server generated a new world folder because the old one was renamed, missing, or level-name changed.
3. You uploaded a world but level.dat wasn't directly inside the world folder, so the server made a fresh one instead.

In each case, your original world may still be on disk — in _previous or under a different name — nothing was actually deleted.

How to fix it

1. Stop the server.
2. Restore a backup from the Backups page, or re-upload the correct world folder — with level.dat at its root — from a copy you saved, via Files or SFTP.
3. Confirm level-name=world in server.properties.
4. Start and check the Console.

Tip: If you have no copy of the world, open your server → Backups — every server is backed up automatically twice a day, so you can restore one from before the update.

Frequently asked questions

Is my old world really gone? Not necessarily. If it was renamed, moved to _previous, or the server just made a new folder, your original may still be on disk. Check your files before assuming the worst.

How do I avoid this next time? Keep level-name consistent, and make a backup (Back up now on the Backups page) before an update.

I can't find any copy — what now? Check the Backups page for an automatic backup from before the update. If none helps, open a support ticket and staff will look at what can be recovered.