Minecraft Update Day Checklist: What to Do When a New Version Drops

A drop lands, your Discord fills up with people asking when the server updates, and you have to decide what to do today. This is the checklist — short, reusable, and written to be worked through in order on every release rather than read once. It does not replace Updating Your Minecraft Server, which is the detailed guide to what each step actually involves; it is the thing you open on the day.

Three to four drops land each year on a roughly quarterly cadence, so you will use this a few times a year for as long as you run a server.

0. Do Not Update on Day One

Nothing on this list is urgent. A server on the previous version keeps working, and the only thing that forces your hand is players on the new client being unable to connect — Java Edition has no cross-version compatibility, so a client can only join a server on its own protocol version.

What you gain by waiting a few days: your plugins and mods get builds for the new version, other people find the crashes first, and the first hotfix usually lands. What you lose: a few days of being current.

Announce a date rather than updating quietly. "We update on Saturday" prevents a week of questions.

1. Confirm What the Current Release Actually Is

Do not take a video's word for it. Two endpoints answer this definitively, and both are public.

Mojang's version manifest names the current release and the current snapshot:

curl -s https://launchermeta.mojang.com/mc/game/version_manifest_v2.json | jq '.latest'

Each entry in that manifest links to a per-version metadata file containing a javaVersion.majorVersion field and a direct server.jar URL — so the Java requirement is published data, not folklore.

PaperMC's Fill API answers whether a version is still supported, and what Java it needs:

curl -s https://fill.papermc.io/v3/projects/paper/versions/26.2 | jq '.version'

Checked on 19 August 2026, those two sources give:

Re-run the two commands rather than trusting that table; it is a snapshot of a moving target.

The Java version is the step people skip

Minecraft raises its minimum Java version periodically and 2026 was one of those times. A 26.x jar on Java 21 does not warn you — it fails immediately with an unsupported class file version. Class file version 69 means the jar wants Java 25; 65 means Java 21. On our servers the runtime is the Docker Image selector on the Startup tab, and it needs changing in the same maintenance window as the version.

2. Back Up. Every Time.

PaperMC calls this "the most important step, and yet the most frequently skipped", and support tickets agree.

• Snapshot from the Backups tab — this captures the whole server volume, not just the world. See How to Create a Backup.
• For a version jump rather than a build update, download the backup off-platform as well.
• Write down what you are currently on: framework, Minecraft version, Java version, build number. That is what "put it back" means.

Updating the server software rarely destroys anything by itself. A plugin misbehaving on the new version absolutely can, and by the time you notice, the world has already been upgraded.

3. Check Your Add-ons Before You Touch the Version

This is the step that decides whether the update takes twenty minutes or a weekend.

Plugins. Open each one's download page and check for a build supporting the new version. Plugins that use only the Bukkit API often survive several Minecraft versions untouched; plugins that reach into Minecraft's internals break on every one. On Paper you can stage new jars: create a folder called update inside plugins/, put the new jars in it, and Paper swaps them in on the next start.

Mods and modpacks. The order reverses — the pack leads, not the Minecraft version. If your pack has no release for the new version, you are done for today; wait. Never update Minecraft underneath a pack. Loose mod lists have to be updated mod by mod, and one mod without a build blocks the whole thing.

Your proxy, separately. A Velocity proxy has its own version and its own Java requirement — 4.0.0 needs Java 25, 3.5.1 still runs on Java 21 — and its plugins are a different ecosystem. Check it as its own item. See Minecraft Server Networks.

A plugin built for the new version usually still loads on the old one

The reverse usually does not. That asymmetry is why you update add-ons first and the server version second, rather than the other way round.

4. Know That the World Upgrade Is One-Way

Every world save records a data version — an ever-increasing integer, stored in level.dat and in every chunk, identifying the version that last wrote it. When a newer server loads an older world it upgrades the data it touches, chunk by chunk as they load.

Two consequences that matter on update day:

