Tags
Creators
Details
V1.0.0
Compatibility
Changes
π v1.0.0 - Release
We are proud to announce the initial release of EnchantsPro! This version establishes a rock-solid foundation for custom enchantments, focusing on performance, server-owner control, and "Pro" quality mechanics.
β¨ New Features
- Complete Arsenal: Added 9 unique enchantments including Trench, Timber, VeinMiner, Smelter, Telepathy, Magnet, Haste, Silk Touch II, and Experience.
- Smart Trench Logic: Trench II now features directional detection, allowing for vertical (walls) and horizontal (floors) 3x3 mining.
- Smooth Timber Engine: Implemented a non-blocking wave system for leaf decay to ensure zero server lag during large-scale deforestation.
- True Silk Spawners: Silk Touch II now correctly captures and restores Mob Spawner NBT data, allowing spawners to be moved without losing their entity type.
- Modular Anvil System: Custom books can now be combined in anvils to increase their level, just like vanilla enchantments.
βοΈ Distribution & Control
- Configurable Economy: Added a comprehensive
config.ymlallowing server owners to set custom spawn percentages for Enchanting Tables, Villager Trades, and Loot Chests. - Admin Command Suite: Implemented
/ep givewith built-in level clamping to prevent illegal enchantment levels, and/ep reloadfor hot-swapping configurations.
π οΈ Technical Improvements
- Async Magnet Logic: The Magnet enchantment now runs on an asynchronous task to maintain 20.0 TPS.
- MiniMessage Integration: All plugin messages and item lores now support modern RGB/Gradient formatting.
- PDC Native Storage: All data is stored via the PersistentDataContainer API for maximum compatibility with other plugins.
Thank you for choosing EnchantsPro! If you encounter any bugs, please report them via our support channels.
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:E525doBB:6VWcUNKp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:E525doBB:6VWcUNKp"
}

