Minecraft 26.3 Server Update: Geyser, Paper, Fabric and Java 25

Published on | Updated

Does Geyser support 26.3? Yes, since 2.12.0 on October 14. Current Geyser, Paper and Fabric builds for 26.3, plus Java 25, the whitelist default and NetherNet.

A snowy Minecraft mountainside with spruce trees

Minecraft 26.3, the Wilderness Bound drop, came out on September 15, 2026. If your server has Bedrock players, your first question is probably whether Geyser supports it yet, and right after that whether Paper and Fabric do. Here are the answers with the current builds, followed by the rest of what 26.3 changes for whoever runs the server. The new blocks and mobs are in our Wilderness Bound post.

Quick answer: Yes, Geyser supports Minecraft Java 26.3, since Geyser 2.12.0 build 1255 on October 14, 2026. On October 31 the GeyserMC download page offers 2.12.1 build 1279, from October 30, for Java 26.3 and Bedrock 26.40 to 26.60. Paper 26.3 has been stable since build 175 on October 11, and Fabric runs 26.3 on loader 0.20.1 with Fabric API 0.165.0+26.3. Two more things trip server owners up: a new 26.3 server starts with the whitelist on, and since Bedrock 26.60 came out on October 27, Geyser needs NetherNet switched on.

Does Geyser support 26.3?

Yes. The first change GeyserMC lists for Geyser 2.12.0 build 1255, published on October 14, 2026, is "Version bumps for Java 26.3". So if you are waiting for Geyser to update to 26.3, it already has, and the builds since then add fixes and Bedrock updates on top. This is where Geyser, Floodgate, Paper and Fabric stood when we checked on October 31, 2026:

  • Geyser: 2.12.1 build 1279 from October 30 is the newest build on the download page, for Java 26.3 and Bedrock 26.40 to 26.60. Type geyser version in the console to see your build and whether a newer one exists.
  • Floodgate: 2.2.5 build 141 from September 17, the build that updated to 26.3, is still the newest (GeyserMC builds).
  • Paper: 26.3 has been in the STABLE channel since build 175 on October 11, and build 231 from October 30 is the newest. It needs Java 25 (PaperMC builds).
  • Fabric: loader 0.20.1 from October 19 is the stable loader, and Fabric API 0.165.0+26.3 came out on October 23 (Fabric Loader 0.20.1, Fabric API). Geyser-Fabric runs only on a 26.3 server and needs Fabric API in the same mods folder, as GeyserMC's setup page says.

Geyser imitates a Java client of the version it supports, so a server only accepts Geyser if it accepts 26.3 clients (supported versions):

  • On Paper 26.3, update Geyser and Floodgate and you are done.
  • On a Paper server that stays on 26.2, add ViaVersion 5.12.0 or newer, so the server accepts the 26.3 client Geyser now imitates.
  • On Fabric or NeoForge, GeyserMC writes that Geyser-Fabric and Geyser-NeoForge only support the latest Java version. A modded server that stays on 26.2 cannot run the current Geyser mod; GeyserMC points to ViaProxy with Geyser-ViaProxy for that case.

The bigger change since October 14 is on the Bedrock side. GeyserMC's NetherNet post of October 8 says Bedrock 26.60 stops Bedrock clients from connecting over RakNet, and 26.60 came out on October 27, 2026. Geyser builds from 1237 on support NetherNet, and it needs a TCP port next to the UDP port. Build 1273 (October 26) added Bedrock 26.60 and makes NetherNet the default only in new configs: a config that already says transport: raknet keeps it. A Geyser server that has not switched loses its Bedrock players. Our NetherNet guide walks through the switch.

Bedrock version numbers look like Java's but are a separate series. Bedrock 26.30 is not Java 26.3: Geyser build 1273 removed support for it, so a Bedrock player still on 26.30 has to update the game.

If you run a Bedrock Dedicated Server instead of Geyser, keep it on the current build. Mojang's Bedrock 26.50 changelog already made NetherNet the default transport for dedicated servers. Our Geyser and Floodgate guide covers the crossplay setup itself.

What else changes for server owners

  1. A new 26.3 server starts with the whitelist on. Add players with whitelist add <name> or run whitelist off. A server you update from 26.2 keeps the setting it had.
  2. 26.3 needs Java 25, just like 26.1 and 26.2. If you come from 1.21.x, Java changes too.
  3. As checked on October 16, NeoForge publishes 26.3 builds without the beta suffix, and Purpur builds from 2650 on are no longer marked experimental. Check plugin and modpack support separately.
  4. Back up before you update. A world that has been upgraded to 26.3 cannot go back to 26.2.

