Tags
Creators
Details
2.0.0-1.21.0
Compatibility
Required content
Changes
Update v2.0.0 (Beta)
It's time for a massive update! This update includes basically a full rewrite of the Mod adding the ability to control the colours differently for EVERY type of a explosion
What's new?
- Added configuration for EVERY explosion
- You want your End Crystals to blow up Purple and Pink while your TNT Blows up Red and Black? Well now you can!
- Added Wind Charge to the explosions
- It causes an explosion so now it gets it's own pretty colours
Current Explosion Types
The following Explosion Types can each be changed separately in the Config
- TNT
- TNT Minecart
- Creeper
- Bed
- Wither (When Spawned)
- Wither Skull
- End Crystal
- Fireball
- Respawn Anchor
- End Dragon (When Respawned - also still WIP)
- Wind Charge
- Breeze Wind Charge
- Wind Charged Effect (When a mob dies with the splash potion)
- Enchantment (When a mob dies to the Wind Charge Enchantment)
Why is this such a big thing you may ask? Well Minecraft doesn't provide what causes an explosion at least not in an easily accessible way. So this mod now dips it lil fingies into much of the game so that the type of explosion can be tracked.
Due to this fact, custom networking has been added to handle the Mod usage on a Server as well as Client. In order to use the different configuration settings for explosions the mod MUST be on the server as well otherwise it will use the default colour configuration. (It will work completely fine in Single-player Worlds just like normal, don't worry)
Please report any issues to the GitHub
Explosions with the new configuration (v2.0.0)

Explosions from the Wind Burst Item and Enchant

It's unlikely to be backported to 1.20 versions due to networking changes between 1.20 and 1.21 (1.20.5+) but if there is enough interest I may
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:682G7A3u:LDO7wItu"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:682G7A3u:LDO7wItu"
}





