Wiki

Duck Shot Wiki

Public setup, weapon authoring, combat systems, particles, admin help, and troubleshooting for Duck Shot.

Quick access

Plugin downloadsDuck Shot All wikisOfficial docs hub AssetsMarketplace SupportHelp routes

Getting Started

Start here for installation, first boot, and your first working Duck Shot weapon.

Wiki Home Install and First Boot Global Config and Runtime First Weapon Walkthrough

Weapon Authoring

Learn the actual weapon-file structure, support files, and player-side feedback systems.

Weapon File Structure Ammo, Attachments, and Classifications Ammo Families, Variants, and Custom Rounds Attachment Recipes, Conversions, and Upgrade Paths Loadouts, Support Items, and Classification Design Classifications, Groups, Lore, and Held Hooks Create Wizard, Templates, and Knobs Starter Templates for Guns, Throwables, Consumables, Grapples, and Devices Stage Templates for Sounds, Particles, and Conditions GUI Browser, Live Tuning, and Categories Support YML Files and Global Editors Input Binds, Consumables, and Alt Actions Action Bar, Sounds, and Feedback Per-Weapon Sounds, Events, and Breath Focus Visual States and Animated Models Weapon Archetype Recipes

Example Library and Pack Planning

Separate the public starter pack, the deeper example library, and your own server-only content so the docs stay honest and useful.

Starter Packs, Example Files, and Server-Only Content Weapon Archetype Recipes

Combat Systems

Tune firing, impacts, special utility items, and the Particles v2 effect stack.

Fire, Recoil, and Aim Scopes, Thermal, Flashlights, and Held Effects Projectiles and Impacts Projectiles, Spread Patterns, Recoil, and Debugging Throwables, Explosives, and Flashbangs Planted Charges, Mines, and Proximity Devices Explosive Payloads, Clusters, and Strike Recipes Mounted Guns and Deployable Emplacements Grapples and Tools Melee Weapons, Breach Tools, and Hybrid Actions Magic Casters, Wands, Staffs, and Spell Actions Particles v2 and FX Conditional Rules and Context-Aware Weapons Block Breaking, Restoration, and Craters Sky Select, Airstrikes, and Support Callers

Server Operations

Handle permissions, runtime tools, integrations, and real troubleshooting on live servers.

Admin Commands and Permissions Integrations and Troubleshooting Ecosystem Bridges, Airdrops, WorldGuard, and Vehicle MC

Server Operations

Admin Commands and Permissions

Review the Duck Shot command lanes, aliases, and important permission nodes.

Plugin downloadsDuck Shot

This page covers the public admin surface for Duck Shot: the main command entry points, the important aliases, and the core permission nodes.

Base command

Duck Shot registers:

TEXT

/duckshot

Aliases:

/ds
/shot
/gun
/guns

Main command lanes

The root command advertises these public lanes:

list
get
give
ammo
menu
reload
state
input
scope
editor
particles

The exact arguments for some subcommands may evolve by build, but that list gives you the public page to expect.

Most useful commands day to day

Reload

Use Duck Shot reload tools when you need the plugin to re-read changed configs after editing weapon or support files.

Give and get

Use the give or get flows when testing whether a weapon is configured correctly. This avoids the most common item-tagging mistakes.

Particles tools

Use:

/duckshot particles list
/duckshot particles test <profileIdOrPrefix> [emit|play]

Those are especially useful while tuning Particles v2.

Core permissions

Duck Shot defines these base permission nodes:

duckshot.admin
duckshot.give
duckshot.use
duckshot.bypass.item_categories.hotbar_limits
duckshot.bypass.item_categories.held_effects

What they are for

`duckshot.use`

Normal player usage permission.

`duckshot.admin`

Administrative control over the plugin command surface.

`duckshot.give`

Lets staff or automation give Duck Shot content items directly.

bypass permissions

These are intended for ops, testing accounts, or special roles that should ignore category-limit or held-effect restrictions.

Recommended role split

Staff

duckshot.use
duckshot.give

Admin or builder

duckshot.admin
duckshot.give
duckshot.use

Testing account

Add the bypass permissions only when you really want to ignore normal category rules during testing.

Best practice

Reload after meaningful file edits

Do not assume the server picked up a new weapon file or effect profile automatically.

Test with a real give flow

If a weapon works only when spawned in a strange way, that usually means the item identity or tags are wrong.

Keep one clean admin account

Have at least one account with normal permissions only and one with bypass permissions. That makes it much easier to see whether a problem is config-related or permission-related.

PreviousSky Select, Airstrikes, and Support Callers Integrations and TroubleshootingNext