Frameworks
How NX Creative scripts adapt to ESX, QBCore, and QBox.
Each NX Creative script ships with a framework bridge. The same script works on ESX, QBCore, and QBox. Detection happens at boot, and the appropriate adapter is loaded before the rest of the script runs.
How detection works
On resource start, the bridge checks which framework resource is currently running and uses the first one it finds:
| Framework | Detected resource |
|---|---|
| ESX Legacy | es_extended |
| QBCore | qb-core |
| QBox | qbx_core |
If no supported framework is running, the resource logs an error and stops. There is no standalone mode.
Most scripts expose a Config.Framework override for the rare case
where autodetection picks the wrong one. The accepted values are listed
in each script's own configuration page.
What the bridge covers
The bridge abstracts the three things that reliably differ between frameworks:
- Money. Wallet and bank balances, both reads and writes, through one set of functions.
- Jobs. Current job and grade, plus duty toggles where the framework supports them.
- Identity. Stable player identifiers and display names.
In script code the calls look the same on every framework. The per-script docs list the exact functions exposed.
What the bridge does not cover
The bridge is deliberately thin. It does not wrap inventories
(ox_inventory is a hard requirement), it does not abstract
ox_target, and it does not try to paper over gameplay differences
between frameworks. When a script needs something framework-specific
that the bridge cannot cover, the per-script docs say so.