Airdrops

The plugin handles the full event pipeline: when drops happen, where they can happen, what they look like, how they open, and what rewards are delivered when players get there.

That makes it useful as both a gameplay system and an event-operations tool. It is not only about the reward crate. It is about everything around the drop that makes players care.

After the first boot, the core admin surface lives in config.yml and crateTypes.yml. That covers scheduler cadence, interactions, visuals, zones, rewards, and cleanup rules.

callins:
  crackshot:
    enabled: false
    weaponTitle: "flaregun"
interactions:
  crate:
    blockClickRadius: 1.75

Use one crate family, one zone, one manual flare, and one scheduled drop as the first milestone. If those feel stable, the larger event surface is worth expanding.

That breadth is what makes the plugin useful on event-heavy servers. Staff can manage scheduler flow, manual activations, crate content, visuals, and cleanup without stitching several different tools together.

It also means the server can treat drops as a repeatable live event instead of one-off manual admin theater.

Use the gallery to show one scheduled plane or display flyover, one manual flare call-in, and one opened reward scene that proves the drop is worth fighting over.

That immediately communicates the difference between a cinematic event system and a simple loot chest plugin.