• The server does not ask. The client warns you before opening an out-of-date world; a server just loads it, upgrades it and carries on.
• There is no downgrade. Setting the version number back in the Startup tab leaves you with an upgraded world and an old server. Restoring the backup from step 2 is the only real undo.

If you want to know what a world is on before you start, /version prints the data version directly, and /data get entity @s DataVersion works too.

5. Watch for Settings That Moved

Recent releases have relocated a lot of configuration, and every relocation produces "I set it and nothing happened" tickets.

• Four server.properties keys became game rules in 1.21.9. pvp, enable-command-block, allow-nether and spawn-monsters were all removed and replaced by game rules. Setting them in the file now does nothing at all. Note that the replacement rules were then renamed again in 1.21.11 (see the next point), so on a 26.x server they are pvp, command_blocks_work, allow_entering_nether_using_portals and spawn_monsters — always take the name from your own server's tab completion rather than from a guide. spawn-animals and spawn-npcs were removed outright back in 1.21.2.
• Every game rule was renamed in 1.21.11. They moved into a registry and went from camelCase to snake_case — doDaylightCycle became advance_time, doMobSpawning became spawn_mobs, announceAdvancements became show_advancement_messages, and so on. Several also had their sense inverted: disableRaids became raids. Any script full of /gamerule calls needs rewriting once across that boundary.
• white-list defaults to true from 26.3. It is false today and the change is already in the 26.3 snapshots. When 26.3 lands, a freshly generated server.properties has the whitelist on, and a brand-new server rejects everyone including you until you add yourself.
• New keys appear. 1.21.9 added the management-server-* family and status-heartbeat-interval; 26.2 added chat-spam-threshold-seconds and command-spam-threshold-seconds. None of these breaks an upgrade, but they will show up in your file and are worth reading rather than deleting.

Every key and its replacement is in Minecraft server.properties: The Complete Reference.

6. The Update Itself

In this order, with nothing skipped:

1. Announce the maintenance window.
2. Update plugins or the modpack first (step 3).
3. Stop the server and wait for the process to exit. Never swap a jar under a running server.
4. Set the new Minecraft Version on the Startup tab, and the Docker Image if you are crossing a Java boundary.
5. Start, and read the console from the top. Plugin failures, missing dependencies and world upgrade progress all appear early.
6. Join and check the things that actually matter to you — claims, ranks, shops, warps, permissions — before you announce it is done.

7. Afterwards

• Watch the console for the first hour, not the first minute. Some failures only surface when a player triggers them.
• Check TPS once people are on. A new version changes performance characteristics; Diagnosing Minecraft Server Lag is how to tell a real regression from a busy first evening.
• Take a fresh backup once you are happy, so your next restore point is post-update.
• Keep the pre-update backup for a week. That is roughly how long it takes for someone to notice a plugin quietly not working.

Do not point a snapshot at your live world

Testing the next drop is a good idea; doing it on the real world is not. A snapshot upgrades the world to its own data version and there is no way back to the release. Use a copy, on a second server, with a copy of your config.

What to Read Next

• Updating Your Minecraft Server — the full guide behind every step here, including snapshots and downgrading
• Minecraft server.properties: The Complete Reference — every key, including the ones recent versions moved
• Minecraft Server Software Compared — which framework tracks which versions, and Paper's support status
• How to Create a Backup — step 2, in detail
• How to install plugins for Minecraft Java Edition — the plugins/update folder and dependency troubleshooting
• How to Install a Minecraft Modpack Server — updating a pack rather than a version
• Diagnosing Minecraft Server Lag — for the evening after
• Minecraft Server Networks: Setting Up a Velocity Proxy — updating the proxy as its own item

Primary sources used for this guide (all checked 19 August 2026): Mojang's version manifest and the per-version metadata it links to; PaperMC's Fill API; PaperMC's update guide; and the Minecraft Wiki on server.properties, game rules and data versions.

Made with 💜 by GameServerKings