Tags
Creators
Details
All versions
1.5.0
Release
EconomyCraft 1.5.0 - NeoForge - 26.1.23 weeks ago 26
Compatibility
Minecraft: Java Edition
26.1.x
Platform
NeoForge
Supported environments
Server-side
Singleplayer
Required content
Changes
Features
- Added support for 26.1.2 and 26.2.
- Added optional placeholder support for other mods (TAB, HUD mods, etc.), exposing
economycraft:balance,economycraft:balance_formatted, andeconomycraft:daily_sell_remaining - Added
/sell everythingto sell your entire inventory at once - Added a
sell_enabledconfig option to disable/sellentirely /shop list <price>now accepts an optional<amount>, to list only part of a held stack- Server shop now shows the sell price alongside the buy price, and supports selling directly from the menu (right-click, or shift-click for a stack)
- Order requests can now be fulfilled partially from the Orders UI, not just in full
Improvements
- Selling an enchanted item now asks for confirmation first, since enchantments don't add to the sell value
- The orders confirm screen only opens if you actually have items to give; the player shop confirm screen only opens if you can afford the purchase
- Server shop entries that fail to load are now logged with their item id instead of silently showing as unavailable
prices.jsonnow cleans up stale/renamed entries and sorts newly added ones into their category automatically, instead of leaving them at the bottom of the file
Fixes
- Fixed splash and lingering potions (e.g. Splash Potion of Healing) showing as unavailable in the server shop
- Fixed the Potion of Wind Charging showing as unavailable and refusing to sell
- Fixed the balance scoreboard reclaiming the sidebar on every balance change (even while disabled), which could overwrite another plugin's or mod's own sidebar
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:djm50zsL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:H4o5bO7g:djm50zsL"
}


