Skip to main content
The 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 off Bridge 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

Bridge.IsAdmin(src) is a framework admin check (e.g. ESX/QB group), and is separate from the Discord-role permission system. For permission nodes backed by ACEs and Discord roles, use Bridge.Permissions.Has(src, node) — see Permissions.

Lifecycle hooks

React to player load, job change, and unload without touching framework-specific events.

Inventory

Item operations are normalized across ox_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 player src.
Treat every inventory action as server-authoritative. Never decide an item exists or a balance is sufficient on the client — call these server-side, and validate any client request through Bridge.Net first.

Running an unsupported stack?

If the bridge does not ship support for your framework or inventory, fill the editable adapter and point a convar at custom. 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.