Sueta

Strikerload

1.0.1-1.21.11

Ever wanted to experience wemmbu's orbital strike cannon? Too lazy? We got your back. Strikerload does exactly that

·Plugin

StrikerLoad

Call down an orbital strike anywhere you can see.

Right-click a payload item to paint a target, and moments later something
arrives from the build limit. Rings of live TNT. A column that drills to
bedrock. A volley of arrows that ends whatever is standing there.

Built for Paper. Folia supported. Fully open source.


Payloads

PayloadWhat it does
NukeConcentric rings of TNT dropped from the sky, detonating on impact
StabA vertical column of TNT from bedrock to build limit, fired top-down
RailgunA delayed volley of high-damage piercing arrows
WolfAirdrops a pack of angry wolves onto the nearest player
DarknessBlinds everyone in range — except whoever pulled the trigger
StasisMarks a point and yanks you back to it after a short delay

Every payload's size is configurable, per item. Hand someone a 3-ring nuke or a
20-ring one; they're the same item with a different yield.


Setup

  1. Drop the jar for your version into plugins/
  2. Add this to spigot.yml — this step is not optional:
max-tnt-per-tick: 1000000

Without it the server throttles TNT spawning and most of your payload will
quietly never go off. Purpur and Pufferfish have their own TNT limits worth
checking too.

  1. Restart, then /strikerload give nuke

Commands

/strikerload give <payload> [player] [size]
/strikerload strike <payload> <x> <y> <z> [world] [size]
/strikerload reload

Aliases: /sl, /strikeload


Permissions

Everything defaults to deny. Nothing is handed out until you say so.

NodeGrants
strikerload.adminThe /strikerload command
strikerload.use.*Every payload
strikerload.use.<payload>One specific payload
strikerload.bypass.cooldownSkip the recharge timer

Per-payload nodes let you give out the fun ones without handing anyone a nuke.


Before you open this up to players

This plugin destroys terrain. That is the entire point, and it will do exactly
what you configure it to do.

  • Set worlds: in config.yml to an explicit list. Empty means everywhere.
  • The safety: section caps how many entities a single strike can spawn. The
    defaults are deliberately conservative. Raise them on purpose, not by
    accident — a mistyped ring count without those caps can take a server down.
  • TNT is attributed to the player who fired it, so WorldGuard, CoreProtect and
    similar can block and log it normally.
  • Consider testing on something that isn't your live world first.

Folia

Supported on every version listed, from the same jars — there is no separate
Folia build.

This isn't a compatibility flag. Charges are scheduled onto the region that
owns each drop position, every charge tracks its own impact, entity work runs
on entity schedulers, and shared state is concurrent throughout. If you don't
run Folia, none of that matters and nothing changes for you.


Versions

MinecraftJar
26.2StrikerLoad-x.x.x-mc26.2.jar
26.1.xStrikerLoad-x.x.x-mc26.1.jar
1.21.11StrikerLoad-x.x.x-mc1.21.11.jar

Separate jars because 26.1+ requires Java 25 while 1.21.11 runs on Java 21 —
one file genuinely cannot cover both.

Paper and Paper forks (Purpur, Folia). Not Spigot or CraftBukkit.


Open source, and verifiable

Licensed AGPL-3.0-or-later. The full source is public. Anyone may use,
modify and redistribute it, including commercially — but any modified version
that gets distributed, or that players interact with over a network, has to
stay open with source available.

Every release is built by GitHub Actions from a tagged commit. The build log is
public and checksums are published with each release, so you can confirm the
jar you downloaded is what the source produces:

sha256sum -c SHA256SUMS.txt

The build also runs an automated audit that fails and blocks the release if
the source contains any means of granting operator status or permissions,
executing commands on someone's behalf, making network requests, spawning
processes, or loading code dynamically. Those aren't promises in a description
box — they're enforced on every single commit, and you can read the check
yourself.

No telemetry. No update pings. No analytics. This plugin does not know the
internet exists.


Support

Bugs and feature requests: open an issue on GitHub.

Security reports: use GitHub's private vulnerability reporting rather than a
public issue.


Independent clean-room implementation. Community software, not affiliated with
PaperMC or Mojang.

Similar projects

Plugin →