Links
Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 5 months ago
All versions
1.0.4
Release
NguyenDevs Orbital Strike Cannon 1.0.46 months ago 2,305
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Paper
Purpur
Changes
🚀 New Features
- EMP Payload: Added the new EMP payload type capable of creating large-scale shockwaves. EMPs can effectively disable Redstone mechanics and apply debuff effects to entities within their blast radius.
- Dynamic Particle Trails System: Introduced a brand-new, highly customizable particle trails system for projectiles. Server owners can now create beautiful and intricate trail trajectories with complete freedom.
- Crafting Recipes: Added example crafting recipes for cannons, allowing players to obtain and use them easily in survival mode.
⚙️ Changes & Improvements
- Cleaned Configurations: Restructured and cleaned up all configuration files. They are now much cleaner, more intuitive, and easier for server owners to read and customize.
- World Restrictions Logic: Changed the world restriction mechanic from a whitelist ("Enabled Worlds") to a blacklist ("Disabled Worlds") approach, offering greater flexibility during setup.
- Improved WorldGuard Integration: Fixed issues and optimized the WorldGuard soft-depend hooks, ensuring stable and accurate plugin behavior within protected regions (claims).
⚠️ Breaking Changes
- Major Core Refactoring: This update involves significant structural changes to the core systems of the plugin. To avoid any incompatibility issues caused by old data structures, please backup your existing
.ymlconfiguration files and allow the plugin to regenerate them after updating!
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:Pfm5HYf2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:sx0zgaef:Pfm5HYf2"
}

