1.2.0
Compatibility
Changes
CeraEconomy 1.2.0
⨠What's New
š New Data System
- Added a new versioned plugin folder: "CeraEconomy-1.2.0"
- Configuration and data are now stored inside the versioned folder.
- Economy data is separated into the "data" folder.
š Daily Transaction Logs
- Replaced the old single "transactions.yml" system.
- Transactions are now automatically separated by date.
- Each day gets its own transaction file:
transactions/ āāā index.yml āāā 2026-08-10.yml āāā 2026-08-11.yml āāā ...
This prevents the transaction file from becoming extremely large on long-running servers.
š° Economy Improvements
- Improved decimal money support.
- Uses precise "BigDecimal" calculations.
- Supports up to the configured decimal places.
- Improved balance formatting.
- Economy limits remain configurable:
- Starting balance
- Minimum balance
- Maximum balance
š Vault
- Improved Vault integration.
- Vault bridge has been tested successfully.
- Supports deposits, withdrawals and balance checks through Vault.
š¾ Auto Save
- Economy data is automatically saved according to the configured interval.
- Transaction data is saved automatically after transactions.
š ļø Fixes
- Fixed configuration loading with the new versioned data system.
- Fixed transaction persistence.
- Fixed economy persistence.
- Fixed decimal balance handling.
- Fixed Vault economy bridge issues.
- Removed obsolete 1.1.3 active configuration references.
ā Tested On
- Paper 1.21.11
- Vault integration enabled
- Decimal economy enabled
- Daily transaction storage
- Economy auto-save
š Version
CeraEconomy 1.2.0
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:zMBcaFYj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfNCaCGD:zMBcaFYj"
}
