Creators
Details
Licensed MIT
Published 9 months ago
Updated 5 months ago
All versions
2.1.0
Release
EzBoost 2.1.05 months ago 49
Compatibility
Minecraft: Java Edition
26.1.x
1.21.x
Platforms
Bukkit
Folia
Paper
Spigot
Changes
Added
- Folia compatibility: EzBoost now supports Folia servers via a
FoliaSchedulerabstraction that routes task scheduling through Folia'sGlobalRegionScheduler/ entity schedulers when the Folia runtime is detected. - Boost top leaderboard (
/boosttop): tracks and displays the top boost buyers using a Jaloquent-backed persistent storage layer. - Jaloquent storage backend: replaced the previous
BoostStorageabstraction with a fully Jaloquent-backedEzBoostRepositoryfor consistent flat-file persistence across all storage operations. storage.debug-loggingoption (storage.yml, defaultfalse): suppresses verbose Jaloquent console output (Queried X rows,Saved model…). Set totrueto re-enable for debugging.- Paper 1.21 smoke-test: CI matrix now includes Paper 1.21.11 alongside Paper 26.1.2, Folia, Spigot, and Bukkit.
Changed
api-versionlowered from26.1.2to1.13so the plugin loads on any Spigot/Paper 1.13+ server without an api-version warning or rejection.- Java compiler target lowered from 25 to 17 for wider JDK compatibility.
AsyncChatEvent(Paper-only) replaced withAsyncPlayerChatEventfor Spigot compatibility.- Plugin version lookup changed from
getPluginMeta().getVersion()togetDescription().getVersion()for broader server compatibility. - CI smoke-test pass condition now also verifies
Enabling EzBoostappears in the server log, preventing a false pass when the server starts but rejects the plugin due to an incompatible api-version.
Fixed
YamlDataStore.query()corrected to handle Jaloquent's flat key format.storage.ymladded topom.xmlresource includes so it is correctly packaged.- Vault is now fully optional: economy class access and listener registration are guarded so the plugin loads cleanly without Vault present.
Optional dependencies
Any compatible version
Any compatible version
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:hxlosrDv:rH71GZ8G"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:hxlosrDv:rH71GZ8G"
}

