Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated last month
All versions
26.10.5
Release
MeowEco 26.10.5last month 2
Compatibility
Minecraft: Java Edition
26.2
26.1.x
Platforms
Paper
Purpur
Changes
MeowEco Economy 26.10.5
This release adds optional VaultUnlocked v2 support while preserving the existing Classic Vault integration.
Added
- Added a VaultUnlocked v2 economy provider with UUID accounts, multiple currencies, transfers, exact amount validation, and asynchronous operations.
- Added regression coverage for Classic Vault and VaultUnlocked v2 interoperability, precision boundaries, progressive transfer tax, rollback, concurrency, and async shutdown.
- Added a direct GitHub Issue button to the project header.
Changed
- Classic Vault and VaultUnlocked v2 balance mutations now share the same economy service, database transaction path, and audit metadata.
- Updated the README, Modrinth project description, and plugin metadata to document the new compatibility.
- Kept VaultUnlocked v2 optional; servers without its API continue using Classic Vault as before.
Fixed
- Rejected v2 amounts that cannot be represented at the configured currency precision or by the existing double-backed storage.
- Coordinated asynchronous v2 operations with plugin shutdown and deferred database close when a running operation needs more time to finish.
- Scoped intentional Classic Vault deprecation handling to compatibility code, explicitly marked legacy VaultUnlocked overrides as deprecated, and removed unused audit-scope resource warnings.
Compatibility
- Paper 26.1.x / 26.2
- Java 25
- Classic Vault remains supported.
- VaultUnlocked v2 is supported as an optional integration.
Download
- Download the compiled plugin JAR from Modrinth versions.
- GitHub Release contains release notes only and intentionally has no build-file attachments.
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:U3hXvwy8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:M9JO0TFv:U3hXvwy8"
}

