Tags
Creators
Details
Licensed GPL-3.0-only
Published 7 months ago
Updated 2 months ago
All versions
2.2.0
Release
EmakiCorelib 2.2.07 months ago 21
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
2.2.0 - 2026-04-08
Overview
This version focuses on fixing the optional dependency loading for EconomyManager, constituting a compatibility and stability update.
Changed
- Adjusted the economy backend registration process.
VaultandCoinsEngineProviders are no longer directly hard-referenced and instantiated during the construction phase. EconomyManagernow checks whether the corresponding plugin is enabled and if the required API classes are visible before deciding whether to register an optional Provider.- The
CoinsEnginerelated Provider has been changed to load reflectively based on runtime state to avoid premature class linking.
Fixed
- Fixed the issue where, when
CoinsEngine / ExcellentEconomyis not installed on the server,EmakiCoreLibwould throw aNoClassDefFoundErrorduring theonEnablephase due to the absence ofsu.nightexpress.excellenteconomy.api.ExcellentEconomyAPI. - Fixed the issue where, despite
CoinsEnginebeing declared insoftdepend, the economy bridge class would still fail at runtime because it was resolved prematurely. - Fixed the issue where CoreLib could not gracefully degrade to a "register only available Providers" state when optional economy dependencies are absent.
Compatibility
- Although the repository for
ExcellentEconomyis namedExcellentEconomy, the server plugin registration name and build artifact identifier still useCoinsEngine. - The existing
softdepend: CoinsEngineconfiguration remains correct; no need to change it toExcellentEconomy. - Existing syntax in action DSL such as
provider=vault,provider=coinsengine, andcurrency=...remains compatible.
Migration
- No configuration migration is required.
- No data migration is required.
- No command, permission, or language file adjustments are needed.
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:EGYz2X2a:6oZDsYcs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:EGYz2X2a:6oZDsYcs"
}

