Framework and Target Integration

Framework, inventory and target are separate settings. Choose a compatible combination for your server and start its dependencies before F5 Airdrop. All settings below are in config/config.lua.

Framework detection

With Config.Framework.mode = 'auto', detection uses this priority among resources that are already started:

1. qbx_core selects qbx.
2. qb-core selects qb.
3. es_extended selects esx.

To select a framework explicitly, use:

Value	Framework
qb	QBCore
qbx	Qbox
esx	ESX
custom	A custom integration based on QBCore, Qbox or ESX.

F5 Airdrop requires a supported framework; standalone mode is not available. Restart the resource after changing the selection. See Items and Inventory for the separate inventory setting.

Notifications

Set Config.Framework.notify to choose the notification provider:

Value	Behavior
auto	Prefer ox_lib when it is running. QBCore and ESX otherwise use their framework notifications.
oxlib	Select OX notifications when ox_lib is running. QBCore and ESX fall back to framework notifications if it is unavailable.
framework	Use the selected framework's notification integration.

On a standard Qbox installation, use framework for Qbox notifications, or start ox_lib for auto and oxlib. Custom framework notifications may require changes in the editable bridge/ integration.

Target selection

Set Config.Target.system to:

Value	Target system
auto	Prefer running ox_target, then qb-target.
ox	ox_target
qb	qb-target
custom	A compatible target configured through the editable bridge.
none	Disable the bundled target interaction.

Players open containers from the front doors while aiming at the doorway. Use Config.Target.distance to configure interaction range, Config.Target.openLabel for the label and Config.Target.openIcon for the icon. The default label uses a translation key from locales/.

none does not provide an alternative key interaction. Use it only with a prepared custom interaction system. If an open container cannot be targeted from its doors, check the selected target resource's own distance settings or contact support.

Custom framework

Set Config.Framework.mode = 'custom' and Config.Framework.custom.base to qb, qbx or esx. Custom mode extends one of these supported frameworks; it is not a standalone framework option.

Adapt the supplied open files in bridge/ to your framework. For assistance, provide support with the framework name, version and relevant customizations. Administrator access still requires the permissions described in Commands and Permissions.

Custom target

For a renamed target that remains compatible with an OX or QB target integration, configure its base and resource name:

config/config.lua

Config.Target.system = 'custom'
Config.Target.custom = {
    base = 'ox',
    resource = 'my-target',
}

Use base = 'ox' or base = 'qb' to match your target and replace my-target with its installed resource name. Other target systems require an adapted integration in the editable bridge/ files. Contact support for compatibility assistance.

See Custom inventory for inventory integrations.