Introduction
Minecraft 26.3 "Wilderness Bound" was released on 15 September 2026 on Java, alongside 26.50 on Bedrock. Three days later, the same question is being asked on every server: do we move the world to 26.3 now, and what is going to break?
Here is what the update actually contains, then how to move a server to 26.3, from the backup to rolling back if the first start goes wrong.
One thing before anything else: opening a world in 26.3 converts it to the new data format (data version 5023), and a converted world will not reopen in an earlier version. The whole procedure below is built around that.
What 26.3 really changes
A new biome and a new structure
The dappled forest is the visible headline: an autumn forest that generates next to cold biomes, with poplars in red, orange and yellow foliage, a carpet of fallen leaves on the ground and shelf mushrooms you can bounce on.
The abandoned camps arrive with it: small campsite structures that generate across sixteen different biomes, with visible chests and hidden chests, each with its own loot table. They are designed to be found early in a playthrough.
Both of them only generate in new chunks: on an existing world, your players will have to travel beyond the already explored area to see them. That is the first thing to announce on your Discord.
Blocks, furniture and decoration
Poplar wood arrives as a complete set: logs, planks, stairs, slabs, doors, fences, signs, buttons, pressure plates, trapdoors and boats, including the chest variant. More significant for creative servers: wool and concrete stairs and slabs, in all sixteen colours.
Two pieces of furniture round out the list. Cushions, in sixteen colours, let players sit down without a minecart or a mod. Straw beds stack to sixteen, are consumed on use and do not change the respawn point: a disposable bed for expeditions.
Finally, cartographers now sell new explorer maps: abandoned camps, ancient cities, mineshafts, desert pyramids and warm ocean ruins. Enough to give players who have seen everything a reason to travel again.
The technical side that concerns administrators
Two new commands arrive. /compute evaluates number providers in integer or float mode, with a scale factor, which replaces calculations previously hacked together with scoreboards. /posteffect controls client-side post-processing shaders (add, remove, list, clear).
The data component list grows noticeably, with attack_animation, block_transformer, cooking_fuel, compostable, mob_visibility, villager_food, waxed and sign_text_front among others. Add to that the minecraft:height_range block predicate, the invulnerable_time entity tag and two environment attributes, minecraft:gameplay/natural_mob_spawns and minecraft:gameplay/straw_bed_rule.
On the client side only, Mojang replaced GLFW with SDL3 for windowing, input and system integration. It does not affect the server, but it explains why some of your players see different controller or multi-monitor behaviour.
The four numbers to check before updating
These are what decide whether your update goes smoothly. None of them is cosmetic.
| Value | 26.3 | What it means |
|---|---|---|
| Minimum Java | Java SE 25 | A server still running Java 21 will not start |
| Network protocol | 777 | Proxies (Velocity, BungeeCord) and ViaVersion need updating |
| Data version | 5023 | The world is converted irreversibly on first launch |
| Data pack format | 121.0 | Existing data packs are rejected until they declare this format |
The resource pack format moves to 97.1: if you push a resource pack through server.properties, it has to be republished with the right pack_format, otherwise your players get a warning when they connect.
Step 1: the backup, before anything else
This is the one step that is not optional: a world opened once in 26.3 will not reopen in 26.2, and nothing undoes that after the fact.
In the panel, open the console and type save-all to force chunks to disk, then stop for a clean shutdown. Wait until the server is fully off: cutting a server mid-write corrupts regions.
Then go to the Backups tab and click Create a backup. Give it an explicit name, for instance before-26-3.
If your world genuinely matters, keep a second copy off the server: from the Files tab, download the world folders (world, world_nether, world_the_end), plugins or mods, server.properties and your permissions.
Step 2: take stock of what will not follow
This is the step everyone skips, and the one that costs an evening. List what runs on your server and check, one by one, that a 26.3 version exists.
Plugin servers
Paper publishes 26.3 builds on papermc.io: the server is not the problem, your plugins are. A plugin compiled for 26.2 may run on 26.3 if it stays away from low-level code, but anything that touches NMS, packets or recipes will break. The usual suspects: anti-cheat, land protection, menus, ProtocolLib and everything depending on it.
The method: open each plugin page, look at the date of the latest release and the supported versions. Anything untouched since 15 September is untested, and if a critical plugin has no 26.3 build, wait.
Modded servers
On the Fabric side, the ecosystem moved fast: Cloth Config API shipped for 26.3 on release day (build 26.3.158), and the optimisation modpacks followed within 48 hours. Fabulously Optimized, OptiFine for Fabric, Optimization, Thunder and FPSBOOST were all available on 26.3 on 17 and 18 September.
On the Forge side, the official branch is still stuck on 1.20.1 and NeoForge is the one tracking recent versions. A Forge server with a hundred mods does not move to 26.3 in an evening, often not within the month: a stable modded server beats a 26.3 one missing half its mods.
If you are unsure which loader to pick, our guide on installing Forge or Fabric on a Minecraft server covers the practical differences.
Proxies and multi-version setups
If you run behind Velocity or BungeeCord, the proxy has to know protocol 777, otherwise your players are rejected for an incompatible version while the backend is perfectly fine. Same for ViaVersion: without an update, 26.3 clients do not get through.
Data packs and resource packs
The data pack format moves to 121.0: your custom data packs are ignored at load time as long as their pack.mcmeta declares an older format. Fixing the value is usually enough; if they use recipes, loot tables or predicates, check the result in game before reopening.
Step 3: move the server to 26.3
Once the backup is done and the inventory is finished, the version change itself takes two minutes.
Stop the server from the console (save-all then stop), then open the Version tab. Pick your Edition (Vanilla, Paper, Spigot or Fabric depending on your setup), then version 26.3 from the list, and start the installation.
Critical point: do not tick the "Format the server" box. It deletes every existing file, your world included. It is only for deliberately starting over on a fresh world to enjoy 26.3 generation.
If you install the server manually from a .jar, use the Files tab and the Upload button, then check in the Settings tab that the startup command points at the right jar name: an update that "does not happen" usually comes from there.
Use the downtime to swap your plugins or mods for their 26.3 versions, rather than chaining two separate restarts.
Step 4: the first start, and what to watch
Start the server and keep the console in front of you. The first launch takes longer than usual: the server converts world regions to data version 5023. On a large world, expect several minutes during which nothing seems to happen. Do not interrupt it, an interrupted conversion damages the regions involved.
After that, three checks are enough to know whether the update is clean:
- Load-time errors: an incompatible plugin announces itself with an immediate stack trace, usually a
NoClassDefFoundErroror anUnsupportedClassVersionError. The latter means the server is not running on the right Java version. - A test connection: log in before announcing the reopening, check that your permissions respond, that land protection still blocks, and that your main plugin's commands work.
- TPS after ten minutes: a server that just converted its world is not representative straight away, look at how it behaves once a few players are connected. If it lags, our 15 tips to optimise a Minecraft server apply as-is on 26.3.
Step 5: rolling back if it goes wrong
Rolling back is possible, but there is one strict rule: it means restoring the backup taken before the conversion, not reinstalling the old version on top of the current world. A world at data version 5023 reopened on a 26.2 server is refused, or worse, loaded partially.
The procedure: stop the server, go back to the Version tab to reinstall the previous version, restore the before-26-3 backup from the Backups tab, put the old jars back, then restart. You lose whatever was built since the backup, which is why the update is best tested at a quiet hour rather than on a Saturday night.
The comfortable variant: spin up a second server on 26.3, restore a copy of the world onto it and test there while the main one stays online, then switch over once everything checks out. Our plans start at 4.99 EUR incl. VAT per month for 8 GB of RAM.
Update now, or wait?
- Vanilla or light survival server: go now, the risk is low and the conversion handles itself.
- Plugin server: go once your critical plugins have a 26.3 build. An anti-cheat or a protection system out of action weighs more than one extra biome.
- Heavy modded server: on a Forge pack, the question often does not arise for several months; on a Fabric optimisation pack, the ecosystem has already followed and the move is realistic today.
One rule in every case: never update on release day on a server with active players. The first few days are what plugin and mod developers use to ship fixes.
Frequently asked questions
Do I need to regenerate my world for 26.3?
No. Your existing world is converted automatically and stays playable. The dappled forest and abandoned camps, however, only generate in unexplored chunks: your players will have to travel to find them.
Which Java version does a 26.3 server need?
Java SE 25 at minimum. A server still configured for Java 21 will refuse to start, with an UnsupportedClassVersionError in the console. On our servers, the Java version is selected automatically based on the installed Minecraft version.
Do my 26.2 plugins work on 26.3?
Some do, some do not: the only way to know is to check each plugin's page. Anything touching packets, NMS or recipes needs updating, ProtocolLib and its dependants first.
Can I go back to 26.2 after starting the server on 26.3?
Not with the converted world: the move to data version 5023 is one-way. Rolling back means restoring the backup taken before the update. That is exactly why step 1 of this guide is a named backup.
Can Bedrock players join a Java 26.3 server?
Yes, through Geyser, provided Geyser is up to date for protocol 777. The matching Bedrock version is 26.50. The full procedure is covered in our guide on running Bedrock and Java together with Geyser.
How long does the world conversion take?
From a few seconds on a fresh world to several minutes on a world of several gigabytes. The server looks frozen during that time: that is normal, let it finish.
Wrapping up
26.3 is a low-risk update for a vanilla or plugin server, provided you keep the order: named backup, plugin and mod inventory, version change without formatting, supervised first start, rollback ready. Heavy modded servers are better off letting the ecosystem get ahead.
If you are starting a fresh server for the occasion, our guide on creating a Minecraft server in 2026 covers the install from scratch. Our plans run from 8 GB of RAM at 4.99 EUR incl. VAT per month to 32 GB at 21.99 EUR incl. VAT for a large modpack, with 16 GB at 8.99 EUR incl. VAT for a plugin server and 24 GB at 15.99 EUR incl. VAT for a modded server. Every version installs from the Version tab of the panel.