Quick answer: There is no Minecraft 1.22 and there never will be. Mojang switched to year based version numbers in 2026: the first digit pair is the year, the second is the game drop of that year, the third is the patch. So 26.1 is the release that would have been called 1.22, 26.1.2 was a patch on it, and 26.2 is the second drop of 2026 and the current version. The scheme applies to Java and Bedrock alike.
If you have looked at server lists lately you have seen the confusion in action. One server advertises 1.21.11, the next one 26.2, a third says 26.1.2, and half the comment sections are people asking which of those is newest. Here is the whole story in one place.
How the new numbers work
The format is year, then drop, then patch:
| Version | What it is |
|---|---|
| 1.21.11 | The last release under the old naming |
| 26.1 | First game drop of 2026, the would-be 1.22 |
| 26.1.2 | Second patch on that drop |
| 26.2 | Second game drop of 2026, current as of this writing |
The reasoning from Mojang's announcement comes down to two things. They moved to smaller, more frequent game drops instead of one huge yearly update, and under the old scheme that would have produced an endless tail of 1.21.x numbers that said nothing about when anything came out. A year based number is self explaining: 26.2 tells you the year and the release at a glance.
The same scheme now covers Bedrock, which used to run its own unrelated numbering. For crossplay servers that is a quiet quality of life win, since both editions finally speak the same version language.
What this means if you run a server
For a vanilla, Paper, or Purpur SMP: run the latest drop. Paper builds follow each game drop closely, and the smaller drop sizes mean plugin breakage between versions has gotten milder than in the big update era. Our own panel lists the current drop as soon as a stable Paper build exists.
For modded: ignore the new numbers, follow your modpack. Mod ecosystems settle on specific versions and stay there for years. The big Forge packs still live on 1.20.1 (Beyond Depth for example), and the Cobblemon world sits on 1.21.1 (Cobbleverse runs Fabric 1.21.1). A modded server on an "old" version is not outdated, it is on the version its mods target. Nothing about the naming switch changes that.
Mixed player versions: ViaVersion still does what it always did. If your players are spread across 1.21.x and 26.x clients, ViaVersion on a Paper server lets newer clients join an older server. The name format changed, the compatibility tooling did not.
And please put your version in your server ads. The most upvoted complaint on r/MinecraftServer this month is server posts that never mention a version. With two naming schemes in circulation it matters twice as much now.
FAQ
Is 26.2 newer than 1.21.11? Yes. Everything starting with 26 comes after everything starting with 1.21. If the number looks like a year, it is the new scheme.
Will there be a Minecraft 1.22? No. That release shipped as 26.1.
Do my old worlds work on 26.x? World upgrades work like they always have: newer versions load older worlds, never the other way around. Take a backup before upgrading, exactly as you would have between 1.20 and 1.21.
What version should a new server pick in 2026? Vanilla or plugins: the current drop, 26.2. Modded: whatever version your modpack targets, and that is normal. If you start a server with us the panel preselects a sensible current version and you can switch freely.
Does this change anything for Geyser crossplay? No. Geyser tracks both editions like before, only the labels are aligned now. Setup is unchanged from our crossplay guide.