Skip to main content
Block Arsenal

Wiki

Airdrops wiki

Wiki

Airdrops Wiki

Scheduled drops, flare call-ins, loot crates, admin tooling, and crash-safe cleanup for MCWAR Airdrops.

Getting Started

Start here for the current Paper build, first boot checks, and the runtime settings that affect every drop.

Wiki HomeInstall and First BootCore Config and Runtime

Crate Authoring

Learn how crate families are structured, where the loot really lives, and how zones and models fit into one crate definition.

Crate Types, File Structure, and Crate FamiliesLoot Tables, Open Actions, and Container DeliverySpawn Zones, Drop Physics, and Landing BehaviorModels, Displays, Panels, and Open Animations

Drop Pipeline and Effects

Run the scheduled event lane, manual call-ins, and the staged smoke signaling that tells players where to look.

Scheduler, Call-Ins, and Smoke Plumes

Admin and Operations

Use the in-game tools, command surface, migration support, and cleanup systems that make the plugin maintainable on live servers.

Admin GUI, Migration, and Live EditingCommands, Permissions, and Admin WorkflowsCleanup, Crash Recovery, and Troubleshooting
Permission modelCore command surfaceCommands worth memorizing`cancel` vs `cancelall`Suggested orderRoutine crate maintenanceEvent setupEmergency debuggingSafe staff boundariesNext pages
Admin and Operations

Commands, Permissions, and Admin Workflows

Review the active admin command surface, the permission node, and the workflows staff should actually use in production.

Plugin downloadsAirdrops

This page is the practical command reference for live-server staff.

Permission model

The current plugin registers one main admin permission:

YAML
mcwar.airdrops.admin

By default it is op.

If you delegate Airdrops management to staff, this is the first thing to route through your permissions setup.

Core command surface

The main command is:

TEXT
/airdrop

The current source exposes these admin paths:

  • /airdrop help
  • /airdrop gui
  • /airdrop crate <crateType>
  • /airdrop loot <crateType>
  • /airdrop addhand <crateType> <chance>
  • /airdrop create <crateType> [displayname...]
  • /airdrop clone <from> <to>
  • /airdrop delete <crateType>
  • /airdrop migrate
  • /airdrop status
  • /airdrop spawnhere [cratetype]
  • /airdrop schedule
  • /airdrop cancel
  • /airdrop cancelall
  • /airdrop givetorch <crateType> [player] [amount]
  • /airdrop reload
  • /airdrop debug [on|off]
  • /airdrop timer <seconds>
  • /airdrop item add <crateType> <logicalId>
  • /airdrop item addhand <crateType> <chance>
  • /airdrop command add <crateType> <chance> <as> <command...>
  • /airdrop message add <crateType> <chance> <scope> <text...>
  • /airdrop zone help

Commands worth memorizing

For real staff work, these are the most useful:

  • status
  • spawnhere
  • gui
  • loot
  • reload
  • cancelall
  • givetorch
  • migrate
  • debug

That set covers most live editing, event handling, and emergency response.

cancel vs cancelall

Do not treat these as the same command.

/airdrop cancel is the scheduler-only lane.
/airdrop cancelall is the broad cleanup lane for scheduler drops plus manual and call-in drops.

That distinction matters a lot on live servers during events.

Suggested order

Routine crate maintenance

  1. inspect the crate in /airdrop loot <crateType>
  2. simulate the roll
  3. spawn a local test
  4. reload only after validation

Event setup

  1. confirm scheduler state with /airdrop status
  2. confirm the correct crate family exists
  3. give or test flare torches if call-ins are part of the event
  4. keep cancelall ready in case an event needs a hard stop

Emergency debugging

  1. run /airdrop debug on
  2. reproduce the issue once
  3. collect what matters
  4. run /airdrop debug off

Safe staff boundaries

If you split responsibilities across staff, a clean model is:

  • event staff use status, spawnhere, givetorch, cancel, and cancelall
  • content staff use gui, crate, loot, addhand, and migrate
  • senior admins use reload, deep zone edits, and schema maintenance

That reduces the chance of someone improvising a destructive live edit during an event.

Next pages

PreviousAdmin GUI, Migration, and Live EditingCleanup, Crash Recovery, and TroubleshootingNext