How do I update the script?

1. Download the latest from CFX Portal. 2. Back up your config files. 3. Replace all files except your config. 4. Restart the resource. Your edited planes, crates, loot, zones and flares live in the database, so they are kept across updates.

F.A.Q

Q: How do I change the language?

Set the code in the config. See the `locales/` folder for what ships. **shared/config.lua** ```lua Config.locale = 'it' ```

Q: How do I open the admin panel?

Type `/airdrop` in chat as an admin. Change the command with `Config.Admin.Command`.

Q: Can a drop be private to one player?

Yes, for drops started by another script. Pass `contested = false` and `triggeredBy` to `TriggerAirdrop` and only that player can loot it. Automatic, admin and flare drops are open to everyone.

Q: How does the XP reward work?

When `Config.Skills.enabled` is on, each crate has an XP budget in one or more categories. The budget is split across the loot slots, so each player earns XP for the slots they take.

3 min readUpdated 2 weeks ago

Setup

Set the code in the config. See the locales/ folder for what ships.

shared/config.lua

1Config.locale = 'it'

Type /airdrop in chat as an admin. Change the command with Config.Admin.Command.

Yes. oxmysql is required. The tables are created automatically on first start.

Drops

Use the global timer for one automatic schedule, or choose independent timers for each zone. Intervals are in minutes; equal minimum and maximum values give a fixed interval.

shared/config.lua

1Config.AutoEvents.mode = 'global'
2Config.AutoEvents.interval = { min = 30, max = 45 }

For separate timers, select Timers per zone in Settings and configure Automatic drops, Minimum gap and Maximum gap in Zones. The same settings can be assigned in the configuration:

shared/config.lua

1Config.AutoEvents.mode = 'zones'

shared/data/zones.lua

1Config.Zones.sandy.auto = {
2    enabled = true,
3    interval = { min = 30, max = 30 },
4}

A zone launch waits while the online player requirement is unmet, the shared drop limit is reached, or another drop is active in that zone. The Control tab shows the reason. Each zone keeps one pending launch, so clearing the condition does not produce a backlog of drops.

Saved zone settings remain in the database. The countdowns start fresh when the resource restarts; missed launches are not replayed. Editing unrelated settings preserves running timers, while changing a zone interval restarts that timer.

Yes, for drops started by another script. Pass contested = false and triggeredBy to TriggerAirdrop and only that player can loot it. Automatic, admin and flare drops are open to everyone.

Edit the loot table in the admin panel. Entries can be items, weapons, cash or bank money, each with a weight, a rarity flag and stack sizes.

A vehicle crate rolls one vehicle from a weighted pool and lands it locked and empty. The winner gets the keys, or the vehicle as an owned vehicle, with fuel restored on claim. Ownership works on Qbox as shipped, QBCore and ESX need the supplied registration snippet. Set this with Config.VehicleClaim.

Rewards

When Config.Skills.enabled is on, each crate has an XP budget in one or more categories. The budget is split across the loot slots, so each player earns XP for the slots they take.

Logging

Yes. Each action has its own webhook in server/config_server.lua. Set the ones you want and leave the rest empty to fall back to Default.

Updates

Download the latest from CFX Portal.
Back up your config files.
Replace all files except your config.
Restart the resource.

Your edited planes, crates, loot, zones and flares live in the database, so they are kept across updates.