Tags
Creators
Details
1.1.7-Beta
Compatibility
Changes
Version 1.1.7-Beta (July 21, 2026)
Added ā Premium
- Personal Vault ā a password-protected physical currency chest. Right-click a Vault block to open. Requires premium license.
- PIN entry via a click-based keypad using custom numbered player-head skulls.
- Native vault block sounds: activate, unlock, wrong-pin, eject, close.
- Craftable via configurable
shape+ingredientsrecipe (default: 8Ć netherite ingot + 1Ć chest). - Data stored in
vaults.ymlwith async writes. - Developer API to check or modify vault balances, set or verify passwords, and check password status.
- GUI fully configurable in
gui.yml(vault-gui,vault-password-gui). Settings and crafting stay inconfig.yml. - Vault hologram ā when a player looks at a vault block (within 5 blocks), a floating
TextDisplayhologram appears above it showing the stored currency balance(s) in the format{color}{symbol} {name}: {amount}. Disappears immediately when the player stops looking at it. Toggled viavault.show-holograminconfig.yml. - Vault item lore balance ā after depositing or withdrawing from the vault, the vault block item in the owner's inventory is updated to show current stored balance(s) below a separator line.
Fixed
- Shop purchase GUI improvements:
- Purchase GUI now stays open when player inventory is not full, allowing spam-click purchases until inventory fills
- Fixed bug where items were incorrectly removed from player inventory when purchase failed due to full inventory space
- All GUIs now allow normal player inventory interactions while keeping the GUI itself protected
Added
-
HTTP REST API ā embedded API server for Discord bots, web panels, and external automation. Disabled by default (
rest-api.enabled: false). See REST API docs for full details.- Bearer token auth, 9 endpoints covering balance read/write, currency list, and server status.
- Zero extra dependencies ā JDK
com.sun.net.httpserveronly.
-
External database sync API ā for plugins that write directly to the database:
- Allows forcing a cache reload on specific player accounts and retrieving the updated balance.
-
eco give|take|set allnow applies to all players (online and offline), not just online. -
eco clear <player> [currency]ā zero out one or all balances for any player, including offline. Permission:relish.economy.eco.clear. -
eco info <player> [currency]ā view balances for any player, including offline. Permission:relish.economy.eco.info. -
Offline player tab completion ā
eco,balance, andre logsnow suggest offline player names (capped at 500). -
/re give <player> <vault|atm> [amount]ā admin command to give a vault block item or ATM block item to any online player, bypassing crafting. Requiresrelish.economy.admin. Amount capped at 1ā64. If inventory is full, items drop at the player's feet. -
Compact currency formatting ā large currency values are now automatically shortened with
K,M, andBsuffixes (e.g.9.99Minstead of9,993,027) across all balance checks, placeholders, holograms, and GUI displays. -
eco give|take|set|clear onlineā wildcard target selector to apply adjustments or clear balances for all currently online players at once. Shows a chat notification to targeted players. -
Escape prefixes (
p:/player:) ā target exact players whose names conflict with wildcard selectors or currency names (e.g. players namedall,online, ordollars) in/eco,/balance, and/paycommands. -
Compact tab completion ā suggested amount arguments in commands now show shorthand suffixes (e.g.
1k,10k,100k,1m,1betc.) for faster input.
Configuration
- New
config.ymlkeys:vault.*,rest-api.* - New
config.ymlkey:vault.show-hologram(boolean, defaulttrue) ā toggles the hover hologram on vault blocks. - New
gui.ymlsections:vault-gui,vault-password-gui - New permissions:
relish.economy.eco.clear,relish.economy.eco.info,relish.economy.vault.use
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:5RyYvL8C:mcAwgU2c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5RyYvL8C:mcAwgU2c"
}

