Tags
Creators
Details
2.0.0
Compatibility
Changes
Highlights
This release requires Minecraft 26.1 and Java 25. Upgrading from 1.x requires a fresh installation due to storage and configuration changes.
What's New
Minecraft 26.1 & Java 25
- Updated to Paper API 26.1 and Java 25 compiler target.
- Updated bStats, JaCoCo, and all dependencies to versions compatible with Java 25.
Database Refactor — Jaloquent ORM
- Replaced raw JDBC with the Jaloquent ORM library for all database access.
- MySQL storage now uses a proper connection pool with cleaner query building.
- Added automatic schema migration system — the database updates itself on startup.
- Tax history is now stored in a dedicated
tax_historytable. - YAML stats backend retained as the default for servers that don't use MySQL.
Tax History Command
- New
/eztax historysubcommand: paginated transaction history for any player. eztax.command.history— view your own history.eztax.command.history.others— view another player's history as an admin.
EzSeasons Integration
- Optional integration with the EzSeasons plugin via soft-dependency.
- When a season resets, EzTax logs a summary containing the season dates and tax totals collected.
Startup Log Improvements
- Cleaner, structured startup output — no more double
[EzTax]prefixes. - Jaloquent internal log spam suppressed on startup.
- Each subsystem now reports its active state on a single line:
Storage: MySQL (table: tax_history),Economy: X via Vault,Permissions: X via Vault. - Final confirmation line:
EzTax v2.0.0 enabled.
Vault Hook
- Improved economy and permissions provider detection logging.
- Transaction tax economy wrapper activation and deactivation is now logged explicitly.
Bug Fixes
- Fixed shading of Micrometer and Prometheus libraries bundled with Jaloquent to prevent
NoClassDefFoundErroron server startup.
Developer / Build
- Maven Shade Plugin upgraded to 3.6.2.
- JaCoCo upgraded to 0.8.14 (Java 25 support).
- GitHub Pages documentation site added (just-the-docs theme).
- CI workflow now clones and installs MockBukkit from source before building, since the dev build is not published to any Maven repository.
Optional dependencies
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:1dSu4W6Q:QIdiGVob"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:1dSu4W6Q:QIdiGVob"
}

