Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated last month
All versions
26.10.0
Release
MeowEco 26.10.02 months ago 43
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Paper
Purpur
Changes
MeowEco Economy 26.10.0
This release adds guarded balance migration and a persistent audit trail for Paper 26.1.x / 26.2 servers running Java 25.
Added
- Dry-run migration from any live Vault economy provider, including common EssentialsX, CMI, XConomy, and The New Economy setups.
- Offline EssentialsX userdata migration and standard CSV migration.
- Automatic CSV backup before every applied migration and a single database transaction for the complete import.
- Persistent transaction audit records with source, actor, transaction ID, amount, before/after balance, and frozen-balance state.
/meco audit <player> [currency] [limit]and/meco audit export [limit].- Optional bStats integration with storage, currency-count, and language charts after a project id is configured.
- GitHub Actions verification for tests, compatibility compiles, and the release jar.
Changed
- English is now the default message language. Chinese servers can set
messages.language: "zh_CN"and run/meco reload. - The marketplace name is now MeowEco Economy for clearer search discovery; the plugin id, data directory, commands, API, and placeholders remain
MeowEcocompatible. - The Modrinth page now starts with positioning, five product benefits, a compatibility table, and a three-minute install path.
Fixed
- Failed balance mutations and failed migrations do not create audit records.
- Transfer and exchange audit rows share one transaction id across both affected accounts or currencies.
- Modrinth loader metadata no longer claims direct Bukkit or Spigot compatibility for the Paper-only build.
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:M9JO0TFv:svP5HeMr"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M9JO0TFv:svP5HeMr"
}

