Duck Shot

If you want guns, ammo, attachments, projectiles, throwables, explosives, grapples, melee tools, and other combat items under one plugin, this is the core plugin for that setup.

The goal is simple: keep the combat system, the shared files, and the player-side loop in one place so the plugin is still manageable after the server grows past a starter setup.

Duck Shot is not only a few demo weapons. The plugin already includes the shared systems you need to run a bigger combat setup later: weapon files, shared ammo, attachments, classifications, projectiles, particles, visual states, GUI categories, and optional integrations.

The bundled lineup is there to help you test the core loop first. After that, you can extend the same system instead of replacing it.

The clean rollout is simple. Install the plugin, boot once so the files generate, make sure the main commands are available, and then test one known-good weapon before you start changing files.

• Drop Duck Shot into plugins/.
• Start the server once so the plugin can generate its files.
• Run /duckshot or /ds and confirm the command surface is working.
• Give yourself one test weapon and run the full loop: hold, reload, fire, and check the feedback.
• Once one weapon works cleanly, move on to your real files.

plugins/
  DuckShot/
    config.yml
    weapons/
    ammos.yml
    attachments.yml
    classifications.yml
    gui.yml
    integrations.yml
    projectiles.yml
    particles.yml
    particles_presets.yml
    visual_states.yml

fire:
  mode: SEMI
  shots_per_second: 4.0
  projectiles_per_shot: 1
 
recoil:
  pitch_per_shot: 0.8
 
reload:
  seconds: 1.9

The main aliases are /duckshot, /ds, /shot, /gun, and /guns. The most common command lanes are listing weapons, giving or getting test items, checking ammo, opening menus, reloading the plugin, and reviewing particles.

Common commands
- /duckshot list
- /duckshot get <weapon>
- /duckshot give <player> <weapon>
- /duckshot ammo
- /duckshot menu
- /duckshot reload
- /duckshot particles

Duck Shot is built around editable files and shared systems. You can tune individual weapons, but you can also control the shared behavior behind the whole arsenal so you are not repeating the same work in every file.

Common edit split
- ammos.yml for alternate rounds
- attachments.yml for conversions and upgrades
- classifications.yml for shared family rules
- projectiles.yml for reusable projectile profiles
- visual_states.yml for presentation and state changes

That is the difference between a plugin that stays manageable and one that turns into a pile of one-off weapon files.

Paper 1.21.4+ and Java 21 are the current baseline. ProtocolLib is the preferred input path, but it is still a soft dependency. WorldGuard and MCWAR-Airdrops are also optional.

Performance-related settings live in shared files. That lets you adjust projectile behavior, particles, sounds, and visual states without reopening every weapon file one by one.

The current soft dependency list is straightforward: ProtocolLib, WorldGuard, and MCWAR-Airdrops. These are optional, not hard blockers.

Duck Shot is also built to sit inside a wider Block Arsenal setup, so vehicle, NPC, and event systems can work with the same combat layer instead of replacing it.

Current integration notes
- ProtocolLib support
- WorldGuard bridge support
- MCWAR-Airdrops bridge support
- Vehicle MC integration paths
- Built for the wider Block Arsenal ecosystem

Duck Shot is not supposed to ship every category pack you might want long term. The starter content is there to prove the system and give server owners something real to test first.

If you want more depth without building every file by hand, Block Arsenal is where the extra Duck Shot packs, related assets, docs, release history, and connected ecosystem content live.

Wider Block Arsenal stack
- Duck Shot for weapons, ammo, attachments, projectiles, and combat items
- Duck Blocks for triggers, displays, map logic, movement systems, and reusable effects
- Vehicle MC for vehicles, rig backends, service systems, transport gameplay, and armed-vehicle workflows
- DuckShell NPCs for AI, patrols, spawners, dialogue, companions, and Duck Shot-ready NPC combat

For normal use, most servers only need the base use permission. Admin and setup routes stay behind the give and admin permissions.

Main permissions
- duckshot.use
- duckshot.give
- duckshot.admin

If you are giving staff access for setup or testing, keep the permission split simple and only hand out the higher routes where they are needed.

The goal here is simple. Show what the plugin looks like in motion, show how the admin side looks, and show the overall visual tone of the lineup before someone downloads it.

Do not use reviews for bug reports. Use the support links instead.

When you report a problem, include the server version, Duck Shot version, the file you changed, the exact item or command you tested, any console errors, and whether you tried it on a clean server.