1.2.1
Compatibility
Changes
Added
- Two new curse modes:
shared_temporals- relics no longer cost you anything. Instead, every temporal carried by two or more companions in the party adds one curse.shared_modifiers_and_temporals- both rules at once. Shared relic modifiers and shared temporals each add their own curses, and the two are added together.
Changed
curse_mode in codex.json is now written as a readable name instead of a number:
| Old | New |
|---|---|
0 |
none |
1 |
shared_modifiers |
2 |
challenge_stacks |
Existing configs are migrated automatically on the first server start and the file is rewritten with the new names. Nothing to do by hand. An unrecognised curse_mode now falls back to shared_modifiers and logs the list of valid values, instead of being silently reset.
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:Lhgk41aC:a1LrDq13"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Lhgk41aC:a1LrDq13"
}

