All versions
1.2.1
Release
Economy Machina 1.2.12 months ago 121
Compatibility
Minecraft: Java Edition
26.2
26.1.x
1.21.x
1.20.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
[1.2.1] — 2026-08-29
Compatibility verification against the newest server builds of the current Minecraft release. No feature or behavior changes.
Verified
- Latest 26.2 builds — the plugin is checked against Spigot 26.2, Paper 26.2 build 121, and Purpur 26.2 build 2627. Every Bukkit API the plugin touches remains present and unchanged on those builds; the supported range stays 1.20 – 26.2.
- The jar is still compiled against the 1.20.4 API on Java 17 by design — one jar covers every server from 1.20 through 26.2. Building against the 26.x API would require a Java 25 toolchain and drop older servers.
Fixed & Hardened
- Build-qualified version strings — Paper and Purpur 26.1.2+ report
Bukkit.getBukkitVersion()as26.2.build.2627-stable/26.1.2.build.63-stablerather than the legacy26.2-R0.1-SNAPSHOTform (PaperMC/Paper#13885).VersionAdapter.parseVersion()already read these correctly; that behavior is now pinned by tests so it cannot regress. - Version parsing can no longer throw — a missing or non-numeric version segment now reads as
0instead of raisingNumberFormatException. An unrecognized version string from a future server build degrades gracefully instead of breaking plugin startup.
Project
- Test suite 54 → 59 — five new
VersionAdaptercases covering both build-qualified forms, their equivalence to the legacy spelling, a two-digit minor (1.21.11), and the defensive non-numeric paths. The monotonic-ordering test now spans build-qualified strings too. - Docs refreshed — README and the Modrinth page state the verified builds, and note that the plugin talks only to the standard Vault
Economyinterface (so it should also run under VaultUnlocked at the API level, untested). - Dependencies unchanged. Adventure 4.26.1 is the final release of the 4.x line and
adventure-platform-bukkit4.4.1 is current; Adventure 5.x is a major version and is deliberately not adopted in a patch release.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:TFWq7WxH:bJcTkvxE"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:TFWq7WxH:bJcTkvxE"
}

