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 Public and Server Release Distributions 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

Public distribution Public starter roster Server distribution Shared update contract Resource pack handoff Why this split exists

Example Library and Pack Planning

Public and Server Release Distributions

Understand how Duck Shot ships selected public starter content and the fuller server distribution from one shared release pipeline.

Plugin downloadsDuck Shot

Duck Shot now ships from one shared source pipeline that produces two release flavors in the same build run.

Public distribution

The public build is the selected starter release. It installs a small authored roster, keeps public examples under weapons/examples/, and ships a filtered public resource pack plus a ResourcePackAssistant handoff file.

Public starter roster

AIRSTRIKE_CASE
AIRSTRIKE_NUKE_CASE
ARCANE_WAND
CLAYMORE
COMBAT_KNIFE
CZ550
doublebarrel
FIELD_MACHETE
FLASHBANG
G17
GRAVITY_WAND
GRENADE
M16A2
M240
MOLOTOV
MP5
Thumper

Server distribution

The server build is the master/internal distribution. It installs the full bundled content set and packages the full server resource pack from the shared workspace.

Shared update contract

engine, editor, schema, and runtime changes are shared automatically
public docs are updated from the same release run
new concrete content defaults to server-only until it is promoted in the release manifest

Resource pack handoff

Duck Shot still leaves pack delivery to ResourcePackAssistant in this pass. The public dist folder includes the public pack zip, SHA1, metadata, and a sample ResourcePackAssistant config wired to a placeholder URL.

Why this split exists

The public release should feel like a clean starter canvas with strong examples. The server release remains the full authored arsenal. One manifest layer now controls both so the pipeline stays synchronized instead of drifting into two manual maintenance tracks.

PreviousStarter Packs, Example Files, and Server-Only Content Weapon Archetype RecipesNext