Tags
Creators
Details
4.6.17+paper
Compatibility
Changes
fix: resolve storage, revival, bounds, and social command edge cases (#558)
-
fix(common): prevent data loss with atomic save in DlcStorage
-
fix(common): correct error message when self-targeting in DlcTrustService
-
fix(paper): skip corrupt UUID entries in RPSocial getRelationsToAll
-
fix(paper): provide fallback fence materials for unbootstrapped tag values in RPConfig
-
fix(paper): add maxHeight bounds check in ReviveHelper ritual pattern matcher
-
fix(paper): clear death holder state on revival and prevent duplicate social error messages
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:Pb03qu6T:bRvYf8lD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Pb03qu6T:bRvYf8lD"
}

