> For the complete documentation index, see [llms.txt](https://otters-developments.gitbook.io/otters-developments/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://otters-developments.gitbook.io/otters-developments/paid-resources/airdrop.md).

# Airdrop

Otters Airdrop is a modern and configurable airdrop system for FiveM supporting **QBCore, Qbox and ESX**.

Create server-wide supply drop events with an aircraft flying into the area and releasing a parachuting supply crate for players to locate and loot. Airdrops can use configurable loot tiers, unlock timers, KOS zones, map blips, flare effects and server-wide notifications.

Authorised staff can create and manage drops through the custom Airdrop Panel with live status information for every active airdrop.

## Features

* Modern custom Airdrop Panel
* QBCore, Qbox & ESX support
* Automatic framework detection
* Multiple simultaneous airdrops
* Configurable loot tiers
* Configurable items and quantities
* Aircraft fly-in system
* Configurable aircraft model
* Aircraft map blip
* Parachuting supply crates
* Surface and landing detection
* Supply crate flare effects
* Crate map blips
* Configurable radius and KOS zones
* Post-loot KOS removal delay
* Configurable landing and unlock timings
* Live airdrop status and countdowns
* Locked crate hologram
* Server-wide incoming and looted broadcasts
* Active Airdrop Manager
* Edit, lock, unlock, teleport and delete active airdrops
* Multiple inventory integrations
* Multiple target integrations
* Multiple notification integrations
* Press E interaction fallback
* Optional required key item
* Optional unlock minigame
* Configurable minimum players
* Configurable airdrop cooldown
* ACE permission support
* Discord webhook logging
* Server-side loot validation
* Configurable UI theme

## How Airdrops Work

When an airdrop is created, the configured aircraft approaches the selected location. The exported documentation uses the Titan as the default aircraft.

Once the aircraft reaches the drop zone, the crate is released and descends toward the ground. Players can follow the aircraft, parachuting crate, map blips and KOS zone to locate it.

After landing, the crate remains locked for the configured duration before becoming available to loot.

## Airdrop Panel

Authorised staff can configure the location, loot tier, unlock time and KOS options before deploying an airdrop.

The Active Airdrop Manager shows live statuses such as **Inbound**, **Falling**, **Locked** and **Ready**, with countdowns where applicable.

## Loot Tiers

Each tier can contain its own items and minimum/maximum quantities. This allows different drop types such as standard, rare, military, event or high-value drops.

## KOS Zones

Individual airdrops can have a configurable Kill On Sight radius. The zone can remain active for a configured period after the crate is looted before disappearing.

## Framework Support

* QBCore
* Qbox
* ESX

## Integrations

The exported documentation lists inventory support including ox\_inventory, qb-inventory and framework inventories, plus ox\_target and qb-target support with a Press E fallback.

## Editable Files

* `shared/config.lua`
* `html/css/theme.css`

## Installation

{% stepper %}
{% step %}

### Place the resource

Place the resource in your server resources folder.
{% endstep %}

{% step %}

### Configure the resource

Configure `shared/config.lua`.
{% endstep %}

{% step %}

### Configure permissions and integrations

Configure ACE permissions and integrations.
{% endstep %}

{% step %}

### Add the resource to your start order

Add the resource to your server start order.
{% endstep %}

{% step %}

### Restart

Restart the resource/server.
{% endstep %}

{% step %}

### Verify the airdrop flow

Create a test airdrop and verify the aircraft, crate, unlock, loot and cleanup flow.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://otters-developments.gitbook.io/otters-developments/paid-resources/airdrop.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.