Links
Tags
Creators
Details
Licensed LGPL-3.0-only
Published 4 months ago
Updated 3 weeks ago
All versions
1.2.0
Beta
LET!EM!BURN! 1.2.03 weeks ago 31
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
LET!EM!BURN! 1.2.0
Updated the supported baseline to Minecraft 1.21.1, NeoForge 21.1.248, Create 6.0.10, and Sable 2.0.3.
Update
- Added impact-triggered Sable payload support for vanilla TNT, failed Draconic Evolution reactor cores, Ballistix explosives, and More Fun TNTs.
- Supported payloads now preserve their native behavior after impact, including fuse timing, explosive variants, persistent blast effects, and radiation.
- Mekanism Cardboard Boxes can now recursively wrap supported explosives without replacing the innermost payload's native effect.
- Ballistix explosions now transfer their native directional force to nearby Sable structures, including offset impacts that can produce rotation.
- PneumaticCraft machines on Sable structures can now leak or rupture after sufficiently severe impacts. Real leak pressure and flow apply bounded thrust in the opposite direction.
- Added server configuration for payload envelope limits, Draconic reactor impact speed, PneumaticCraft damage and thrust, and Ballistix blast impulse.
Optimization
- Optimized Draconic Evolution reactor explosion annulus scanning while preserving the original affected positions, processing order, random-number consumption, and explosion results.
Fix
- Failed Draconic reactor cores can now travel directly on Sable structures and no longer consume surrounding carrier blocks while inside a sublevel.
- Impact effects are deferred until the end of the physics step and deduplicated, preventing repeated explosions from a single collision.
- Cancelled or failed native effects now restore an unconsumed payload instead of silently deleting it.
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:daRAzYaH:IQ0GxPjC"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:daRAzYaH:IQ0GxPjC"
}



