Requirements · General docs

Almost every resource documented here builds on the same small set of dependencies. Install these once and most scripts will drop straight in.

Each resource's own installation page lists what it specifically needs; this page covers the common ground.

The common dependencies

Resource	Purpose	Where
`ox_lib`	UI, callbacks, locales, keybinds	https://github.com/overextended/ox_lib
`oxmysql`	Database access	https://github.com/overextended/oxmysql

Both are free, actively maintained, and required by most of what I publish.

Framework

Pick one. Resources here support both, and detect which is running automatically:

qbx_core (Qbox)
qb-core (QBCore)

Inventory

Pick one. This is chosen independently of your framework — running QBCore with ox_inventory is a common and fully supported combination:

ox_inventory
qb-inventory

Start order

This is the single most common cause of a resource failing to boot.

Resources detect their framework and inventory at start by checking which resources are already started — not which are listed in your config. Anything a script depends on has to appear above it in server.cfg:

ensure ox_lib
ensure oxmysql
ensure qbx_core        # or qb-core
ensure ox_inventory    # or qb-inventory

ensure dd-cards        # resources go last

Warning

If a resource starts before your framework, it will error out with something like no supported framework found even though the framework is very much installed. Move the ensure line down and restart.

Locales

Resources here use ox_lib's locale system and follow its convar. Set it if you are not running English:

setr ox_locale "en"

Translation files ship as JSON under each resource's locales/ directory.

Optional integrations

These are detected if present and simply skipped if not:

Category	Supported
Targeting	`ox_target`, `qb-target` — otherwise a built-in walk-up prompt is used
Menus	`ox_lib` context menu, `qb-menu`
Phones	`lb-phone`, `npwd`, `qb-phone` — otherwise on-screen notifications

Support varies by resource; check the relevant compatibility page.

Databases

Resources that store data create their own tables on first start, and ship the SQL under install/sql/ if you would rather import it by hand. Every shipped statement is CREATE TABLE IF NOT EXISTS, so importing twice is always safe.