Installation
How to install Newb_Bridge. Start Newb_Bridge after ox_lib, your framework, inventory, target, and any other resource it bridges.
Start Newb_Bridge after ox_lib, your framework, inventory, target, and anything else it has to talk to. If those come up later, it can miss them and you’ll get the wrong provider, or none. Don’t start Newb_Bridge before the framework. Scripts that import @Newb_Bridge/import.lua have to start after the bridge. import.lua errors if the bridge ain’t running.
Requirements
ox_lib, oxmysql, and the framework / inventory / target you already run. Providers default to "auto" except Config.Dispatch, which defaults to "internal".
Get the resource
Grab the newest build from the Releases page and unzip it into resources. Keep the folder named Newb_Bridge, because import.lua finds the bridge by that name.
Use the release zip, not the source from the repo's main page. The Code → Download ZIP button and the main branch give you the raw source with no built UI, so menus and inputs will come up blank or broken. It's the same mistake as pulling ox_lib from its source tree instead of a release.
Add to server.cfg
ensure ox_lib
ensure oxmysql
ensure qbx_core # or qb-core / es_extended
ensure ox_inventory # your inventory
ensure ox_target # optional; any other bridged resource too
ensure Newb_Bridge
# scripts that use bridge.*
ensure your_scriptConfigure
Leave providers on "auto" in settings/bridge_resources.lua, or pin them. On start, the server console prints which provider each module resolved to. Details: Configuration.
Next steps
- Configuration: pin providers or leave them on auto-detect
- Supported: which frameworks, inventories, and other resources it works with
Writing your own resource, or moving one off community_bridge? That's all under For Developers.