Minecraft 26.3 and your server: breaking changes and when to update

Minecraft Java Edition 26.3 Wilderness Bound was released on 15 September 2026. For anyone running a server that is not the signal to update, but to plan. The interesting side of 26.3 is not the new blocks: it is a set of breaking changes that make datapacks, recipes and command blocks fall over hard — and the question of which server software is actually ready a few days after release.

What shipped on 15 September

After ten snapshots, three pre-releases and three release candidates, the final version landed on 15 September 2026 under the name Wilderness Bound. The datapack format in the release is 121.0 and the resource pack format 97.1. Note that Pre-Release 1 was still on 119.0, so anyone who aligned their packs with the pre-release has to bump that number one more time.

The release also carried a handful of late fixes, among them VSync, the server resource pack settings and sprint attacks. Bedrock 26.50 shipped on the same day (with the 26.51 hotfix a day later), so Java and Bedrock players get the same content. What that update means for a Bedrock server — and why players suddenly cannot join — is covered in Bedrock 26.50 and your server.

What is actually getting added

The centerpiece is a new biome: the dappled forest, an autumnal woodland with poplars, red shrubs and fallen trees. Poplar wood gets the full set — logs, wood, planks, stairs, slabs, signs and hanging signs, buttons, pressure plates, doors, fences, gates, trapdoors and shelves, plus poplar boats and boats with chest. The leaves come in red, orange and yellow. Poplars also grow shelf mushrooms, small and large, and you bounce off them if you land on one.

There are also wool stairs and slabs in all sixteen colors with sound-dampening properties, concrete stairs and slabs in sixteen colors, and cushions: non-solid entities you can sit on. The straw bed is a single-use bed crafted from hay bales that does not set your spawn point. A new structure, the abandoned camp, generates in seventeen forest and taiga-like biomes with a variant per biome type, holding chests, barrels and explorer maps. New explorer maps cover Ancient Cities, mineshafts, desert pyramids, warm ocean ruins and abandoned camps across eight biomes. Realms owners can now create and manage invite codes.

One thing gets misreported a lot in coverage: the 25-chunk render distance is a Realms feature. Realms owners get two separate sliders for render and simulation distance. If you host your own server, you have had view-distance and simulation-distance as separate settings in server.properties for years. 26.3 changes nothing there.

The breaking changes that hit datapacks hardest

This is where the real work is. The best-known one is the recipe field cookingtime: it used to be optional with a default of 200 and is now required. Every cooking recipe in your datapacks without that field will break. Number providers have also been split into separate integer and float registries to avoid precision loss, with a long list of new math providers added. That touches loot tables — where rolls and bonus_rolls are now number providers themselves — villager trades, and any custom provider you have written.

Block state providers have been renamed, so simple_state_provider is now just simple, and they can be standalone registry types. More annoying is the entity predicate format: it has been rebuilt as a data component map, the type field is now minecraft:entity_type, and unknown sub-predicates are rejected instead of being silently ignored. That turns working datapacks into hard failures instead of quiet wrong behavior: better long term, painful on update day.

/team modify and /waypoint modify now only accept color names in lowercase with underscores: dark_purple works, darkpurple does not. That breaks old command blocks and scripts. All custom fuels have to be redefined using the new component format. The world generation noise fields have been renamed (firstOctave became base_octave, amplitudes became amplitude_modifiers), which is serious porting work if you run custom worldgen. And /publish has lost its gamemode argument. If you ship resource packs with modified terrain shaders, expect them to break outright: terrain.vsh and terrain.fsh have been rewritten.

New tooling for server admins

Two commands have been added. /compute evaluates number providers with context; it requires an explicit integer or float type, and dividing by zero fails the command instead of returning anything. The same applies to /data compute. /posteffect toggles post-processing shaders on or off for a player.

Thirteen new data components have landed as well, among them minecraft:attack_animation, minecraft:block_transformer, minecraft:brewing_fuel, minecraft:cooking_fuel, minecraft:mob_visibility and minecraft:sign_text_front. Fuel handling for cooking also changes: leftover material now drops on the ground if fuel remains, or stays in the slot once the fuel runs out. If you run automated furnace arrays, retest it rather than assume.

When to update, and when definitely not to

Three days after release, support looks like this: Fabric has a stable 26.3 loader, Paper offers 26.3 only as experimental builds (the latest stable Paper is 26.2, build 124), Purpur follows Paper and therefore has the same status, NeoForge is on 26.3.0-beta and Forge has nothing for 26.3 yet. ViaVersion 5.12.0 supports 26.3 since 18 September. If you are torn between Paper and Purpur, we compared them in Paper versus Purpur.

So the advice stays boring and unchanged: do not run a production server on experimental builds. If you play vanilla or Fabric without heavy mods, go ahead. If you run Paper with plugins, wait for a stable Paper build and for plugins that name 26.3 explicitly; on 26.2 that broader plugin support took about a week. A plugin that worked on 26.2 can still break because of Paper's own API cleanup: being recent is not enough, it has to name your version. If you run a modpack, do not update individual mods but wait for an official release of the pack.

And remember that world conversion has been one-way since 26.1: a world saved on 26.3 may never come back to 26.2. Make a backup first and test on a separate instance with a copy of your world — we described a workable approach in backup strategy for your Minecraft server. Turn auto-updaters off as well: an updater that quietly lifts your server to an experimental 26.3 build is exactly what you do not want right now.

Keeping players on older clients connected

ViaVersion 5.12.0 supports 26.3, so a server that is already on 26.3 can simply let players on 26.2 or older in. For most plugin servers the reverse setup is smarter for the next few weeks: keep the server on 26.2, update ViaVersion, and players who have already moved their client to 26.3 can still join. Once Paper is stable, you update in one go with everything tested. If you run Geyser for Bedrock players: Geyser presents itself as a 26.2 client, so on a 26.3 server Geyser needs ViaVersion — on a 26.2 server it works without extras.

A practical checklist for the next few weeks

What you can do now: make a backup, spin up a test instance on 26.3 with a copy of your world, and grep your datapacks for cooking recipes without cookingtime, for old provider names and for color names without underscores; set your pack formats to 121.0 and 97.1. Go through your plugin list for explicit 26.3 support, update ViaVersion to 5.12.0 and hold the live server until Paper has a stable build. If you are still on 1.21 or older, note that servers have needed Java 25 or higher since 26.1; anyone already on 26.2 changes nothing there.

The figures in this article come from minecraft.wiki (Java Edition 26.3) and from the download pages of Paper, Fabric, NeoForge, Forge and ViaVersion on 18 September 2026.