FAM Tools
Sign in
Library · Community Bridge

community_bridge for FiveM

What it is

A compatibility layer that lets one script run on ESX, QBCore, Qbox and ox_core without a fork per framework.

Every script author eventually faces the same problem: three frameworks, three inventories, two targeting systems and one codebase. A bridge resource abstracts those behind a single API so a weapon shop can ask for the player's job without caring which core answers.

Official documentation Repository All resources

Why servers run it

  • One codebase instead of an ESX build and a QBCore build that drift apart.
  • Covers the parts that actually differ: player data, inventory, notifications, targeting, menus and progress bars.
  • Lets a server swap an inventory or a framework later without rewriting every script that touched it.

Installing community_bridge

  1. 1. Start it before your own resources

    The bridge detects what is installed at start, so it has to load after the framework and before anything that calls it.

  2. 2. Declare it in your fxmanifest

    Add it as a shared_script import the same way you would ox_lib.

  3. 3. Read the detection log

    On first start it prints which framework, inventory and target system it found. If that line is wrong, everything downstream will be too.

Working examples

One weapon-shop check, four frameworks

-- Instead of branching on ESX vs QBCore vs Qbox, ask the bridge.
local job = Bridge.Framework.GetPlayerJob(source)
if job.name ~= 'police' then return end

Bridge.Inventory.AddItem(source, 'WEAPON_CUSTOMPISTOL', 1, {
    durability = 100,
})
Bridge.Notify.SendNotify(source, 'Weapon issued', 'success')

What goes wrong

A bridge is only as good as its detection. If you run two inventories, or a renamed framework folder, it will guess and guess wrong.

It adds a layer, not magic. Framework-specific behaviour that has no equivalent elsewhere cannot be bridged; it can only be reported as unsupported.

community_bridge — questions people ask

Do I need a bridge as a server owner?
Only if a script you install requires it. Bridges are aimed at script authors; servers install them because a resource asked for one.

Runs alongside

ox_lib

The shared library half the modern FiveM ecosystem depends on: menus, notifications, progress bars, zones, callbacks and a cache.

qbx_core (Qbox)

A maintained fork of QBCore rebuilt on ox_lib and ox_inventory, with typed exports, semantic versioning and a much cleaner core.

es_extended (ESX Legacy)

The original FiveM roleplay framework, still running a very large share of live servers — jobs, money, society accounts and a huge script catalogue.

qb-core (QBCore)

The roleplay framework most new FiveM servers are built on, with the largest modern script ecosystem and a one-click txAdmin recipe.