Tags
Creators
Details
1.6.1
Compatibility
Changes
Savs Common Economy v1.6.1 Release Notes
⚠️ Important
If you are updating an existing server: This update is a full rewrite to support Minecraft 26.1.
While it is fully backward compatible, we recommend backing up your config folder and database (if using one) before upgrading.
- Your existing
savs-redis.json,worth.json, andshops.jsonfiles will automatically migrate to the new formats. Savs-Redis-Libis no longer required as a standalone mod and can be safely deleted.
Please report any bugs or issues on the Issue Tracker.
New Features
Minecraft 26.1 Support
The entire codebase has been ported and rewritten for Minecraft 26.1.
Native Redis Synchronization
Redis PubSub for cross-server balance synchronization is now built natively into the core mod.
Permissions System
The mod has been updated to interface with the Fabric Permissions API v0.7.0. You can securely control access to all commands via mods like LuckPerms. A permissions.json configuration file has also been added as a fallback, letting you adjust the required Vanilla OP Level for commands if you aren't using an external permissions manager.
Buy & Sell Split Market
Server-direct trading has been expanded. We've added a /buy command to complement /sell. The worth.json configuration now separates buyPrices and sellPrices. When migrating from old versions, your new buyPrices will safely default to double your current sell rates.
Quality of Life
Event-Driven Shop Computations
Shop signs have been optimized to use an event-based system. They now only refresh exactly when stock is changed, eliminating the previous background looping scans.
Full Changelog
Compatibility: Minecraft 26.1 (Fabric) Server-Side Only: No client installation required
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:NFdebgJ8:pytaO7Ac"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NFdebgJ8:pytaO7Ac"
}

