Minecraft 26 Plugins: The Calendar Versioning Guide

Calendar versioning: why 1.22 never happened

Minecraft dropped the 1.x numbering in favour of calendar versioning. The first number is the year, the second is which release of that year it is. The latest version is 26.2, published on 16 June 2026 under the name Chaos Cubed. So there is no 1.22 to wait for: 26.x is what comes after the 1.21 family.

The practical fallout is that "the latest 1.x" is no longer a usable way to describe a target. When you look for a plugin, or when you describe the one you want built, you need a specific calendar version. The gap between 26.1.2 and 26.2 is not cosmetic: on the Paper side, 26.1.2 has a stable build and 26.2 does not.

• Current version: 26.2, released 16 June 2026, codenamed Chaos Cubed
• The first number is the year, not a generation counter
• Always state your exact version when describing a plugin

Which version to build against, according to the numbers

A bStats sample of 62,948 servers gives the real spread: 1.21.11 accounts for 36.4% of servers, 26.1.2 reaches 14.9%, 26.2 sits at 7.4%, and 1.21.4 is still on 7.2%. The 1.21 family is by a wide margin the most represented, and in that sample the calendar versions have not taken over.

That gives you two clear answers. If your server has actual players on it, the sane production target on the 26.x side is 26.1.2, because Paper 26.2 has no stable build. And if you are releasing a plugin for other people, building only for 26.2 cuts you off from most of the fleet. Keeping 1.21 compatibility is not nostalgia, it is where the servers are.

• 1.21.11: 36.4% of the measured fleet
• 26.1.2: 14.9%, the most installed calendar version
• 26.2: 7.4%, recent and without a stable Paper build
• 1.21.4: 7.2%, still very much alive

Java 25 or Java 21: which floor do you target?

Java 25 is the floor for the calendar versions. If your server runs 26.x, that is the runtime you need, with no room for negotiation: an older JDK will not start the server at all.

The bytecode level you compile your plugin to is a separate decision. Targeting Java 21 still makes sense, because that is what the majority of the fleet runs, and a .jar compiled for 21 loads fine on a newer runtime. The reverse does not hold: a plugin compiled for 25 refuses to load on a Java 21 server and throws an unsupported class version error at startup.

• Runtime for a 26.x server: Java 25 at minimum
• Sane compile target for a plugin you distribute: Java 21
• Compiling too high locks the plugin out of older servers

Adventure 5: why your 1.21 plugin stopped compiling

Paper 26.x ships Adventure 5, and that release removed APIs that had previously only been deprecated. The consequence is blunt: code written for 1.21 may no longer compile at all against the 26.x API. This is a build failure rather than something you discover in game, which is the better of the two outcomes.

It is the classic trap when you lift a snippet from a tutorial or an old repository. It was written for 1.21, it looks correct, and it simply will not build. Adventure covers messages and the text shown to players, so that is the code to re-read first.

• Adventure 5 removed deprecated APIs outright, it did not just flag them
• Code targeting 1.21 can fail to compile against 26.x
• Treat any pre-26.1 tutorial as something to re-check, not copy

Deobfuscation, the dead remapper, and the libraries: block

Minecraft has been deobfuscated since 26.1, and Paper's remapper is gone. The whole dance of remapping a plugin so it lines up with the real class names on the server no longer has a purpose. One less stage in the build chain, and one less source of cryptic startup failures.

The second method change is dependencies. The libraries: block in plugin.yml replaces shading. Instead of bundling an entire library into your .jar and hoping it does not collide with another plugin's copy, you declare it and the server fetches it. Smaller .jar, and two plugins that need the same library no longer each carry their own copy of it.

• Minecraft has been deobfuscated since 26.1
• Paper's remapper no longer exists
• Declare dependencies in libraries: instead of shading them
• Folia schedulers are still required for multithread compatibility

How Minax builds a plugin for 26.x

You describe the plugin in plain English: the behaviour you want, the commands, the permissions, and above all your exact server version. Minax writes real Java code, compiles it, and hands you a .jar. When compilation fails, a self-correction loop reads the errors, fixes the code, and rebuilds. That loop is precisely what you want facing APIs that Adventure 5 removed.

Then you test the plugin online before touching your own server. It is the only honest way to find out whether the commands do what you thought you asked for. Folia schedulers are emitted for multithread compatibility, so a plugin aimed at a Folia server does more than compile, it respects the threading model that server expects.

• Name your version: 26.2, 26.1.2, or a specific 1.21 build
• Name your platform: Paper, Spigot, Bukkit, or Folia
• Get the compiled .jar and run it online first
• Refine in one sentence, then drop it into /plugins

Frequently asked questions