Links
Tags
Creators
Details
0.9.4-beta
Compatibility
Changes
Added checks for using death chest type plugins or data packs. Assuming the death chest is placed at the location of the player at deat, the re-assembly logic now looks if there is a container at the location that the root block would be placed and if that is the case, the root block is not restored and the container is left untouched. This means that after retrieving the contents of the death chest there will be a missing block in the vessel that will need to be replaced.
Added checks to restrict what blocks the helm itself can be placed on.
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:XvUnbHww:QC6v5TG8"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:XvUnbHww:QC6v5TG8"
}

