1.0.0
Compatibility
Changes
Adds a single custom TNT entity that behaves completely differently depending on what block triggered it. Instead of dozens of unrelated explosive block classes, every variant — from a firework-quiet Party TNT to a Nuclear TNT, each with its own explosion algorithm tuned for what it's supposed to do:
Terraform the world into a theme, Spawn mobs, Buff or debuff everyone nearby Mining, Just blow up, And Nuke the world up! More than forty different types of TNT with ten tier each other. The ten highest tiers of nearly every TNT type can make bigger BOOM.
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:fqsroQ8M:PIfyKf2X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fqsroQ8M:PIfyKf2X"
}

