Tags
Creators
Details
All versions
1.0.0-rc.1+26.1
Beta
Enchantment Overhaul 1.0.0-rc.1+26.12 weeks ago 51
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Changes
- Every enchantment has its own reagent and price curve, matched to its theme and power. Endgame enchantments ask for endgame materials: Mending takes Ghast Tears, Swift Sneak Sculk Sensors, Lunge Wind Charges, Looting Rabbit Feet and Infinity Spectral Arrows. Bookshelves still cut costs by up to half, and upgrading in steps costs exactly as much as applying the level directly.
- The grindstone no longer costs an enchantment slot. Items penalized by older versions get their slots back, and the anvil's slot restoration is gone.
- The anvil repairs every tool vanilla could only fix by combining two copies: bows, crossbows and fishing rods with string, tridents with prismarine shards, shears with iron, flint and steel with flint, the two sticks with their food, and brushes with feathers. Each material comes from an item tag datapacks can edit.
- Grinding templates now drop from dungeons and desert pyramids as documented.
- Veil no longer makes its wearer untargetable: phantoms attack again, mobs retaliate when hit and Endermen keep their aggro. It still cuts detection range to a quarter.
- The catalogue shows its inventory label and the real bookshelf discount, keeps your selected level while you add reagents, and books with two enchantments show both.
- Upgrade names, armor resistances, catalogue hints and /upgrade messages are translated, French included.
- The wiki is up to date with the current mechanics.
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:iPA46eKp:Vw4hoq8T"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iPA46eKp:Vw4hoq8T"
}

