2.2.0
Compatibility
Changes
✦ DRAGONS WRATH: UPDATE v2.2.0 ✦
— THE STEALTH & SACRIFICE UPDATE —
The Ancient Forge has grown cold. The requirements for wielding true power have shifted, and the Sovereigns have tightened their grip on the world's most powerful relics.
⚒ THE ANCIENT FORGE REWORKED
The Forge no longer guides the weak. If your sacrifice is insufficient, the Forge will remain silent, offering only a cryptic warning.
Recipe Secrecy: Recipes are no longer public knowledge. You must discover the components through trial and error—or find someone who knows the ancient secrets.
Failure Risk: The Crusher remains the most volatile relic. Its forge success rate is hardcoded at 25%. If the Forge rejects your offering, your materials will be lost to the void forever.
⚔ UPDATED RELIC REQUIREMENTS
The cost of power has reached an all-time high. Relics now require rare materials from the deepest corners of the world.
🔒 STEALTH PROTOCOLS
We have implemented Stealth Admin Controls. For the average player, the existence of administrative commands has been scrubbed from the system.
Fake Unknown Commands: Attempting to access restricted commands will now result in a standard "Unknown Command" error to maintain the mystery of the relics.
📜 ADDITIONAL CHANGES
Global Uniqueness: Relic tracking is now more precise. The world will only ever allow one of each relic to exist at a time.
Aether Returns: When a legendary wielder falls, the relic is immediately returned to the Aether, allowing it to be forged once again by someone worthy.
Internal Tagging: Weapons are now bound by persistent internal data—renaming your relic in an anvil will no longer strip it of its legendary status.
The Forge is open. Will you provide the sacrifice?
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:NYzhJjMN:6CeI1nIa"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:NYzhJjMN:6CeI1nIa"
}

