Brick Bridge installation

Brick Bridge requires ox_lib, one supported framework, and any optional provider resources you select.

1. Install the resource

Copy the release folder into your server resources directory as brick_bridge. Do not install the separate QA resource on a production server.

2. Configure providers

Open config.lua and choose a framework plus any optional provider categories. Every selector accepts:

• auto to select the first compatible resource that is already started;
• disabled for an optional category you do not use;
• an exact provider identifier from the compatibility list.

Explicit selection never falls through to a different provider. A selected provider must belong to the active framework and any required companion resource must already be started.

3. Set the startup order

ensure oxmysql
ensure ox_lib

# Start exactly one framework.
ensure qb-core
# ensure qbx_core
# ensure es_extended

# Start every provider selected by Brick Bridge here.
ensure brick_bridge

# Start Brick Scripts consumers after the bridge.

The bridge validates its required ox_lib support and selects providers synchronously from current resource state. It does not wait for missing resources, retry, fail over, or switch providers while running.

Caution

The ensure ox_lib line belongs in normal server startup configuration. Never restart, reload, or run ensure ox_lib on an already running server.

4. Check readiness

Confirm the server console reports a ready bridge with the framework and provider selections you intended before starting dependent products. Treat a configured provider name as a choice, not proof that the resource started successfully.

Provider changes

When you change, update, or restart a selected framework/provider, restart brick_bridge before restarting its consumers. The bridge intentionally keeps its selected provider set frozen for the lifetime of the resource.

Common startup problems

• If ox_lib support is unavailable, correct its install/start order and restart the bridge.
• If provider configuration is invalid, use auto, disabled, or an exact provider from the current matrix.
• If a resource was not started in time, move it before Brick Bridge in server.cfg.
• If the provider does not match the active framework, select a compatible provider.
• If an appearance or phone integration needs a companion resource, start that companion before the bridge.