All versions
1.2.3
Release
Curses Revamped 1.2.33 weeks ago 28
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1–1.21.11
Platform
Fabric
Supported environments
Server-side
Client and server
Changes
Curses Revamped Base 1.2.3 Changelog
Added
- Added shared Base support for curse discovery and revealed curse states.
- Added shared cursed boon data support so Base and Additional can store, transfer, display, and apply the same boon data.
- Added
/cursesrevamped debug itemfor inspecting the held item's enchantments, discovery state, boon data, and applicable effects. - Added Base discovery commands for researching, revealing, unlearning, and checking curse progress.
- Added the hidden
creativeDiscoveryBypasssetting for creative testing.
Changed
- Base now acts as the shared foundation for Additional instead of only containing the vanilla curse reworks.
- Base owns the shared Vanishing, Binding, discovery, boon, tooltip, and debug APIs used by Additional.
- Creative mode follows normal discovery rules by default, making research and unlearning tests reliable. The behavior can be changed in the hidden Base config.
- Base configuration comments now explain the Base, shared, and Additional-owned settings.
- Vanilla Curse of Vanishing and Curse of Binding tooltip support now uses the shared discovery state.
Compatibility
- Minecraft version remains 1.21.1.
- Additional requires Curses Revamped Base 1.2.3 or newer.
- Base can still run by itself and remains primarily server-side.
- Existing discovery data, cursed boon data, and enchantment IDs remain compatible.
- Fabric Base and NeoForge Base were updated together.
Notes
- Install the Base file matching your loader.
- Install the matching Additional file as well if you want custom curses, research UI, fake enchantments, and Ominous Offering.
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:RclCiZKl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YYTT1zLX:RclCiZKl"
}