The October 1 and October 16 tables further down are kept for comparison. Geyser, Floodgate, Paper and Fabric were rechecked on October 31, 2026; the other findings carry the date of their own check.

New servers start with the whitelist on

Under Server Properties, Mojang's 26.3 changelog has a single line: "The white-list property is now true by default."

A default only matters when the server creates server.properties from scratch. If you update an existing 26.2 server, its server.properties already has a white-list= line, and that value stays. The servers that get caught are brand new ones, and servers where someone deleted server.properties to start clean.

On those servers, anyone who is not on the list is disconnected. A vanilla server shows "You are not white-listed on this server!". Paper, Spigot and Purpur take the text from spigot.yml instead, and the default there is "You are not whitelisted on this server!" (PaperMC docs). Operators still get in, because ops are automatically whitelisted, as the Minecraft Wiki notes. So if you made yourself op first, you can join while your friends cannot. That looks like a connection problem. It is a setting.

To let your friends in, add them from the console:

whitelist add Steve
whitelist add Alex
whitelist list

In the console you type commands without a slash. In game, as an operator, it is /whitelist add Steve. The player does not need to be online.

To open the server to everyone, run whitelist off. The server writes that to server.properties itself, so it stays off after a restart. Setting white-list=false in the file and restarting does the same. On Space-Node you do both from the panel: commands in the live console, and server.properties in the file manager.

For a server that is only for friends, the new default is the sensible one. Leave it on and add the people who play.

Java 25, and what changes if you come from 1.21.x

Mojang publishes a small version file for every release, and it names the Java version the game needs. For 26.3 that is Java 25. It was the same for 26.1 and 26.2. The last version on Java 21 was 1.21.11. Paper lists Java 25 as the minimum for its 26.3 builds as well.

If your server runs 26.1 or 26.2 today, Java stays as it is. If it runs 1.21.x, switch to Java 25 before the first start on 26.3. On an older Java the server stops straight away. Paper prints this:

Minecraft 26.1 and newer requires running the server with Java 25 or above.

A vanilla server stops with an UnsupportedClassVersionError that mentions class file version 69.0, which is the Java 25 class format.

In the Space-Node panel you pick the Java version in the Startup tab. If Java 25 is not in the list for your server, ask us in live chat before you update.

Coming from 1.21.x on Paper, two more things change. Since 26.1, Paper keeps the Nether and the End inside world/dimensions/ instead of separate world_nether and world_the_end folders (PaperMC 26.1 notes), so backup scripts and tools that use the old folder names need new paths. Multiverse worlds move into that folder too, and our guide to the Paper 26 dimensions folder shows where they end up and what to back up first. And if you copied ZGC flags from a Java 21 setup, drop -XX:+ZGenerational, which is obsolete on Java 25. Our ZGC vs G1GC guide has flag sets for both Java versions.

Removed log lines

The changelog also says "some log lines that server software might look out for have been removed" and points to the Minecraft Server Management Protocol instead. Mojang does not say which lines.

The line panels watch to see that a server has finished starting, the one that ends in For help, type "help", is still in the 26.3 server jar. If you run something else that reads the console, such as a bot that tails the log for joins and leaves or a script that reacts to certain messages, test it after the update.

Smaller changes from the changelog

  • Mobs that do not despawn now stop their random walking and swimming when no player is near, the same way other mobs already did.
  • Mojang lists better chunk generation performance and faster structure locating. It also fixed a bug where locating a structure created an empty region file for every candidate chunk in terrain that had not been generated yet (MC-311323).
  • level.dat now keeps a version_history list with the world's earlier data versions.
  • The data pack version is now 121.0, so data packs made for 26.2 may need an update. One example from the changelog: signs no longer run click events in custom text by themselves.
  • PaperMC writes in its 26.3 post that it plans to merge almost all Bukkit, Spigot and Paper config options in 26.4. Nothing changes in 26.3, but expect some config work on the next update.

Where the server software stood on October 1

Software26.3 status on October 1, 2026
VanillaReleased September 15, needs Java 25 (Mojang)
PaperBeta since build 134 on September 28, build 142 on October 1. The download page still offers 26.2 as the main version (PaperMC)
PurpurBuilds since September 16, every one marked experimental (Purpur)
FabricStable loader 0.19.5 and Fabric API 0.161.0+26.3 (Fabric, Modrinth)
NeoForge26.3.0.40-beta (NeoForged)
Forge66.0.9, no recommended build yet (Forge)
Velocity4.2.0 supports 26.3 (PaperMC)
GeyserSupports Java 26.2; the 26.3 update is not released yet (GeyserMC)
ViaVersion and ViaBackwards5.12.0 added 26.3 on September 18 (ViaVersion, ViaBackwards)

