Bridge global gives you one provider-agnostic surface for player data. Write against Bridge.GetJob(src) and Bridge.Inventory.AddItem(src, ...), and the bridge routes to whatever framework and inventory the server runs. Account names and the job shape are normalized, so your code never branches on ESX vs QBCore.
Everything here is for resources building on the bridge. If you are configuring which framework/inventory the bridge uses, see Providers.
Framework
The most-used calls hang offBridge directly as shortcuts; the full surface is Bridge.Framework.
Server
The full
Bridge.Framework surface also includes GetSociety(job), AddSociety(job, amount), RemoveSociety(job, amount), and GetPlayersByJob(job).
Normalized job shape
Normalized accounts
Money accounts are always one of three normalized names, regardless of framework:Society balances require the framework’s banking resource (
esx_addonaccount, qb-banking, or Renewed-Banking). Without one, GetSociety / AddSociety / RemoveSociety are no-ops.Client
Lifecycle hooks
React to player load, job change, and unload without touching framework-specific events.- Server
- Client
Inventory
Item operations are normalized acrossox_inventory, qb-inventory, qs-inventory, ESX legacy, and the bridge’s virtual inventory.
Server
Client
Usable items
Register a use handler from the server. The bridge wires it to whatever inventory’s “use” path and calls your function with the playersrc.
Running an unsupported stack?
If the bridge does not ship support for your framework or inventory, fill the editable adapter and point a convar atcustom. The adapter contract is the exact method set documented here.
Custom Framework
The framework adapter contract and a worked example.
Custom Inventory
The inventory adapter contract and item shapes.
