Tags
Creators
Details
0.3.2-alpha+1.21.1
Compatibility
Required content
Changes
Hot fix: Fixed the bonfire so that after death, the rendering of the fire persists, problem was that nbt data was re-saved on server, but on the client side it wasn't leading to desynchronization, and it not showing lit. Now should be synced.
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:PDkYCAeF:Ryl8g5An"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:PDkYCAeF:Ryl8g5An"
}

