Tags
Creators
Details
All versions
1.7.0
Release
ExplodeAny 1.7.03 years ago 53
Uploaded by
Compatibility
Minecraft: Java Edition
1.20–1.20.4
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
1.7.x
Platforms
Bukkit
Paper
Purpur
Spigot
Changes
Changelog
- Added support for custom entities that are not handled by other configurations.
- A new section has been added (
CustomEntity), which supports any custom entity that causes an explosion that is not contained in VanillaEntity. This is the case, for example, for MrCrayfish's Gun Mod, which adds some custom entities. Since ExplodeAny can't know anything about this entities, it's mandatory to specify a new entity property,ExplosionRadius, in all these entities.
- A new section has been added (
- Added new entity properties:
ExplosionRadius: Allows to set the explosion radiusExplosionFactor: Allows to set a multiplier for the explosion radiusReplaceOriginalExplosion: Allows to replace the original explosion, thus using the custom radius for a new custom explosion- Removed material property
ExplosionRadiusFactorin favor of entity'sExplosionRadiusandExplosionFactor.
- Added new commands:
/explodeany configuration show, which allows to show both entity and material configurations for all sections. Required permission:explodeany.configuration.show./explodeany checktool toggle [player], which allows to toggle other players' checktool. Required permission:explodeany.checktool.toggle.others. (Note that this permission is NOT contained inexplodeany.checktool.toggle, so it is not applied by default for players that can toggle their own checktool)
- Improved autocompletion: all commands have autocompletion now, even for parameters. Only commands that a given user has permission to use will show up as suggestions.
- Improved localization: added new variables for messages and improved default messages.
- Improved sample configuration & documentation.
- Minor performance improvements
Server support
- Bukkit-based server 1.7 - 1.20 (Bukkit, Spigot, Paper...)
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:aTqv5cdx"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:b3oVwYdE:aTqv5cdx"
}

