Loading content...
Detection & config
How the bridge picks your framework and systems automatically — and how to force or disable any of them.
How the bridge picks your framework and systems automatically — and how to force or disable any of them.
The bridge figures out your setup on its own: the framework, and which inventory, keys, fuel and dispatch system you run. Most of the time you configure nothing. When you run several at once, a convar lets you force the right one.
On boot, the bridge checks which resources are started and picks the first match for each axis. You get one line per axis in the console:
[INFO] Bridge: framework esx detecte
[INFO] Bridge: inventaire ox_inventory detecte
[INFO] Bridge: cles vehicule none detecte
[INFO] Bridge: fuel native detecte
[INFO] Bridge: dispatch none detecteWhen nothing matches, the axis falls back to a safe default (vanilla, framework, none
or native). The bridge always loads — it never blocks your server.
Set the matching convar in your server.cfg. auto (the default) keeps auto-detection.
Use setr so the value reaches the client too.
setr see:inventory "ox_inventory"see:frameworkstringoptionalThe framework. Values: esx, qbcore, qbox, ox, vanilla. Default auto.
see:inventorystringoptionalThe inventory. Values: ox_inventory, qs, ps, codem, origen, tgiann, jaksam, or framework (the framework's own inventory). Default auto.
see:keysstringoptionalThe vehicle keys system. Values: qbx, qb, wasabi, renewed, mrnewb, qs, jaksam, or none. Default auto.
see:fuelstringoptionalThe fuel system. Values: statebag (ox_fuel), legacy, cdn, renewed, qb, lc, ps, rcore, qs, nd, bigdaddy, gks, rip, my, lj, melons, hrs, or native. Default auto.
see:dispatchstringoptionalThe dispatch system. Values: cd, ps, qs, rcore, origen, tk, pmdt, or none. Default auto.
If you don't need the multi-framework layer at all, disable it entirely:
see:bridgestringoptionaltrue (default) loads the bridge; false skips it completely. With it off, any access to lib.bridge raises a clear error instead of silently doing nothing.
Force a system whose resource isn't running and the bridge won't crash — it warns and falls back to auto-detection:
Bridge: convar see:dispatch "cd" -> cd_dispatch non demarre, retour a l'auto-detectionA typo, or a forced system you forgot to install, degrades gracefully instead of taking the server down.
Most third-party adapters are written from each product's public API but haven't been verified in-game yet. If one misbehaves, the product's API may have changed since — report it and we'll update the adapter.
Not sure what got picked? The detection lines are printed on boot (server console and F8),
and exposed as lib.bridge.framework, lib.bridge.inventorySystem, and so on.