Paper and NeoForge check on October 12, 2026

The official Paper download service now lists Minecraft 26.3 build 175 in the STABLE channel. It was published on October 11 at 15:32:14 UTC, or 17:32:14 in the Netherlands. The Paper download page offers that build, and its commit records the promotion to stable. The earlier beta status in the October 1 table is historical.

NeoForge's official Maven index lists 26.3.0.76 without a beta suffix. Its release-bot notice was posted on October 11 at 19:46:53 UTC, or 21:46:53 in the Netherlands. That confirms a published version without the suffix; it is not an explicit STABLE channel designation like Paper's.

These releases replace the earlier advice to wait for Paper's stable promotion or NeoForge's beta suffix to disappear. They do not tell you whether your plugins, modpack, proxy or Geyser setup will work. Java 25 remains the requirement for 26.3, as Paper's current documentation confirms. Keep a recoverable pre-update backup and test the intended combination on a copy. Check Purpur's own release information separately; Paper's promotion does not verify another project's current build status.

Status on October 16, 2026

Software26.3 status on October 16, 2026
PaperSTABLE since build 175 (October 11); build 200 on October 16 (PaperMC builds)
PurpurBuilds 2650 (October 13) and 2651 carry no experimental flag; the main download page still opens on 26.2 (Purpur API)
FoliaOne ALPHA build, build 3 on October 14 (PaperMC builds)
SpigotBuilds exist; BuildTools needs --rev 26.3, because its "latest" file still points at 26.2 (Spigot versions)
FabricLoader 0.19.5 is stable, Fabric API 0.163.0+26.3 came out on October 14 (Fabric, Modrinth)
NeoForge26.3.0.86 on October 16; the beta suffix ended at 26.3.0.75-beta (NeoForged Maven)
Forge66.0.12 on October 14, still no recommended build (Forge)
Velocity4.2.0 supports 26.3 and needs Java 25; the 3.x line stops at 26.2 (PaperMC docs)
Geyser2.12.0 build 1255 (October 14) added Java 26.3 (GeyserMC builds)
Floodgate2.2.5 build 141 (September 17) updated to 26.3 (GeyserMC builds)
ViaVersion and ViaBackwards5.12.1 (October 8) fixes several 26.2 and 26.3 translation bugs (ViaVersion)

Plugins and mods

A stable server jar does not mean your plugins are ready. This is what the download pages listed on October 1, with the rows we rechecked on October 16 or 31 marked:

Plugin or mod26.3 status
LuckPermsLists 26.3 since 5.5.85 (September 19); 5.5.87 is current (checked October 16)
WorldGuard7.0.19 (September 18) lists 26.3. It needs WorldEdit, which now has a full 26.3 release (checked October 16)
WorldEdit7.4.6 release on October 15 supports 26.3; before that only betas did (checked October 16)
DiscordSRVLists 26.3
BlueMap5.28 (September 25) lists 26.3
ChunkyLists 26.3
Simple Voice ChatThe Paper plugin 2.6.24 supports 26.3; the Fabric and NeoForge builds for 26.3 are still beta (checked October 16)
CoreProtectv24.1 (September 24) added 26.2 support; still no 26.3 release on October 31
EssentialsXStill no release for 26.3: 2.22.0 (May 31) is the newest on October 31. The dev builds have had 26.3 support since September 15 (checked October 16)
DynmapNo release for any 26.x version. Paper 26.3 support exists only on a community branch, without a release (checked October 16)
Lithium0.26.3 (October 28) lists 26.3 on Fabric and NeoForge (checked October 31)
CreateThe newest Minecraft version on its page is 1.21.1

Sources: the version lists on Modrinth, the GitHub releases of CoreProtect and EssentialsX, the EssentialsX dev builds, WorldEdit 7.4.6 and the Dynmap commits. WorldGuard's install page lists WorldEdit as a requirement.

Players ask about their own mods too. On October 31, Sodium 0.9.2 and Iris 1.11.7 had 26.3 releases for Fabric and NeoForge, and Replay Mod 2.6.28 supports 26.3 on Fabric. OptiFine still had no 26.3 build, not even a preview: its newest file is a preview for 26.2 (Replay Mod, OptiFine). Our 26.3 performance mods list has the current build of each performance mod. Those are client mods, so they do not block the server update, but a player who depends on OptiFine may want to stay on 26.2 through ViaBackwards for a while.

