How to update your Minecraft server without breaking your world

The part you can’t undo

Worlds only go forward. Once a newer version opens one, it quietly converts pieces of it to the newer format, and an older version can’t read what comes out. Try to go back and you can end up with chewed-up chunks.

So the backup comes first, every time, and it comes before anything else on this page. Copy the whole server folder, the way we describe in the backups post, and hang on to it until you’ve played on the new version for a few days.

Plugins and mods set the schedule

Here’s the thing nobody mentions in the announcement: your add-ons decide when you can update, not Mojang. Authors need time to rebuild for a new release. Sometimes that’s a weekend. Sometimes it’s a month, and a few projects never come back.

Open the download page of every plugin or mod you actually depend on. Does it list the new version? If your permissions plugin doesn’t, you wait, and that’s that. Updating anyway tends to end with a server that refuses to start, or worse, one that starts and silently drops a feature.

The server software has the same lag. Paper needs a build made for that exact Minecraft version, and it can show up a little after the game does.

What the update looks like in practice

Warn people first. A line in your Discord is enough. Then stop the server and make that backup.

Swap in the new server file and keep the old one in a folder somewhere, in case you need it. Then check Java. Newer Minecraft releases occasionally need a newer Java, and the server won’t even try to start on the old one. Version 1.20.5 was the one that moved to Java 21, for instance.

Start it and watch the console as it loads, because the first error is almost always the useful one. It usually names the plugin or mod that has a problem. Once it says it’s done, join it yourself and walk around. Open a chest, break a block, run a command from a plugin. Only after that do you tell everyone it’s back.

Snapshots and other test builds

Mojang puts out test versions ahead of each big release. They’re fun. They’re also a one-way door for your world. If you want to poke at one, do it on a copy on a different server and leave the real world alone.

Your players need to match

Clients and servers have to agree on the version, more or less. When they don’t, a player sees “Outdated client” or “Outdated server” and gets nowhere. Plugin servers can sometimes let a range of versions in with a helper plugin, but that’s a patch, not a plan.

Mineshire does the careful part for you. Choose a new version for the server and it checks your plugins and mods before changing anything, and it can take a backup first. You should still join afterwards and look around, since no checker replaces actually standing in your world.

Quick answers

Is replacing the server file all it takes? For the software itself, mostly. You also have to check plugins and mods, Java, and your backup, as above.

Can I go back if the update goes wrong? Only if you made a backup first. Worlds that a newer version has opened can’t safely be loaded by an older one.