Tags
Creators
Details
All versions
0.8.0-beta+26.1
Beta
Enchantment Overhaul 0.8.0-beta+26.13 months ago 19
Uploaded by
Compatibility
Minecraft: Java Edition
26.1.x
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Changes
- Walking Fortress is granted again when wearing a full Warding V set. The equip hook never ran, so the advancement was unreachable in normal play.
- Easy Magic no longer crashes the game on startup. Both mods synced chiseled bookshelf contents by adding the same methods to the same block entity; the sync now hooks the base class instead and the two coexist.
- Honing boosts bow and crossbow projectile damage, replacing the removed Power enchantment, adding +1 base arrow damage at level 1 up to +3 at level 5.
- New game rule honing_on_axes, default on, lets servers stop Honing from applying to axes.
- New game rule enchanting_xp_cost, default on, lets modpacks without an XP economy remove XP level costs from the enchanting table. The catalogue then skips the XP check, does not consume levels, and hides the XP line.
- Catalogue cost labels and game rule names are now translatable instead of hardcoded English, in both shipped languages.
- Rose gold armour from Additional Additions gains innate explosion resistance, matching how vanilla sets work.
- Enchantment slots and smithing template eligibility are data-driven. Datapacks can set an item's slot budget with the slots/tier_3 to tier_6 item tags, and make items upgradeable with the upgradeable/honable, wardable, temperable and grindable tags. Shipped tags reproduce previous behaviour exactly, verified across all 1510 registered items.
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:YcuF6XFw"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:iPA46eKp:YcuF6XFw"
}

