Integrations

Fuel, vehicle keys, and targeting are optional. Advanced Bus Job works when none are installed by using safe built-in fallbacks.

Configure the three slots in config/shared.lua:

Config.Integrations = {
    fuel = 'auto',  -- auto | custom | none | resource name
    keys = 'auto',
    target = 'auto',
}

Modes

'auto' — selects the first supported resource that is already started
'custom' — uses the buyer-editable adapter in custom/<system>/custom.lua
'none' — uses the built-in fallback
Resource name — forces that exact resource; if it is not started, the script warns and falls back safely

Start integration resources before lx-busjob so auto-detection can see them:

ensure ox_fuel          # example
ensure qbx_vehiclekeys  # example
ensure ox_target        # example
ensure lx-busjob

Supported systems

Slot	Auto-detected resources	Fallback
Fuel	`ox_fuel`, `LegacyFuel`, `ps-fuel`, `cdn-fuel`, `Renewed-Fuel`, `lc_fuel`, `lj-fuel`	FiveM native fuel level
Keys	`qbx_vehiclekeys`, `qb-vehiclekeys`, `wasabi_carlock`, `MrNewbVehicleKeys`	Bus remains unlocked; no ownership key is registered
Target	`ox_target`, `qb-target`	`[E]` prompt at the depot NPC

Every built-in integration is now an open adapter file:

custom/
├─ fuel/    ox_fuel.lua, LegacyFuel.lua, ps-fuel.lua, cdn-fuel.lua,
│           Renewed-Fuel.lua, lc_fuel.lua, lj-fuel.lua, custom.lua
├─ keys/    qbx_vehiclekeys.lua, qb-vehiclekeys.lua, wasabi_carlock.lua,
│           MrNewbVehicleKeys.lua, custom.lua
└─ target/  ox_target.lua, qb-target.lua, custom.lua

You can inspect or adjust the adapter for your installed version without touching escrowed core logic.

Use the focused guides for setup details and official API references:

Detection log

About half a second after start, both client and server print the resolved slots:

[lx-busjob] Integrations — fuel: ox_fuel | keys: qbx_vehiclekeys | target: ox_target

If a forced resource is missing or a custom hook is left nil, the console also explains which fallback was used.