Reference
Engines and versions
Which server software and Minecraft versions you can target.
You choose a game, an engine and a version when you start a project. Modloom only offers combinations that have a published server API to build against, so a missing version is not an oversight in the picker.
Engines#
Modloom builds for three server engines. Folia is not supported.
| Engine | Versions | Builds | Experimental |
|---|---|---|---|
| Paper | 26.3 to 1.9.4 | 33 | 26.3, 26.1.1 |
| Purpur | 26.3 to 1.16.5 | 24 | 26.3 |
| Spigot | 26.3 to 1.8.9 | 36 | None |
The list above is read from the same definitions the app uses, so it always matches the picker.
Some builds of the newest releases are marked experimental in the picker because the engine itself is in alpha or beta. Expect rough edges there.
Java versions#
Each Minecraft version is compiled with a matching Java toolchain, chosen for you.
| Minecraft version | Compiled with | Your server needs |
|---|---|---|
| 1.8 to 1.16 | Java 8 | Java 8 or newer |
| 1.17 | JDK 17 targeting Java 16 | Java 16 or newer |
| 1.18 to 1.20.4 | Java 17 | Java 17 or newer |
| 1.20.5 to 1.21 | Java 21 | Java 21 or newer |
| 26.x | Java 25 | Java 25 or newer |
Run your server on at least the Java version in the last column, or the plugin will fail to load.
What a new project contains#
A new project is generated for your engine and version with a Maven build, a plugin.yml and a starter class. The server API is a provided dependency, so it is not bundled into your jar. The api-version in plugin.yml is set to match your target where the server supports it. See Project structure.
The agent also loads guidance for your target so it writes against the right API era: legacy, flattening, modern and newer component-based APIs each differ.
Compiling a combination is not the same as testing it. The wide version matrix has been checked for published dependencies, not exercised on live servers. Test on your own server before you rely on any build.