All versions
1.3.3
Release
EnchantShop 1.3.3last year 37
Compatibility
Minecraft: Java Edition
1.21–1.21.8
Platform
Paper
Changes
Version 1.3.3 - The Admin Control Update
This is a major feature update that gives server owners deep control over their server's economy, progression, and balance. EnchantShop is now a powerful administrative tool!
✨ New Core Features
- Enchantment Blacklist: You can now prevent specific enchantments from appearing in the shop! A new
enchantmentBlacklistlist in theconfig.jsonallows you to make powerful enchants like Mending a rare, non-purchasable treasure. - Per-Enchantment Permissions: A new
perEnchantPermissionstoggle in the config enables a powerful permissions system. Whentrue, players will need the permission nodeenchantshop.buy.<enchant_name>(e.g.,enchantshop.buy.mending) to purchase an enchant. This is perfect for donor perks or quest rewards! - Max Level Overrides: Break the vanilla limits! A new
maxLevelOverridessection in the config lets you sell enchantments at any level you desire, such as Sharpness X or Efficiency VII.
🔧 Improvements & Fixes
- Modernized Plugin Structure: The plugin now uses a single
paper-plugin.ymlfor all metadata, resolving a critical loading error and improving compatibility with modern Paper servers. - Improved Permissions: The permission system has been expanded. All
enchantshop.buy.*permissions are now nested under theenchantshop.adminnode for easier management in permissions plugins. - The
config.jsonwill now automatically update with examples for all the new features.
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:79L9qCW4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qLJ9goZn:79L9qCW4"
}

