> 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/configuration.md).

# Configuration

Otters Airdrop is configured primarily through `shared/config.lua`. Visual customisation is handled separately through `html/css/theme.css`.

## Framework

```lua
Cfg.Framework = 'auto' -- auto | qb | qbx | esx | standalone
```

When set to `auto`, the resource attempts to detect the framework running on the server.

## Integrations

The exported documentation lists support for multiple inventory, target, and notification systems.

### Inventory

Documented inventory support includes:

* ox\_inventory
* qb-inventory
* QBCore
* Qbox
* ESX

### Target

Documented target support includes:

* ox\_target
* qb-target

Servers without a supported target system can use the built-in Press E interaction.

### Notifications

The exported documentation lists options including:

* Built-In System
* ox\_lib
* okokNotify
* QBCore
* Qbox
* ESX
* mythic\_notify
* Chat

The built-in Otters notification system can also have its screen position configured.

## Aircraft

Aircraft settings can be configured, including:

* Aircraft model
* Height
* Speed
* Approach distance
* Fly-away distance
* Optional moving aircraft blip

The exported documentation uses the Titan as the default aircraft.

## Loot Tiers

Loot tiers control the rewards available from an airdrop. Each loot entry can have configurable minimum and maximum quantities.

Use separate tiers for different event values, such as standard, rare, military, event, or high-value drops.

## Drop & Unlock Timings

Landing and unlock timings are configurable. Active drops show live status/countdown information in the Airdrop Manager.

## KOS Zones

KOS zones can be enabled per drop and can have a configurable radius. The post-loot removal delay controls how long the zone remains active after the crate has been looted.

## Blips & Broadcasts

The resource can display aircraft/crate map blips and send server-wide incoming and looted broadcasts.

## Minimum Players & Cooldown

Airdrops can require a configurable minimum number of players and can use a configurable cooldown to control how frequently drops are created.

## Permissions

Staff access is controlled using ACE permissions. Configure the ACE values used by your copy of the resource in `shared/config.lua` and add the matching rules to your `server.cfg`.

## Discord Logging

Discord logging can be enabled or disabled. The exported documentation lists events such as:

* Aircraft Incoming
* Crate Ready
* Crate Looted

## UI Theme

Edit:

```
html/css/theme.css
```

to customise the Airdrop Panel and supported built-in UI elements.

## Asset Escrow

The documented customer-editable files are:

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

The remaining protected runtime files are handled through FiveM Asset Escrow.


---

# 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/configuration.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.