1.3.2
Compatibility
Changes
CeraEconomy 1.3.2
Fixed
- Fixed YAML ↔ MySQL migration.
- Fixed migration path.
- Fixed migration handling for UUID, player name, and "BigDecimal" balance.
- Added migration logs for imported/skipped accounts.
- Migration flags now automatically reset after a successful migration.
Migration Configuration
When using migration, only enable the migration flag that matches your configured "type".
If "type: yaml":
type: yaml mysql-to-yaml: true yaml-to-mysql: false
If "type: mysql":
type: mysql mysql-to-yaml: false yaml-to-mysql: true
«⚠️ Important: Never set "mysql-to-yaml" and "yaml-to-mysql" to "true" at the same time. This can cause the migrations to overwrite each other and may result in data being overwritten or lost.»
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:dnmoqsQ3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:lfNCaCGD:dnmoqsQ3"
}
