2.0.0
Compatibility
Changes
Version 2.0.0 - The Gameplay Update
This is a massive update that adds entirely new gameplay mechanics and powerful administrative tools, transforming EnchantShop into a complete enchanting economy system for your server!
✨ New Gameplay Features
-
Disenchanting GUI (
/disenchant):- Players can now remove enchantments from their items for a partial refund!
- Simply hold the item and run
/disenchantto open a new interactive GUI. - The refund percentage is fully configurable in the
config.json. - This feature is available to all players by default (
enchantshop.disenchant).
-
Enchanted Book Support:
- The enchant shop is now a book shop! If a player runs
/eshopwhile holding a regular book, they will purchase an Enchanted Book instead of applying the enchant directly. - This allows players to store, trade, and sell enchantments, creating a new player-driven economy.
- The enchant shop is now a book shop! If a player runs
🛠️ New Admin Features
- Admin Enchanter Command (
/enchanter):- A powerful new command for admins to instantly enchant the item a player is holding.
- Usage:
/enchanter <player> <enchantment> <level> - Includes full tab-completion for player names and enchantment IDs.
- Requires the permission
enchantshop.enchanter.
🔧 Improvements & Fixes
- Configuration Reset Recommended: Due to the large number of new messages and settings, it is highly recommended that you delete your old
config.jsonto allow a fresh one to generate. - Added over 10 new configurable messages for all the new features.
- The
DisenchantCommandwill now correctly check if the item held is actually disenchantable before opening the GUI.
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:qLJ9goZn:PwU7VAZ3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qLJ9goZn:PwU7VAZ3"
}

