Install Brick Bridge for FiveM

Brick Bridge requires ox_lib, one supported framework, and the provider resources needed by your product.

1. Install the resource

You need the separate brick_bridge resource alongside your purchased script. Use the release supplied through your official delivery location. If you cannot locate it, contact Brick Scripts support for access.

Copy the complete release to resources/[brick]/brick_bridge/. Confirm that fxmanifest.lua and config.lua are directly inside that folder.

2. Configure providers

Open brick_bridge/config.lua. For example, a QBCore server using ox inventory, target, notifications and database can select:

brick_bridge/config.lua

Config.Framework = 'qb-core'
Config.Inventory = 'ox_inventory'
Config.Target = 'ox_target'
Config.Notify = 'ox_lib'
Config.Database = 'oxmysql'

Edit those existing settings; keep the other shipped settings your product needs. Use the compatibility list for exact identifiers.

Selector value	Effect
auto	Selects a compatible provider that is already running, in the bridge’s category priority order.
Exact provider identifier	Selects that provider; it must be running and compatible with your framework.
disabled	Disables a provider category. Use only for categories none of your products require. The framework cannot be disabled.

For Config.Framework = 'auto', Qbox takes priority over QBCore, then ESX. For inventory, ox_inventory takes priority; qb-inventory is skipped when qs-inventory is running. For target, ox_target takes priority over qb-target. Select an exact identifier when several providers are installed and you want a specific one. Legacy qb-inventory-v1 is explicit-only.

3. Set the startup order

Start ox_lib, your framework and the selected providers before Brick Bridge. Add the bridge before each dependent product in server.cfg:

server.cfg

ensure brick_bridge

See Startup order for a complete example and the recovery order after changing providers.

4. Check readiness

Confirm the resource starts without errors. Support diagnostics are silent with the default Config.Debug = false.

To check the selections, temporarily set Config.Debug = true and restart Brick Bridge before its consumers. Inspect bridge ready and the provider summary lines in the fresh server console. They show the selected framework, category, configured selector, provider and resource state. Client-only providers also report in F8 when a player joins. Resolve failures for categories your product requires. Set debug back to false after checking and apply the same restart order.

If the resource’s update checker reports it is outdated and an update is available, updating is strongly recommended. For a startup failure, follow Troubleshooting.