1.1.1
Compatibility
Changes
Added compat for PlayerRevive mod Shrines are now capped to world border(to support smaller servers) When no vessel present there is a 3% chance for a non vessel to eat a fragment(can be configured) shrine travel has now been converted to fragment travel, incarnate is now tied to fragments whether they are in a display case, chest, or player inventory Fragments can no longer be placed into an ender chest(to ensure no soft lock happens) Fixed bug where shrine tether breaks innate domain
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:ZqV4ydO3:eDhOz9kL"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:ZqV4ydO3:eDhOz9kL"
}

