Minecraft 26 plugin generator for 26.1.1, 26.1.2, 26.2 and 26.3

After 1.21.11, Minecraft Java Edition left the long-running 1.x numbering behind. Versions now start with the year, 26 for 2026, followed by the drop number within that year and, for fixes, a third number. That is where 26.1.1, 26.1.2, 26.2 and 26.3 come from.

For server owners the change goes beyond looks. Scripts, build files and tools that parse "1.x" version strings had to be updated, and anything assuming the first number is always 1 needed rework.

Spaleforce's version list covers both lines: 1.16 through 1.21.11, then the 26.x releases, with 26.3 marked as the latest.

A plugin compiles against a server API artifact. For years, Paper and Purpur published theirs as "version-R0.1-SNAPSHOT". For 26.x they moved to build-numbered versions, and their repositories do not offer 26.x under the old naming, so a build file copied from a 1.21 project fails to resolve.

When you choose Paper or Purpur on a 26.x version, Spaleforce looks up the latest matching API build, preferring a stable one, and uses it for the build. Spigot still publishes its 26.x API under the old naming, so Spigot and Bukkit projects resolve as before.

If Paper or Purpur has not published a build for your version yet, the plugin is compiled against the Spigot API instead, so the project still builds.

Minecraft servers have raised their Java requirement over time: Java 17 from 1.18, Java 21 from 1.20.5, and Java 25 for the 26.x line. The 26.x server API itself ships as Java 25 class files, so compiling against it takes a recent JDK.

You do not have to install any of it. Compilation runs on our servers with a toolchain that can read those files, and the plugin is built at a Java level suited to the version you picked. On your side, just make sure the server runs the Java version its software asks for.

An AI that does not know the target writes what it has seen most, which for Minecraft plugins means older releases. The result compiles against the wrong API or uses names that changed long ago: in 1.21.3, for example, GENERIC_MAX_HEALTH became MAX_HEALTH, and code that mixes both eras does not build.

Spaleforce tells the AI which version it is writing for, and the compiler then checks the code against the real API of that version. Anything that does not exist there shows up as an error and is fixed automatically before you download.

If your plugin depends on something added in a specific 26.x release, select that release or a later one and name the feature in your description.

A plugin compiled for 1.21.x is not guaranteed to work on a 26.x server. If it relies on anything that changed, it fails when it loads or when that code runs. Test before switching a live server.

The simplest route is to generate the plugin again for the 26.x version you are moving to, starting from the same description, and keep the 1.21 project untouched for servers you have not upgraded. From the editor you can also start a Minecraft test server and pick among the versions it offers.