Tags
Creators
Details
All versions
1.13.0-folia.1
Release
ExplodeAny 1.13.0-folia.1last year 194
Compatibility
Minecraft: Java Edition
1.21–1.21.8
1.20.x
1.19.x
1.18.x
1.17.x
1.16.x
1.15.x
1.14.x
1.13.x
1.12.x
1.11.x
1.10.x
1.9.x
1.8.x
Platform
Folia
Changes
Changelog
- Added specific TNT properties [see the wiki]: some new properties have been added specifically for TNT. They can be used in the same entity "Properties" section that all explosive entities have. Some of these entities are:
- MinimumTravelDistanceToDamageBlocksUnderwater: it allows to set a minimum distance that a primed TNT must travel after it is primed in order to enable underwater damage. This is a workaround for vanilla TNT cannons blowing up after enabling ExplosionDamageUnderwaterBlocks. You can set a minimum distance (like 10) so that propellant TNT does not damage the cannon, but still propel the projectile TNT.
- SnapToBlockGridOnPriming: stops primed TNT from moving from its position, allowing to keep primed TNT aligned with the block grid.
- DisableExplosionChaining: allows to disable explosion chaining, i.e., TNT won't be primed by other exploding TNTs.
- Added OnHit and OnBreak particles [see the wiki]: until now, the entity material Particles section allowed to configure particles that spawn when a block is broken. This stays as the default behavior, but you can now configure particles when a block is hit by the exploding entity too.
- Fix boss bar duration not being properly computed: while a duration could be used for configuring the checktool's boss bar, the real duration did not match the specified one. It is fixed now.
- Compatibility rework: to ensure the plugin will continue running in different server implementations (such as Paper, after their hard-fork on Spigot), we have reworked our compatibility layers. Now, paper-based servers will load an specific compatibility layer, allowing to leverage Paper-only features.
- Minor improvements
Server support
- Folia-based server 1.8 - 1.21.8
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:b3oVwYdE:e9rJci74"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3oVwYdE:e9rJci74"
}

