All versions
1.0.0-additional
Release
Cursed Revamp 1.0.0last week 5
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Client and server
Changes
Release Highlights
- Reworked Curse of Vanishing so it can trigger from durability loss.
- Reworked Curse of Binding with armor-stat combining and Mending support.
- Added additional curse builds for Fabric and NeoForge.
- Added curse discovery with scrambled unknown curse names.
- Added fake hidden curse displays and fake anvil curse behavior.
- Added enchanting-table research with XP, lapis, and bookshelf-based costs.
- Added revealed-but-not-researched curse names for protection-style curses.
- Added cursed books to generated loot.
- Added held cursed-book effects.
- Added cursed enchanting behavior affected by Bad Omen, Hero of the Village, and extra curse rolls.
- Added automatic cursed item equipping for visible curses.
- Added Curse of Curses armor carrier behavior for held tools and weapons.
Full Additional Curse Names
- Curse of Fragility
- Curse of Hunger
- Curse of Echoes
- Curse of Soulbinding
- Curse of Backlash
- Curse of Blindness
- Curse of Pulling
- Curse of Concrete Legs
- Curse of No Jumping
- Curse of Curses
- Curse of Bad Omen
- Curse of Reduced Reach
- Curse of Fire
- Curse of Projectiles
- Curse of Explosions
- Curse of Vulnerability
- Curse of Crossed Wires
- Curse of Dead Wings
- Curse of Mercy
- Curse of Magnetism
Idea Credits
- REDKING_11: Curse of Soulbinding, Curse of Reduced Reach, Curse of Fire, Curse of Projectiles, Curse of Explosions, Curse of Vulnerability
- MrHaamu11: Curse of Backlash, Curse of Blindness, Curse of Pulling, Curse of Concrete Legs, Curse of No Jumping, Curse of Curses, Curse of Crossed Wires, Curse of Dead Wings
- MrHaamu1: Curse of Bad Omen
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:YYTT1zLX:y0Hw1tNI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YYTT1zLX:y0Hw1tNI"
}

