Minecraft 26.3 Wilderness Bound: new features and updating your server

On 15 September 2026 Minecraft 26.3 left the snapshot stage and reached everyone as a full release under the name Wilderness Bound. After weeks of testing camps on separate instances, we finally have something you can put on a server where people actually play. Let us walk through what the update brings to the game, and then through the things a server owner usually finds out about only when something stops working.

A new forest and everything growing in it

The headline addition is the Dappled Forest biome, which generates near cold biomes. Poplar trees grow there in three leaf variants: red, orange and yellow. Each variant has its own falling leaf particles in a matching colour, and saplings collected from one tree can grow into any of the three colours, so plantations on your server will always come out a little random.

Fallen trunks generate alongside standing poplars, and shelf mushrooms grow on both of them, a new kind of mushroom in two sizes. The smaller one grows with bone meal, the larger one drops two items when broken. You can cook stews with them like with any other mushroom, and they bounce slightly when stepped on, with a sound of their own. Under the trees you will find red shrubs and leaf litter, while the wandering trader now offers both poplar saplings and shelf mushrooms.

The mobs need no introduction: sheep, chickens, cows, pigs, rabbits and foxes. The interesting part is that they show up in their cold variants, which gives the forest a coherent mood and makes it immediately clear this is not just another forest with a different leaf texture.

Abandoned camps across eighteen biomes

The structure that looked identical everywhere throughout the snapshots finally got variants matched to its surroundings. Abandoned camps generate in eighteen biomes, from meadows and cherry groves, through various kinds of taiga and birch forest, to swamps, savannas, pale gardens and sparse jungles. Some pieces are shared by every variant, the rest depend on the location. Inside, chests and barrels with loot are waiting.

From a survival server point of view this is the best thing in the whole update, because it gives players a concrete reason to leave spawn. The camps are small, scattered and require no knowledge of any mechanic, so they work for everyone, from a veteran to somebody in their first week.

Explorer maps are their own items now

Alongside the camps, Mojang rebuilt the entire map system. Until now an explorer map was an ordinary filled map with a different name. Each one now has its own item and its own icon, from the ocean monument map, through the ancient city and mineshaft maps, to the abandoned camp map. Maps found in old worlds convert into the matching new items on load, so nobody loses anything.

One change may catch you out: explorer maps and buried treasure maps can no longer be zoomed out, neither in a crafting table nor at a cartography table. Only maps in the #minecraft:extendable_maps tag can be extended. If a plugin or datapack on your server counted on the old behaviour, that is the first place to check after updating.

Cushions, straw beds and wool stairs at last

Three additions the builders on your server will appreciate more than everything else combined. Cushions are crafted from three wool slabs, come in sixteen colours and can be sat on. They have no collision, so they overlap other objects happily, though not one another. Pistons cannot move them, and they break when the block underneath is gone.

The straw bed, in turn, is a single use bed. You sleep through the night without setting your respawn point, and the bed falls apart afterwards. Three hay bales give you four of them, but in the Nether and the End an attempt to sleep destroys them with no effect. For servers with a fixed spawn or adventure maps this is genuinely useful, because you can finally let players skip the night without juggling commands.

On top of that, every wool colour and every concrete colour received stair and slab variants. Wool stairs and slabs still dampen vibrations like the full blocks, and concrete ones can be cut in a stonecutter. The building palette grows by dozens of entries and it shows immediately once somebody starts on interiors.

What this version changes on the server side

Here comes the part no trailer shows. The most important detail sits in server.properties: the white-list property now defaults to true.

The second thing matters to anyone building automation on top of logs: some of the lines server software used to watch for in the console have been removed. Mojang points to the server management protocol instead, which reached 3.1.0 in this version and gained notifications about a full world upgrade on startup, from started, through progress, to finished or failed. If an event you rely on is missing, the official route is a feature request on the feedback site.

There are also two changes that simply work in your favour without any configuration. Locating structures and generating chunks both got faster, which you will feel everywhere players like to sprint into the unknown. On top of that, mobs marked as persistent now stop their random walking and swimming when no player is nearby, exactly as ordinary mobs have behaved for a long time. On a server with elaborate farms and hundreds of named mobs that is real relief for the main thread, though do not treat the update as a substitute for tuning. If your server stutters, start with the settings in paper.yml and spigot.yml, where there is usually far more to gain.

Worth noting as well: level.dat now holds a version_history list with the earlier data versions of the file. Diagnosing a world that has been through several updates becomes a good deal less mysterious.

Signs no longer run commands on their own

