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
The top-level sections that matter`general``interactions.crate``scheduler``callins``smokePlume``dropPhysics``effects``messages``chunkHandling` and `cleanup``admin`A good editing orderNext pages
Getting Started

Core Config and Runtime

Understand the global config surface for interactions, scheduler behavior, call-ins, visuals, messages, and cleanup.

Plugin downloadsAirdrops

config.yml is the server-wide admin tools for Airdrops. It decides how drops are scheduled, how crates can be opened, how display entities look while falling, and how the plugin cleans up after itself.

The top-level sections that matter

The current config is organized around these major blocks:

  • general
  • interactions
  • scheduler
  • callins
  • smokePlume
  • dropPhysics
  • effects
  • messages
  • chunkHandling
  • cleanup
  • admin

If you treat crateTypes.yml as the only important file, you will miss most of the live-server behavior that makes drops feel good or broken.

general

This is the broad server policy layer.

Important keys:

  • enabledWorlds
  • debug
  • onlyOneActiveDrop
  • nearbyAnnouncementRadius

This is where you decide whether the server behaves like a tightly controlled event lane or a looser sandbox where drops can overlap more often.

interactions.crate

This section controls how players actually open crates.

Important keys include:

  • blockClickRadius
  • ignoreInteractableBlocks
  • searchRadius
  • cleanupRadius
  • hitboxWidth
  • hitboxHeight
  • projectileOpens
  • projectileMode
  • projectileHitboxExtra

The biggest practical settings here are the ones that stop foliage or nearby blocks from eating right-clicks and the ones that decide whether shots open the crate or shoot it down into an impact-open flow.

scheduler

This is the timed drop pipeline.

Important keys:

  • enabled
  • baseIntervalMinutes
  • randomJitterMinutes
  • announceOffsetsSeconds
  • autoReschedule

If the server depends on drops as a recurring event loop, this is the section to lock down before you touch the crate families.

callins

This is the manual drop path layered on top of the scheduler.

Important keys:

  • enabled
  • ignoreOnlyOneActiveDrop
  • cloud.*
  • torch.*
  • crackshot.*

If you want scheduled drops to stay limited while allowing staff or players to use flare call-ins separately, this section is where that policy lives.

smokePlume

This controls the staged smoke effect used by call-ins.

Important keys:

  • tickIntervalTicks
  • baseYOffset
  • growth.*
  • colorInterpolation.*
  • smokeLayer.*
  • stages

The stage list is especially important if you are trying to preserve the older MCWAR green-to-red warning plume while still using the modern display-based plugin.

dropPhysics

This controls where drops begin and how they travel down.

Important keys:

  • defaultDropY
  • minGroundY
  • descentBlocksPerSecond
  • parachuteAttachDelaySeconds
  • minClearanceAbove
  • glide.*

This is the difference between crates that feel cinematic and crates that feel like a vertical teleport with particles.

effects

This is the visual and audio backbone for the modernized build.

The biggest subsections are:

  • viewRange
  • displaySmoothing
  • sway
  • plane
  • parachute
  • crate

Inside effects.crate you will find the main live-server behavior for:

  • landing sounds and particles
  • open sounds and particles
  • deliveryMode
  • container inventory rules
  • blastOpen
  • lootSpray
  • denied-open feedback
  • panel open behavior

This section matters just as much as the crate entry itself.

messages

This controls player-side announcement output for both scheduled drops and call-ins.

The current config uses chat, title, subtitle, and actionbar message lanes for announcements, plus call-in deployment messaging.

chunkHandling and cleanup

These sections exist to keep long-flying display pipelines from becoming a restart problem.

Important cleanup keys:

  • enabled
  • cleanOnChunkLoad
  • recordFlightPath
  • startupSweep.enabled
  • startupSweep.chunksPerTick
  • targets

If a server has ever been hard-killed with planes in the air, these sections are not optional reading.

admin

The admin.visualTuning.timedPreview settings control how long preview visuals stay up and where they appear in front of the admin.

That matters when you are tuning models and animation behavior in-game instead of blindly reloading YAML.

A good editing order

For most live servers, use this order:

  1. general
  2. interactions
  3. scheduler
  4. callins
  5. dropPhysics
  6. effects
  7. messages
  8. cleanup

Only after that should you start major reward balancing in crateTypes.yml.

Next pages

Use these pages together:

PreviousInstall and First BootCrate Types, File Structure, and Crate FamiliesNext