Start here
Versions and platforms
Minecraft version scope, Java requirements, platform support and the current limits of the ArionAC beta.
Minecraft version scope
The current version allowlist covers these releases. Availability of a detector or physical correction is narrower than this installation scope.
| Series | Releases in scope |
|---|---|
| 1.20.x | 1.20, 1.20.1, 1.20.2, 1.20.3, 1.20.4, 1.20.5, 1.20.6 |
| 1.21.x | 1.21 through 1.21.11 |
| 26.x | 26.1, 26.1.1, 26.1.2, 26.2; 26.3 is in development |
Older Minecraft releases, snapshots, April Fools releases and unlisted future versions are outside this scope. Sharing a client protocol does not prove that two native versions have identical mechanics.
Server platforms
| Platform | What to expect |
|---|---|
| Spigot | Use the standard server plugin. Optional Paper APIs must not be required for loading. Verify the exact server build in your staging environment. |
| Paper | Use the standard server plugin. Paper-specific capabilities are checked by version and availability. |
| Purpur | Use the standard server plugin. Non-vanilla options and mechanics may require explicit integration; the server name alone does not authorize arbitrary movement. |
| Folia | Validation is ongoing. The ordinary public beta does not advertise folia-supported. A separate validation build and targeted tests are not a complete production approval. |
Java requirements
| Server version | Runtime guidance |
|---|---|
| 1.20–1.20.4 | Meet the server platform’s Java requirement; this plugin targets Java 17 bytecode. |
| 1.20.5–1.21.11 | Use the Java runtime required by the actual server distribution, normally Java 21 or newer. |
| 26.x | Java 25 or newer is required by these Minecraft servers. |
Use the platform’s supported runtime, even if the plugin’s own bytecode can load on an older Java release. The Java used to build the project and the Java required to run Minecraft are different requirements.
Prediction and correction availability
The beta’s guarded packet-prediction correction route accepts matching native client/server pairs for 26.1, 26.1.1, 26.1.2, 26.2 and 26.3. This runtime scope is separate from completed gameplay validation: 26.3 remains in development. Incomplete world history, unconfirmed state, unsupported poses, possible pushing and unreliable synchronization withhold correction authority. Earlier releases and translated connections can remain observation-only.
A matching prediction result does not automatically mean the engine has enough information to correct a player. An unknown result is not treated as proof of cheating. Loading a version library or accepting a protocol does not establish full gameplay acceptance.
ViaVersion and Bedrock
ViaVersion is optional. A translated client may require different packet, impulse and movement handling. ArionAC does not assume that an older protocol selected in a modern client recreates the older game’s native physics. A missing translation capability makes the affected decision inconclusive.
Geyser/Floodgate players are exempt by default. With geyser.EXEMPT-BEDROCK-PLAYERS: true and an empty EXEMPT-CATEGORIES list, the exemption covers all categories. Changing that setting does not establish reliable Java-model detection for Bedrock.