1.3.0
Compatibility
Changes
CeraEconomy 1.3.0 ā Changelog
š Added
- Added MySQL storage support.
- Added HikariCP connection pooling for MySQL.
- Added automatic creation of the following database tables:
- "ceraeconomy_accounts"
- "ceraeconomy_transactions"
- Added YAML ā MySQL migration.
- Existing YAML balances are automatically imported into MySQL when the corresponding account does not already exist.
- Added MySQL connection configuration:
- Host
- Port
- Database
- Username
- Password
- Pool size
- SSL toggle
š§ Improved
- Improved storage initialization order to ensure Storage is loaded before Economy.
- Improved MySQL connection handling with automatic connection pooling.
- Economy data is now persisted directly to MySQL when MySQL storage is enabled.
- Improved player-name persistence in MySQL.
- Improved startup logging for storage initialization and migration.
š Fixed
- Fixed the "Storage is not loaded before Economy" startup error.
- Fixed a missing HikariCP dependency in the final plugin JAR.
- Fixed MySQL storage initialization and table creation issues.
- Fixed YAML account data potentially being lost when switching to MySQL by introducing automatic YAML ā MySQL migration.
ā ļø Notes
- YAML ā MySQL migration is supported.
- MySQL ā YAML migration is not currently supported.
- Existing MySQL accounts are never overwritten during YAML migration.
- It is recommended to keep your existing YAML data as a backup when switching to MySQL.
š¦ Version
CeraEconomy 1.3.0
Storage Upgrade
CeraEconomy 1.3.0 introduces MySQL support while keeping YAML storage available for servers that prefer a simple file-based setup.
You can start with YAML and migrate your existing economy data to MySQL when needed, without rebuilding player accounts from scratch.
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| CeraEconomy-1.3.0.jar | Unknown | 4.48 MiB |
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:lfNCaCGD:n9yol8Xa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfNCaCGD:n9yol8Xa"
}
