08/01/2026

Minecraft 26.1, 26.2, 26.3 — what happened to 1.21? (2026)

• Minecraft
• Guides

If you opened the Paper download page and saw 26.2 instead of 1.21, nothing is broken. Mojang changed how versions are numbered in early 2026: the old 1.x scheme is closed, and versions are now counted by year. And if your server refuses to start after updating, the reason is almost certainly Java 25. Below is both — plus the things most people miss before touching their server.

How versions are numbered now

The format is year.drop.hotfix. First number is the year, second is which game drop of that year it is, and the third only shows up if something needed fixing. So 26.1.2 means 2026, first drop, second hotfix.

The main thing to remember: there is no Minecraft 1.26. Search for it and you will find nothing useful. Mojang explained the new system officially, and the old numbering stopped at 1.21.x.

Where things stand: Java Edition is on 26.2, Bedrock on 26.35.

Java 25 — the wall everyone hits

From 26.1 onward Minecraft requires Java SE 25. Not 21, not 17 — 25. The wiki lists it as a hard requirement for 26.1, and the same goes for everything newer.

For players this is a non-issue, because the launcher ships its own Java. For you as a server owner it matters, because the server jar runs on whatever Java your start script points at — nothing else.

Here is what it looks like when it is wrong: the server dies instantly with Unsupported class file major version, or literally Minecraft 26.1 and newer requires Java 25. If you see either message, stop looking — that is your answer.

The fix is two steps: install JDK 25, then point your start script at it. Paper has its own guide for installing Java. Paper itself now requires Java 25 too, so there is no way around it.

One tip from experience: check what actually launches your server, not what is installed on the system. On machines with several Java versions those are two completely different things — and it is the most common reason someone installs Java 25 and nothing changes.

Do Aikar's flags still apply? Yes.

This is the confusion I see every week now. Word got around that Minecraft switched from G1GC to ZGC, so people conclude their flags are obsolete and rush to move the server to ZGC.

Don't. That garbage collector change applies to the launcher and client, not to server guidance. Paper still officially recommends Aikar's flags, still on G1GC.

When ZGC genuinely makes sense: large heaps, roughly 24 GB and up, with a full server and constant chunk generation. That is where generational ZGC takes out the GC lag spikes and you feel it. Below that, G1GC with Aikar's flags stays the better choice for most servers — private ones essentially always.

If you are unsure how much RAM you need in the first place, I covered that in how much RAM a Minecraft server needs.

Why plugins break differently now: the end of obfuscation

This is the biggest technical change of 2026 and the least discussed. 26.1 is the first fully unobfuscated release — Mojang now ships real class, method and field names.

The consequences are concrete. Paper dropped its internal remapper entirely, because obfuscated names simply no longer exist in the server jar. Fabric moved to Mojang's official mappings, which makes Parchment redundant.

What this means for you: plugins still break when the API changes, and that will never stop. But one whole category of breakage looks different now — the kind where a plugin touches NMS and falls apart on every new version because of mappings. When a plugin developer tells you in 2026 that they need time to port, it is more often real API changes than remapping.

Which server software to run at all is its own topic — I compared them in Paper, Purpur, Fabric or Forge.

Before you update: there is no going back

This is the section I wanted to write the whole post for. Once you bring a world up to 26.1 or newer, you cannot take it back to an older version. Paper states it plainly: backups are mandatory, and downgrading after a world upgrade is not possible.

On top of that, 26.1 changed world storage — dimensions now live in separate folders. If you have backup scripts or tools that expect the old layout, check them before you need them.

Here is how I do it, in order:

• Back up the whole folder — world, configs, plugins. Not just the world, because a config without its plugin is worth nothing.
• Clone the server to the side and update the copy. Never the live one first.
• Wait for the Paper build and for plugins to follow it. That is usually a few days to a week after a drop lands.
• Only then touch the real server — and not on a Friday night.

Updating on release day is the fastest known way to spend your weekend without a server.

Java and Bedrock numbers no longer match

It used to be safe to assume Java and Bedrock sat at roughly the same number. Not anymore. The same content ships as Java 26.3 and Bedrock 26.50 — and right now Java is on 26.2 while Bedrock is on 26.35.

For most people that is trivia. It matters if you run crossplay through Geyser, because then you are tracking both sides at once. How to set that up from scratch is in my crossplay guide for Java and Bedrock.

What your server should be running right now

• Java Edition 26.2 — the current game version. Bedrock is on 26.35.
• Java SE 25 — mandatory from 26.1 up, no exceptions.
• Paper — stable 26.2 builds exist, grab the latest. Build numbers climb constantly, so always take the newest stable rather than copying a number out of someone else's guide.
• NeoForge — follows the game version, so 26.1.0.x for 26.1.
• Fabric Loader — the latest stable, alongside Mojang's official mappings.
• Plugins — check every one before you update, not after. The ones I put on every server are in essential Paper plugins.

Next up: 26.3 and the Dappled Forest

The third drop of 2026 ships as Java 26.3 and Bedrock 26.50, expected somewhere between mid-September and mid-October. Mojang has not locked a date. Snapshots are already out so you can test ahead, and the planned-versions list is kept on the wiki.

The content is autumnal: a new biome called the dappled forest with poplar trees, shelf mushrooms and red shrubs, plus wool stairs and slabs and a new abandoned camp structure.

One practical note that will save you some grief: the new biome only generates in new chunks. In an existing world you will not see it around spawn, only once you travel far enough out. If you want players to see it immediately, that is a reason to start a new world or push the world border — not a sign your update failed.

What to skip

• Don't search for "Minecraft 1.26". It doesn't exist. The version is 26.x.
• Don't confuse it with Education Edition. If you run into "26.30 Learning Cubed, August 2026" — that is Minecraft Education, a different product, and it has nothing to do with your server.
• Don't switch to ZGC just because you read that the GC changed. For most servers G1GC with Aikar's flags stays better.
• Don't update on release day. Wait for the Paper build and the plugins.
• Don't touch the live world without a backup. There is no downgrade.
• Don't assume the Bedrock number matches the Java number. It doesn't anymore.

Where to run all this

The new numbering is cosmetic — what actually decides whether your server survives a drop is Java 25, a backup before the upgrade, and the patience to wait for plugins. On mcbalkan the Java version is already sorted, backups run on their own, and when something breaks you talk directly to me — no ticket queue, no bot. See our Minecraft hosting.