1.1.0-additional
Compatibility
Changes
Curses Revamped 1.1.0
This update focuses on the Additional version of Curses Revamped, adding a much bigger curse system, hidden curse discovery, fake enchantments, and the new risky enchanting-table path: Ominous Offering.
Highlights
-
Added Ominous Offering to the enchanting table.
- Rare special enchant option.
- Gives stronger enchantment results.
- Always comes with curse risk.
- Bad Omen increases its appearance chance.
- Hero of the Village reduces curse pressure.
-
Added hidden/fake curse discovery.
- Unknown curses can appear scrambled.
- Some curses can pretend to be vanilla enchantments.
- Curses can be researched at an enchanting table using XP and lapis.
-
Added cursed stat boons.
- Some cursed items may gain small positive bonuses.
- Example: weapons can show improved attack damage.
- These bonuses make cursed items more tempting instead of always being instant trash.
Changes
- Improved enchanting table UI for Ominous Offering.
- Improved curse research UI.
- Added fake enchantment behavior for some hidden curses.
- Added per-player curse discovery progress.
- Added anvil support for fake curse trolling.
- Added cursed books to curse systems.
- Added Curse of Curses behavior so it can trigger many curse effects.
- Added configs for several hidden/balance systems.
- Improved tooltip behavior for cursed boons.
Known Issues
-
Creative environment testing is currently difficult to use clearly.
- This will be improved with new commands and clearer text in a future update.
-
Curse of Vulnerability is currently broken.
- A fix will be attempted in the next batch.
Notes
The base/server-side version is still intended to stay simpler. Most of the new curse discovery, fake enchantment, and Ominous Offering systems are part of the Additional jars.
The next update is planned to improve cursed boons and bring some boon improvements to the base version as well.
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:tYuKjxt9"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:YYTT1zLX:tYuKjxt9"
}

