Tags
Creators
Details
5.0.0
Compatibility
Required content
Changes
Version 5.0.0 - The Audio-Visual Overhaul & New Launch Mechanics!
This massive update completely overhauls how missiles are launched, adds stunning new visuals, and introduces realistic soundscapes to the battlefield.
Major Features & Visuals
- Animated Launch Pads: The Launch Pad is now a fully animated 3D structure! Missiles are no longer placed as blocks on top; instead, you load them directly into the launcher by right-clicking.
- Complete Sound Overhaul: Added immersive, high-quality sound effects for missile launches, in-flight flybys, anti-air interceptions, and distant explosions.
- Next-Gen Explosions: Completely rewritten explosion visuals. Enjoy cinematic mushroom clouds, shockwaves, debris scattering, dynamic screen shake (earthquake effect), and blinding flashes.
- Thermal Burn Mechanics: Explosions are no longer just about breaking blocks. The intense heat from the blast will now leave behind scorched blocks and scattered fire at the epicenter.
Anti-Air & Combat Tweaks
- Upgraded Anti-Air Systems: Interceptor missiles now feature beautiful smoke trails and advanced predictive tracking. Successful interceptions now result in realistic mid-air detonations.
- Heavy Missile Mechanics: Heavy Ballistic Missiles now require the launcher to be raised into a 90-degree vertical firing position before launch (Right-click the loaded pad with an empty hand).
Optimization & Bug Fixes
- Flight Synchronization: Rewritten projectile logic to ensure perfectly smooth launches. Missiles no longer "teleport" or jitter during the first seconds of flight.
- General Optimization: Improved server-client syncing and targeting performance for a more stable multiplayer experience.
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:JHvED368:p0RCx81X"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JHvED368:p0RCx81X"
}

