2.0.0
Compatibility
Changes
OrbitalStrike v2.0.0 ā Break Change
What's New
This major update brings full support for Minecraft 1.21 through 26.1.2, along with long-awaited fixes and performance improvements.
Features & Fixes
- Cooldown System The cooldown setting on cannons now actually prevents firing until the timer expires. Set it in
cannons.ymlper-cannon. - Safety Limit ā Nuke strikes now cap at a configurable maximum TNT count (
max-tnt-per-strikeinconfig.yml, default -1). No more accidental server melts. - EMP Shockwave reworked ā Smoother visual effects, better performance, and more reliable block destruction.
- Permissions overhaul ā
orbitalstrike.usenow defaults totrueso all players can use cannons by default. Granular craft permissions (orbitalstrike.craft.*) have been added. - Crafting recipes now require permission by default ā Server owners must explicitly grant
orbitalstrike.craft.<recipe>to players. - Fixed cannons.yml configuration ā The item and settings sections now use proper YAML format.
Bug Fixes
- Cooldown field now actually works (it was defined but never checked)
- Fishing rod cannon tools can no longer accidentally cause issues when fishing
- Fixed several cases where the plugin would crash with
ClassCastExceptionon certain item types - Plugin no longer leaks memory over time (fixed listener registration)
- Improved error messages for missing targets, invalid materials, and blocked regions
- Fixed EMP particle effects not rendering on Paper 26+
Performance
- Nuke strikes now have a configurable TNT cap (
max-tnt-per-strikeinconfig.yml, default -1) to prevent server lag. - EMP shockwave effects are significantly more performant
- Overall particle effect handling has been optimized
Full documentation: https://github.com/NguyenDevs/Orbitalstrike
Report issues: https://github.com/NguyenDevs/Orbitalstrike/issues
Optional dependencies
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:sx0zgaef:QVi0e1gM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sx0zgaef:QVi0e1gM"
}


