Tags
Creators
Details
Licensed GPL-3.0-or-later
Published 3 months ago
Updated 3 days ago
All versions
1.1
Beta
Bombsight, Rockets & Claymore - 1.13 days ago 1,900
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Add bombsight, C-8 rocket pod, Claymore and C4 presets; overhaul missile flight and chunk handling
- Bombsight: ballistic impact prediction for nearby bomb racks, target runs with automatic release on Sable ships, optical view (RMB with empty hand) with etched reticle, drum counters and release lamp; floor/wall/ceiling mounting
- C-8 rocket pod: assembled one section at a time, ripple/salvo settings panel, hopper loading, launch sounds and effects; redstone-triggered firing with unloaded-area handling
- M18A1 Claymore: directional 60-degree fan of steel balls, 3 s arming delay, detonator/tripwire/redstone triggering; walls block fragments, ship-aware facing and carrier velocity, chain detonation and sub-level support
- C4: pre-throw presets for immediate activation, one-click start, timer or detonator with auto-pairing; configurable keypad lockout after incorrect codes
- Detonator: reaches charges on Sable ships by world position; reports fired, out-of-range, not-ready and lost charges
- Cruise missile and AIM-9: new models, folding fins, smoother client motion, improved autopilot, continuous animated plume and contrails
- AIM-9: live status and hold-fire reasons in its panel, launches from Sable ships with corrected sky checks on flipped ships
- Munition flight: keeps terrain ahead loaded and waits for missing chunks instead of vanishing; removed forced-tick tickets that NeoForge failed to purge, causing permanent chunk ticking and server TPS drops
- Tripwires: multiple wires per post; reworked anti-tank mine
- Mine explosions: CBC white shrapnel clouds and vanilla flame effects
- UI: unified GUI kit, notices HUD and consistent tooltip palette
- Added recipes for all items; test fixtures no longer depend on grid layout
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:DtRY2QQN:jpF6JTEp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DtRY2QQN:jpF6JTEp"
}

