All versions
1.0.5
Release
EconomyShop by ilius 1.0.56 months ago 55
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Folia
Paper
Purpur
Changes
EconomyShop v1.0.5 — Persistent item settings + sell-to-shop fix
Features
Item settings now persist when you delete and re-add
- Items removed via the admin GUI are soft-removed instead of permanently erased
- Re-adding the same material to the same category restores its previous price, stock mode, dynamic-pricing flags, and every per-item setting exactly as you left them
- A new "Restored" chat message confirms when this happens (distinct from the regular "Added")
- Old soft-deletes auto-purge after 90 days alongside the existing transaction-purge dashboard action
- Database migrates automatically on first boot — no config changes needed
Bug Fixes
Sell-To-Shop "Exclude from Sell All" visual not updating
- Right-clicking an item in
/shop sellto exclude it from Sell All correctly toggled the exclusion, but the red ✘ "Excluded" lore line and missing glow never appeared - Now the lore and glow update on every right-click as expected
- The exclusion itself was always working — Sell All did skip excluded items — only the visual feedback was broken
- Caused by Paper changing inventory item access to return a snapshot rather than a live reference
Crash-window dupe vector in /shop sell hand and /shop sell all
- Both commands deposited money before removing items, opposite of the canonical sell order
- A server crash mid-transaction could have left a player with both items and money
- Now items removed first, money deposited last
- The GUI sell paths (
/shop sellbutton, sell-confirmation GUI) were already correct — this brings the command paths in line
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:zR6c1YxT:kdWQFCXq"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:zR6c1YxT:kdWQFCXq"
}

