All versions
2.0.0
Release
Kaiju Strike Designator 2.0.021 hours ago 22
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
A full rewrite. Almost nothing from 1.0 is left.
New
- The designator is now a handheld weapon with a scope, zoom, a rangefinder and a thermal view. The placeable device and its timer are gone.
- Three strike modes (Atomic Breath, Breath Sweep and Pinpoint) and three yields, picked from a radial menu on V.
- The Cosmic Relay, a voiced cinematic that follows your offering across the universe to Kakuō, the Isotope Sovereign, and rides the beam home. Skip it with Jump or turn it off in the client config.
- New beam, shockwave, impact frames, storm, ground sigil, volumetric mushroom cloud and falling ash.
- Much more detailed craters: a glowing shaft, trinitite, magma, irradiated rock, an ejecta rim, and a blast zone that knocks buildings down by material, flattens or chars trees and starts fires.
- New blocks: Trinitite, Irradiated Rock and Charred Log.
- Nuclear Cores are now ammo, with a reload animation.
- Distant strikes are heard late, at the speed of sound, and other sounds fade out right before impact.
- Operator commands: /kaijustrike strike, /kaijustrike cancel and /kaijustrike list.
- Separate client and server configs, both editable from the Mods menu.
- Works with Iris shader packs.
Fixed
- Dedicated servers crashed on startup.
- Strikes could crash with "Controller ... is not registered".
- Ripped-up blocks could crash the client.
- Firing used up the designator.
- Large craters dropped servers to around 10 TPS. Carving now happens per chunk section with a time budget.
- The cloud shader ran every frame even when no strike was happening, and vanilla clouds stayed hidden for good.
- Positional sounds played at full volume everywhere.
- Strikes killed everything with no damage source or death message, creative players included.
Removed
- GeckoLib and Flywheel are no longer required.
Back up your world before updating from 1.0. Your designators carry over, but placed 1.0 devices don't.
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:qEqYBafH:aHYD8u7n"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qEqYBafH:aHYD8u7n"
}