A plugin that does not list 26.3 may still load. Plenty do. Others load and then fail the first time they meet a new block or item. A test copy shows you which kind you have. A live server full of players is the wrong place to find out.

Cushions need their own check. They are entities, not blocks: Mojang's changelog calls them "Cushion entities", and Paper 26.3 added new events for breaking them. If you rely on a claim or protection plugin, check that its changelog covers cushions before you open the server again.

Modded servers follow a simpler rule: run the version your mods or your modpack target. All The Mods 10 runs on 1.21.1, and the ATM11 beta (0.9.0, September 19) targets 26.1.2, not 26.3. Moving a modpack server to 26.3 is the pack author's call. When a new pack version does come out, our modpack update guide shows how to update without losing the world.

How to update safely

  1. Decide whether you need 26.3 now. A modded server, or one that leans on a plugin without a 26.3 release, such as CoreProtect, can stay on 26.2 for a while. Players who already updated their game can still join a 26.2 Paper server through ViaVersion 5.12.0, which added 26.3 clients. A crossplay server on 26.2 needs ViaVersion as well, because current Geyser builds imitate a 26.3 client, and a modded crossplay server needs 26.3 or ViaProxy, as the Geyser section above explains.
  2. Make a backup in the panel. Also download the world over SFTP, so one copy lives off the server. PaperMC calls backups "absolutely mandatory" for this update, because a world upgraded to 26.3 cannot be downgraded.
  3. Test on a copy first, on a second server or on your own PC, and copy the world folder as well. A world upgraded to 26.3 cannot go back to 26.2, so the upgrade itself is what your test has to cover. Our test server guide explains how to set one up.
  4. If you come from 1.21.x, set Java 25 in the Startup tab.
  5. Set the server to 26.3 in the panel and start it. If the version or build you want is not offered yet, ask us in live chat.
  6. Watch the console for the first minute. Missing dependencies, plugins that refuse to load and Java errors all show up there. Stop the server with stop rather than a force kill: Mojang's open bug MC-312008 says that if a 26.3 server dies in the middle of a save, files in data/ such as scoreboard.dat or game_rules.dat can be left empty.
  7. Open server.properties and check white-list. On an updated server it should still have its old value.
  8. Join with two accounts, yours and a friend's. Check inventories, claims, ranks and a trip through a Nether portal.
  9. Keep the pre-update backup until the server has run for a week or so with real players.

FAQ

Why can nobody join my new 26.3 server?

New 26.3 servers start with white-list=true in server.properties. Players who are not on the list are disconnected with "You are not white-listed on this server!", or "You are not whitelisted on this server!" on Paper, Spigot and Purpur. Add them with whitelist add <name> in the console, or run whitelist off to open the server.

Does Minecraft 26.3 need Java 25?

Yes. Mojang's version file for 26.3 names Java 25, as it did for 26.1 and 26.2, and Paper lists Java 25 as the minimum for its 26.3 builds. 1.21.11 was the last version on Java 21.

Is Paper 26.3 out?

Yes, and it is stable. Paper 26.3 moved to the STABLE channel with build 175 on October 11, 2026, and build 231 from October 30 was the newest on October 31. It needs Java 25. Plugin, modpack and crossplay compatibility still need their own checks.

Can I go back to 26.2 after updating?

Not with the same world. PaperMC writes that you cannot downgrade a world after upgrading it to 26.3. Restore the backup you made before the update instead.

Can players on 26.3 join a 26.2 server?

On Paper, yes, if the server runs ViaVersion 5.12.0 or newer, which added support for 26.3 clients. Without ViaVersion, the client and the server need the same version.

When will Geyser update to 26.3?

It already has. Geyser 2.12.0 build 1255 added Java 26.3 on October 14, 2026, and 2.12.1 build 1279 from October 30 was the newest build on October 31. Geyser-Fabric and Geyser-NeoForge come from the same builds and run only on 26.3. Use Floodgate 2.2.5 build 141 or newer, the build that updated to 26.3. Then switch Geyser to NetherNet: Bedrock 26.60 came out on October 27, and GeyserMC says Bedrock clients stop connecting over RakNet with it. Our NetherNet guide covers that switch.

Sources

All opened on October 31, 2026:

The checks from October 1 to 27 link their sources in the text where they are used.

Related guides

Running a server on 26.3? See the Minecraft plans: Java and Bedrock, NVMe storage, DDoS protection and 9 regions to choose from.