Tags
Creators
Details
Licensed ARR
Published 6 months ago
Updated 3 months ago
All versions
1.1.1
Release
DisenchantX 1.1.16 months ago 12
Compatibility
Minecraft: Java Edition
26.1.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
v1.1.1 — Bug fixes & item rescue
Bug fixes
- Books are no longer lost when your inventory is full. Extracted enchanted books now drop in front of you (like a vanilla Q-key throw) with the standard pickup delay and pickup sound, instead of vanishing.
- All extracted enchantments are now properly removed from the source item. Previously, when using a single book to extract multiple enchantments combined, only the first enchantment was removed from the item — the others stayed silently attached, blocking
/enchantafterwards because of conflicts. - Anvil mutations are now deferred to the next tick. This avoids vanilla rolling back our slot updates after the cancelled click event, which could cause the disenchanted item to revert to its enchanted state.
- Fixed a malformed
minecraft:enchantmentscomponent override. When all enchantments were removed from an item, Spigot/Paper would write an empty{}component (missing thelevelskey) instead of clearing the override. This silently broke vanilla/enchanton the item afterwards.
New features
/dx fix <player> [enchant]— admin command to repair items broken by previous extractions or remove a specific enchantment.- Without
[enchant]: removes all enchantments from the player's mainhand item and repairs any malformed component override. - With
[enchant]: surgically removes a single enchantment by name (e.g./dx fix Steve sharpness). - Tab completion suggests online player names and the enchantments currently on the target's item.
- Without
- New permission
disenchantx.fix(default: op).
Notes
- Items broken by previous versions can be repaired by holding them and running
/dx fix <yourname>.
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:kgbEEIL6:tXZV7XU3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:kgbEEIL6:tXZV7XU3"
}

