Items and Inventory

Each loot entry has its own quantity and chance. Loot is generated when the container lands or is placed at its destination. The cargo visible inside the container is decorative and does not indicate its remaining contents.

Define loot

Configure items in config/config.lua:

config/config.lua

Config.AirdropCoords[1].items = {
    {name = 'weapon_pistol', amount = 1, chance = 50},
    {name = 'pistol_ammo', amount = {2, 4}, chance = 75},
    {name = 'heavyarmor', amount = 1, chance = 100},
}

Field	Value
name	Item name registered in your inventory.
amount	Nonnegative integer or inclusive {minimum, maximum} range. Defaults to 1 when omitted.
chance	Percentage from 0 to 100. Defaults to 100 when omitted.
info	Optional item metadata supported by your inventory.

Use whole numbers for quantities and keep the maximum at least as large as the minimum. An amount of zero skips the item. Each chance is independent: three entries at 50% can produce zero, one, two or three entries.

The selected inventory determines which item names, metadata and capacities it accepts. Configure stash capacity through Config.Stash.weight and Config.Stash.slots, or the corresponding per-drop settings. See Drop Settings.

Adapter selection

Set Config.Framework.inventory in config/config.lua:

Value	Inventory
auto	Detect a running inventory.
ox	ox_inventory
qb	qb-inventory
ps	ps-inventory
qs	qs-inventory
codem	codem-inventory
tgiann	tgiann-inventory
esx_native	Native ESX items; no airdrop stash support.
custom	Custom integration through the editable bridge.

Automatic detection uses this priority:

ox_inventory → qs-inventory → ps-inventory → codem-inventory → tgiann-inventory → qb-inventory.

On ESX, detection falls back to native items if none of these inventories is running. Native ESX inventory does not provide airdrop loot stashes. Install a compatible stash-capable inventory.

Start the selected inventory before F5 Airdrop. Use an explicit mode if multiple inventories run, and choose an inventory compatible with your framework. Detection by resource name does not establish compatibility with every release or fork.

OX inventory

Select ox for ox_inventory. Start its required dependencies before F5 Airdrop and use item names registered in that inventory.

QB inventory

Select qb for qb-inventory. The installed version must support the stash operations and stash access controls required by the supplied F5 integration. A version number alone does not establish compatibility. Older or modified inventories may need an adapted bridge; contact support with your inventory version before deploying such a setup.

Other adapters

PS, QS, CodeM and TGIANN integrations depend on the installed inventory release. Their stash opening, item transfers, access controls and cleanup must be compatible with the supplied bridge. For a modified inventory or an integration issue, use the editable files in bridge/ or contact support.

Catalog and images

Opening /airdropanel loads the registered item catalog for the selected inventory. This is the list of available item definitions, not the administrator's personal inventory.

Item images use the inventory's definitions and image location. The default locations are:

Inventory	Default image location
OX	The inventory:imagepath setting, otherwise nui://ox_inventory/web/images/.
QB / PS	nui://qb-inventory/html/images/ or nui://ps-inventory/html/images/.
QS	nui://qs-inventory/html/images/.
CodeM	nui://codem-inventory/html/itemimages/.
TGIANN	nui://inventory_images/images/, using .webp by default.

To use a shared image location, set:

config/config.lua

Config.Inventory.imageUrl = 'nui://inventory_images/images/%s.webp'

Replace the path with your installed image location. %s is replaced with the item name. This setting overrides individual item images. Set it back to 'auto' to use the selected inventory's image configuration. HTTP(S) image addresses are also supported and require the image host to be available.

Custom inventory

Set Config.Framework.inventory = 'custom' only after preparing a compatible integration. Custom inventory work belongs in the supplied editable bridge/ files and Config.Inventory.custom settings. The integration must support loot stashes as well as the panel's item catalog. Contact support if your inventory is not covered by the supplied adapters.

Item metadata preservation

The Custom Drop editor preserves each loaded item's info when launching or saving. Changing quantity or chance retains that metadata. Changing the item name removes the original metadata from that row; newly added rows start without metadata.

The form has no metadata editor. Define metadata in the configuration using fields supported by your inventory.