Integrations

How Integrations Work#

Nothing in the job's own logic knows which framework, key script or clothing system you run. Each of those sits behind a small, open bridge file, and the right one is picked from what is already running when the resource starts:

Layer	Supported	Without it
Framework	es_extended · qb-core · qbx_core	Required. There is no standalone mode.
Vehicle keys	qs-vehiclekeys · qb-vehiclekeys · qbx_vehiclekeys · F_RealCarKeysSystem · fivecode_carkeys · glfp10_carkeys · mono_carkeys · ti_vehicleKeys · vehicles_keys · wasabi_carlock · xd_locksystem

Integrations — Bus Driver Job for FiveM | Quasar Store | Quasar Store

lua

-- config/config.lua
Config.DefaultNotifications = false

function SendTextMessage(msg, type)
    -- ox_lib
    lib.notify({ description = msg, type = type == 'info' and 'inform' or type })

    -- or any other resource, e.g.:
    -- exports['okokNotify']:Alert('Bus', msg, 5000, type)
end

lua

-- config/config.lua
-- Auto, the default: the first running resource in the list wins.
Config.Vehiclekeys = dependencyCheck(vehicleKeys) or 'none'

-- Pinned: always this bridge, whatever is running.
Config.Vehiclekeys = 'qs-vehiclekeys'

Copy a bridge
Copy client/vehiclekeys/none.lua — or the bridge closest to yours — to a new file named after your key resource. Every file in that folder is loaded, and each one only runs when its name matches Config.Vehiclekeys.

Change the guard and the two calls

lua

-- client/vehiclekeys/my_keys.lua
if Config.Vehiclekeys ~= 'my_keys' then
    return
end

function AddVehiclekeys(vehicle, plate)
    exports['my_keys']:GiveKeys(plate)
end

function RemoveVehiclekeys(vehicle, plate)
    exports['my_keys']:RemoveKeys(plate)
end

Register it for detection
Add one line to the vehicleKeys list in config/config.lua — the running resource's name, then your bridge's name:
lua
```
local vehicleKeys = {
    ['qs-vehiclekeys'] = 'qs-vehiclekeys',
    -- ...
    ['my_keys'] = 'my_keys',
}
```

Event	Sent when	Fields
`MissionStarted`	A route is taken from the panel.	Bus, stops, pay, experience
`MissionFinished`	The bus is handed back and the route pays.	Pay, experience, crash penalty
`MissionAbandoned`	A route is abandoned from the panel, or left behind by disconnecting.	Passengers aboard
`MoneyPaid`	A route payout, and every ticket fare a driver receives.	Amount, what for, passenger
`ExperienceGiven`	Experience is granted.	Gained, level before → after, toward next, total

lua

-- config/config.lua
Config.Webhooks = {
    Enabled   = true,
    Url       = 'https://discord.com/api/webhooks/…', -- the shared channel
    Name      = 'qs-busjob',
    Avatar    = '',   -- an image URL, or '' for none
    Timestamp = true,

    Events = {
        MissionStarted   = true,  -- to the shared Url
        MissionFinished  = true,
        MissionAbandoned = false, -- not sent
        MoneyPaid        = 'https://discord.com/api/webhooks/…', -- a staff channel of its own
        ExperienceGiven  = true,
    },
}

Quest	Progresses when
`level_up_bus` — Bus Driver Progress	The driver levels up.
`complete_routes_bus` — Complete bus routes	A route is completed and paid.
`complete_multiplayer_routes_bus` — Complete multiplayer bus routes	A player passenger pays the driver a ticket.

How Integrations Work#

Integrations

How Integrations Work#

Notifications and Prompts#

Notifications#

3D prompts and the currency#

Vehicle Keys#

Adding a key system#

Copy a bridge

Change the guard and the two calls

Register it for detection

Target#

Clothing#

Fuel#

Discord Logs#

qs-inventory Quests#

Job Money and the Scoreboard#

Languages#