Tags
Creators
Details
All versions
1.6.0
Release
EconomyCraft 1.6.0 - NeoForge - 1.21.11last week 7
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Features
- Added a
balance_separatorconfig option to customize the thousands separator used wherever a balance is displayed - Added
top_name,top_balance, andtop_balance_formattedleaderboard placeholders (e.g.%economycraft:top_name 1%for the richest player) /sellnow routes to an open order instead of the server whenever that order pays more per item, before falling back to the server price for the rest/shop,/servershop, and/orders(including the claim screen) now show a preview for filled shulker boxes (hover the item and press Ctrl+Q), letting players see the contents- Server shop (
prices.json) entries can now carry acomponentsfield for items that need specific NBT (custom names, enchantments, shulker boxes with contents, etc.); add a#labelsuffix to the key (e.g.minecraft:shulker_box#loot_rare) to sell several different variants of the same item /orders request <item>now tab-completes to any item id, vanilla or modded
Improvements
- Simplified
shop.json/orders.jsonstorage by dropping redundant top-level item fields (item identity now comes only from the existingstackfield) - Shop and order deliveries are now stored in one shared
deliveries.jsoninstead of being duplicated insideshop.jsonandorders.json, with any pending deliveries migrated automatically on first load /shoplistings and/ordersrequests now consistently show newest first, instead of an unspecified order
Fixes
- Fixed a PvP kill-reward exploit by a misconfigured
pvp_balance_loss_percentage - Fixed the same class of bug in
taxRate - Fixed
/dailydeducting money instead of granting it ifdailyAmountwas configured negative - Fixed a crash on startup, and in
/daily, from a corrupted null entry inbalances.jsonordaily.json - Fixed a shop listing or order request with unreadable item data becoming a stuck "phantom" delivery that reappeared as an unclaimed item on every login
- Fixed a duplication exploit in the deliveries/claim screen
- Fixed
/orders request <item>being unable to request modded items at all
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:H4o5bO7g:C0jy7bfk"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H4o5bO7g:C0jy7bfk"
}


