1.0.1
Compatibility
Changes
Grave Drop Removed protection: grave can now be broken by any player (no owner-only restriction). Name tag fix: player nickname above the grave should now render correctly. TileEntity sync: fixed client/server syncing for grave data (ownerName, owner UUID), improving stability of rendering/interaction. Grave contents on break: breaking the grave returns/drops stored items as before (vanilla slots restored correctly, extra items dropped/added). TeardownFisics Whole-tree fall: breaking natural trees makes the entire tree fall (logs become falling entities). Leaves behavior: leaves do not fall as entities — they break immediately and drop items normally. Structure-safe: isolated logs / logs in builds do not trigger whole-tree falling (tree detection via nearby leaves). Reach distance: increased interaction/build reach to 5 blocks on both client and server (safe for dedicated servers). Notes Game version: 1.12.2 Loader: Forge Config: no config changes required
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:2XQDFv5V:YiHHtzWA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:2XQDFv5V:YiHHtzWA"
}

