Tags
Creators
Details
1.0.9-fix
Compatibility
Required content
Changes
1.Changed configuration file type back to normal instead of server-side, added instant configuration synchronization and effect functionality.
2.Removed the feature where entities attacked by Absolute Destruction Damage could not use setHealth() to regenerate.
3.Optimized Powerful Mining Mode logic - now you can left-click to cancel block selection after selection.
4.Optimized Absolute Destruction Damage logic to make it more like vanilla damage sources.
Optional dependencies
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:naW7WZy0:bY4ptfkc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:naW7WZy0:bY4ptfkc"
}

