All versions
1.21.1-2.0.4
Release
1.21.1-2.0.47 months ago 486
Compatibility
Minecraft: Java Edition
1.21.1
Platform
Fabric
Supported environments
Server-side
Singleplayer
Required content
Changes
- Added the entity type tags
#tntutils:deny_explosionsand#tntutils:allow_explosions, which can be used to disallow or allow entity types to create explosions, respectively.- For example, tagging minecraft:ghast with deny_explosions (in a datapack) allows you to block explosions from Ghast fireballs.
- Individual entities (as opposed to entity types) can also be tagged with
tntutils.deny_explosionsandtntutils.allow_explosionsto (dis)allow them to create explosions.- The entity tags are not to be confused with entity type tags. They can be applied to an entity with the
/tagcommand. Notice the dot instead of a colon, since the argument to/tag addcannot contain colons. - For example, to make a Creeper that explodes even when explosions are disabled in the config, you can use the command
/tag @n[type=creeper] add tntutils.allow_explosions. - Note: While it is possible to tag a player with tntutils.deny_explosions, this will not completely prevent them from causing explosions, as, for example, they can still ignite TNT with a redstone signal.
- The entity tags are not to be confused with entity type tags. They can be applied to an entity with the
- Added the config options
entityDamageMultiplierandknockbackMultiplier, which can be used to change the amount of damage and knockback applied to entities, respectively. - The
/explodecommand will now bypass thedisableExplosionsconfig option. - Added suggestion for the default explosion strength (4) to the '/explode' command.
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:rynRpwv0:WKivN9GI"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:rynRpwv0:WKivN9GI"
}