This change deserves its own paragraph, because it touches security. Signs no longer execute click events stored in their text by default, and text components on newly placed signs are no longer resolved by default. The new allow_op_features field brings the old behaviour back, and it is off by default.

Signs placed in worlds saved before this version get that field set to on, so your existing sign based menus survive the update. Every new sign, however, needs the field set explicitly. If you build a hub, a lobby or a shop around clickable signs, write this down, otherwise you will lose an hour wondering why a freshly placed element does nothing while an identical one next to it works perfectly.

Pack formats and the key technical changes

The stable release closes a long run of changes that moved through the snapshots starting at format 108.0. The numbers now look like this:

On the data side, most of the action is in loot tables and everything that uses them. Types with a dedicated registry now accept an inline value, an identifier, a list of identifiers or a hash prefixed tag, and lists may mix inline values with references. The number provider registries were split into separate ones for integers and floats. Pottery sherds and potion recipes became data driven, and the block state fields Name and Properties are now called id and properties.

New and changed commands

The posteffect command was added, applying postprocessing effects defined in a resource pack to a player screen. The server has no way of knowing whether a player actually has such a pack, so treat it as a bonus for the community playing with your resource pack, not as a mechanic you can build gameplay on. A compute command also appeared, evaluating number provider values in various contexts, and data modify gained a matching source.

The item command now takes a slot source instead of a single slot and gained fill and override subcommands, which handle a mismatch between slot count and item count differently. execute gained a slots condition. The gamemode argument is gone from publish, as the default game mode is now set with defaultgamemode or the button in world options. spreadplayers relies on the #entities_can_teleport_to block tag, so it stopped scattering players onto signs and structure void.

Transparency and a new windowing backend

Two things stand out on the client side. The Improved Transparency setting now enables an order independent transparency algorithm, OIT for short. It solves the old problems with objects vanishing behind glass or water, but at a higher performance cost than the previous approach, and it introduces minor new artefacts in return, such as slightly wrong cloud colours seen through several translucent layers. The toggle sits under F3 + X, so a player on weaker hardware can simply turn it off.

The other one is GLFW being replaced by SDL3 for window management, input and platform integration. Key bindings now rely on the physical position of keys rather than layout dependent codes, which ends a years long annoyance for anyone not on a US layout. Borderless fullscreen became the default and no longer requires a restart when switching, and on Linux the game uses Wayland when it is available.

Fixes you will notice during shared play

The list of fixed bugs in the full release is enormous, because it collects everything from more than a dozen weeks of testing. A few entries have exceptionally long beards or touch servers directly:

Smaller conveniences came along too: suspicious stew and mushroom stew are now crafted with any two mushrooms, new villager trades refresh even while you are trading with them, and the player icon on maps always shows the direction you are facing. Players in spectator mode finally pass through portals, which for anyone moderating a server is a change felt every single day.

Update the server or wait?

This is no longer a snapshot, so the answer differs from what it was all summer. Updating is worth it, though not the same afternoon the version came out. Engines like Paper need a few days, and plugins need more, since the changes to loot tables, item components and signs touch exactly the places add-ons like to meddle with.

• Back up the world and the configuration before you touch anything. A world saved on 26.3 cannot be moved back to an older version.
• Go through your plugin list and see which ones already have a 26.3 build and which stay silent. One missing add-on can hold up the whole update.
• Review your datapacks against format 121.0, with particular attention to loot tables, predicates and potion recipes.
• If you have clickable signs in a lobby or a shop, plan for setting allow_op_features on newly placed elements.
• Make sure you know how white-list is set in your server.properties, especially if you are building an instance from scratch.
• Plan new terrain for your players, because without it the dappled forest and the camps stay nothing more than news they read about.

How to move to 26.3 at MineHost

1. 1

   Make a backup from the panel

   Before changing the version, copy the world and the configuration. It is one click, and it is your only way back if things go differently than you expected.
2. 2

   Put a copy of the world on a test instance

   Run 26.3 on a copy first, not on your main world. You will see which plugins start without console errors before your players do.
3. 3

   Switch the engine version in the panel

   Once the tests look good, switch the version on the main server. Installing the engine and changing versions happens in the browser, with no manual file uploads.
4. 4

   Review the configuration after the first start

   Check server.properties, the whitelist in particular, and read the logs for plugins complaining about missing methods.
5. 5

   Open new terrain for your players

   Push the world border out or prepare a separate exploration world so the dappled forest and the abandoned camps have somewhere to generate.
6. 6

   Announce it like an event

   Write on Discord what exactly was added and where to find it. An update nobody hears about brings nobody back.