Brick Bridge

Brick Bridge keeps framework and provider differences behind one shared integration layer. Brick Scripts products use it for framework lifecycle, inventory, target, notification, database, banking, medical, progress, minigames, Text UI, and other selected capabilities.

Requirements

• ox_lib
• One supported framework: QBCore, Qbox, or ESX Legacy
• The native providers selected in the bridge configuration

Caution

Provider selection runs once from current resource state and stays frozen until the bridge restarts. There is no background retry, failover, or automatic provider switching.

Next steps

1. Place frameworks and providers before brick_bridge in your startup order.
2. Configure only providers that exist in your installed bridge release.
3. Start Brick Bridge before its consumers.
4. Review the complete compatibility list.

Integration contracts are intentionally not published in this documentation yet.