How do I update my Minecraft server to 26.2 and the new yearly versions?

Minecraft no longer uses version numbers like 1.21.x. Since 2026, releases follow a year-based numbering scheme — 26.2 'Chaos Cubed' is the second drop of this year — and arrive as smaller game drops spread across the year. In this article you will learn how the new model works and how to update your server safely: back up first, then check Java 25, and finally change the server version. You use the same steps for 26.3 "Wilderness Bound", released on 15 September 2026.

From 1.21.x to yearly versions: how the drop model works

Mojang no longer releases Minecraft as one big yearly update followed by a long string of point releases. Instead, several smaller game drops arrive each year, and the version number tells you exactly where you are: the first number is the year, the second is the drop within that year. So 26.2 is the second drop of 2026, and 26.3, released on 15 September 2026, is the third drop. Small bugfix releases get a third number, such as 26.2.1.

For you as a server admin, this means updates arrive more often but are smaller each time. That makes the step-by-step plan below reusable for every future drop — only the version number changes.

Step 1: Make a backup first

Once a world has been opened in a new drop, you cannot downgrade it to an older version. A backup is your only way back.

1. Log in to panel.mc-node.net and open your Minecraft server.
2. Go to the Backups tab and click Create backup.
3. Wait until the backup has fully completed and check that the file size looks right (not 0 bytes).
4. Are all your backup slots in use? Download an old backup first or delete one.

You can find more details in how do I make a backup.

Step 2: Check Java and switch to Java 25

Along with the yearly versions, the minimum Java requirement has gone up: the 2026 drops run on Java 25. If you start 26.2 on an older Java version, the server will crash immediately on boot.

1. Open your server's Startup tab.
2. Check which Docker image (the Java version) is currently selected.
3. Still on Java 21 or older? Select the Java 25 image.
4. Restart your server via the Console tab to apply the change.

Recent 1.21.x versions also run on Java 25, so you can safely do this step before switching versions. For a full walkthrough, see how do I change the Java version.

Step 3: Change the server version to 26.2

1. Stop your server via the Console tab.
2. Go to the Startup tab and find the variable for the server version (for example Minecraft Version).
3. Replace the old value (such as 1.21.8) with 26.2. If it says latest, your server automatically picks the newest release; around a drop we recommend a fixed version number, so you choose the moment of the update yourself.
4. Start the server. On first boot the new server jar is downloaded and your world is converted; this can take several minutes. Do not interrupt this process.

The exact steps per server type are covered in how do I change my version.

Running Paper with plugins? Wait for support

If you run Vanilla, you can update almost immediately after a release. For Paper and other plugin servers it works differently: the Paper team first has to support each drop themselves, and your plugins have to follow after that. Update too early and your server will not start, or plugins will disable themselves. Here is how to check whether you are ready for the drop:

1. Check the PaperMC downloads page to see whether builds for 26.2 or 26.3 are available yet. Builds marked as experimental are not meant for production servers.
2. Go through your most important plugins on the page where you downloaded them (such as Hangar, SpigotMC or Modrinth) and check whether the new drop is listed among the supported versions.
3. Read the plugin author's changelog: sometimes the existing build already works, sometimes a separate update is required.
4. Not sure? Test the drop on a second (test) server first, or wait a few days after the release before moving your main server over.

Common problems

• UnsupportedClassVersionError or the server stops immediately — You are running the new drop on a Java version that is too old. Set Java 25 (step 2) and start again.
• Plugins throw errors or get disabled — One or more plugins do not support 26.2 yet. Open logs/latest.log via the Files tab to see which plugin causes the error, then update or remove that plugin.
• You want to go back to the previous version — A world that has been opened in 26.2 can no longer be loaded in 1.21.x or an earlier drop. Set your server version back and restore the backup from step 1 via the Backups tab.
• Players see 'Outdated server' or 'Outdated client' — The player's version and the server version differ. Have players select the same version as the server in their launcher.
• There is no Paper build for the new drop yet — This is normal in the first days after a release. Keep running your current version until a stable build is available; you do not need to do anything.

Ready for every future drop

With this plan — make a backup, check Java 25, change the version, and wait for support on plugin servers — you can update your server safely to 26.2 and just as easily to 26.3. Stuck anyway? Open a ticket via our support page and include your server name and the exact error message from the console.