Install guide

Airdrop System

QBCore / QBox / ESX · configure zones, rewards and admin commands

Tip. Test airdrops on a staging server first - rewards and zone size are easier to tune offline than on a live city.

1. Requirements

  • QBCore, QBox or ESX (see product page for your build)
  • ox_lib recommended for notifications / progress
  • Inventory system used by your framework (ox_inventory or equivalent)
  • OneSync enabled on the server

2. Download

  1. Claim the asset from the Cfx.re portal after purchase.
  2. Download and extract the airdrop resource folder.

3. Installation

  1. Place the folder in your resources directory.
  2. Ensure dependencies start first, then the airdrop resource:
ensure ox_lib
ensure ox_inventory
ensure qb-core # or es_extended / QBox stack

ensure 1017-airdrop
  1. Restart the server and confirm the resource starts without errors.

4. Configuration

Open the config file and set:

  • Framework bridge - match QBCore / QBox / ESX.
  • Drop intervals & chance - how often automatic drops can occur.
  • Zones / locations - allowed drop areas or random bounds.
  • Crate rewards - item names and amounts that exist in your inventory.
  • Commands / permissions - admin force-drop ACE or job restrictions.
  • Blips & notifications - visibility for players when a crate is active.
Performance. Avoid huge simultaneous particle / object counts on low-end hosts. Start with fewer active crates and scale up.

5. Verify it works

  1. Use the admin command (if enabled) to force an airdrop.
  2. Confirm the blip / notification appears for players.
  3. Reach the crate, complete the capture flow, and receive configured loot.
  4. Watch server resmon while a crate is active.

6. Troubleshooting

IssueWhat to check
No drops spawnTimers, zone config, resource actually started, console errors
Players get no itemsReward item names vs inventory; inventory export/framework bridge
Only admins see eventsNotification settings and permission checks in config

Product page: Airdrop System