1.0.0
Compatibility
Changes
🚀 v1.0.0 - The Initial Release
Launching the high-performance economy foundation
This is the official first release of EIZZOs-Tokens! This version establishes a robust, asynchronous foundation for server owners who need a reliable way to manage multiple currencies without sacrificing server performance.
✨ New Features
-
Multi-Currency Engine – Create and manage unlimited unique tokens (e.g., Gems, Vote Points, Crystals).
-
Interactive GUIs
-
Player Wallet: A clean, paginated menu for players to see all their balances at once.
-
Admin Dashboard: Manage player balances and token settings directly in-game.
-
Vault & PAPI Support – Seamlessly display balances in scoreboards and hook into existing economy-based plugins.
-
Asynchronous Database Core – All data handling for SQLite and MariaDB is moved off the main thread to ensure 20.0 TPS.
⚙️ Technical Details
Click to view technical implementation details
- Optimized Data Pooling: Utilizes HikariCP for high-performance MariaDB connections.
- Smart Caching: Player data is cached locally upon login to minimize database queries.
- Fail-Safe Storage: Local SQLite is the default for "plug-and-play" setup.
Developer Note: This is the first stable release. If you encounter any issues or have feature requests, please report them via our GitHub Issue Tracker.
🛠 Commands Added
/tokens— Opens the personal wallet UI./tokens admin— Opens the administrative management menu./tokens give/take/set— Full control over player balances via command or console./tokens reload— Reloads the configuration and token files instantly.
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:XtuGZBjj:hnnyAA3E"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XtuGZBjj:hnnyAA3E"
}

