1.5
Compatibility
Changes
📋 Changelog: v1.5
Performance overhaul and bigger decay range
Decay scan radius increased from 24 to 64 chunks around each player. Only chunks that are currently loaded are affected, so the effective range depends on your render distance Completely rewritten decay engine: the world is now processed in small slices spread across many ticks instead of in one huge scan, which means no more freezes or FPS drops when decay triggers Block type detection is dramatically faster, so a decay cycle now starts and finishes in a fraction of the previous time Decay now triggers reliably every 60 seconds. If a large cleanup is still running when the next minute arrives, the next decay waits in a short queue instead of being skipped Mobs that decay are gone for good: when a mob type is wiped out, it is removed again if it tries to respawn anywhere within the decay radius Boss mobs (Ender Dragon and Wither) are still protected
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:6GozKu00:zD4d4FvZ"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:6GozKu00:zD4d4FvZ"
}

