All versions
1.2.3
Release
Curses Revamped Additional 1.2.33 weeks ago 20
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client and server
Required content
Any compatible version
Changes
Curses Revamped 1.2.3 Changelog
Changed
- Reworked fake curse enchantments so their disguises now depend on the item they are applied to.
- Weapon curses now use believable weapon enchantments such as Sharpness, Knockback, Looting, or Power.
- Armor curses now use Protection, Thorns, or the matching protection enchantment.
- Pulling uses Knockback on melee weapons and Punch on bows and crossbows.
- Backlash uses Thorns on armor, Sharpness on melee weapons, and Power on bows and crossbows.
- Dead Wings only uses Unbreaking or Mending as a disguise on Elytra.
- Magnetism only uses Loyalty as a disguise on tridents.
- Concrete Legs only uses Feather Falling on boots and leggings.
- Curses without a believable disguise remain scrambled instead of showing an invalid enchantment.
Fixed
- Fake curse displays no longer change when an item loses durability.
- Normal unknown curse tooltips, anvil fake displays, and debug reports now use the same item-aware disguise rules.
- Updated fake-enchantment documentation to match the actual item categories.
Compatibility
- Minecraft version remains 1.21.1.
- Additional requires Curses Revamped Base 1.2.3 or newer.
- Existing enchantment IDs and curse behavior remain unchanged.
- Fabric and NeoForge Additional builds were updated together.
Notes
- Base and Additional remain separate files. Additional cannot be installed by itself.
- Suggestions for new curses, fake enchantments, and enchanting ideas are welcome.
Thanks
Special thanks to Melmi for suggesting Curse of Psychosis and for helping shape the addon with curse ideas and feedback.
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:mmGMQuTv:RdOUQ53i"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mmGMQuTv:RdOUQ53i"
}

