Tags
Creators
Details
Licensed ARR
Published 11 months ago
Updated yesterday
All versions
0.7.5-beta
Beta
Project: Explosive 0.7.5-betayesterday 415
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Added
- New wasteland with teal ground, black trees, mushrooms, shelf fungi and glowing lichen
- Nuclear shelters deep underground, with living quarters, stores and a command room
- Rare missile silos with a working ICBM and sliding doors
- Cluster ICBM that splits into 28 rockets over the target
- Cluster warhead with 40 bomblets, some of them duds
- Lead, hazmat suit, RadAway and iodine tablets
- Air raid siren that reacts to incoming missiles and bombs
- Trench lines, bunkers, gun nests and field guns in the world
- Landmines, sandbags, barbed wire and camouflage netting
- Proximity, delay and penetrator fuses
- Guidance kit that glides bombs onto a target
- Handwritten target papers for ICBMs
- API for other mods
- Create: Radars support
Improved
- Nukes bring down stone buildings and shatter windows
- Blast waves fade with distance, and solid cover protects you
- Explosions are weaker underwater, with new effects
- Missiles now hit walls and terrain
- Bombs and missiles crash through leaves
- Explosion smoke no longer appears inside blocks
- Up to 60% less server load during strikes, 99.6% fewer particle packets
- Creative tab sections
Fixed
- Bombs dropping twice when broken by hand
- Debris, leaves and snow left floating after blasts
- Bombs on the bed of deep water going off as on land
- Mushroom cloud rising again after reloading a world
- Nuclear flash staying on screen
- Designator coordinates jumping beyond 2 km
- Server stalls with Sable installed
- Airdrops are now creative only
Other
- Removed the old ExplosiveAPI, use ProjectExplosiveAPI
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:3rXU9gz8:bk31iEeA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3rXU9gz8:bk31iEeA"
}

