Frameworks and the core stack
In short
A framework gives every script the same idea of a character, a job, money and an inventory. Choose one before you buy scripts — most resources are written for a specific framework.
| Framework | Style | Notes |
|---|---|---|
| ESX Legacy | Long-running, very large catalogue | es_extended; works with ox_inventory |
| QBCore | Popular, large script market | qb-core; qb-inventory by default |
| Qbox | QBCore-compatible on a modern ox stack | qbx_core; ox_inventory and ox_lib built in |
| ox_core | Minimal and developer-focused | By Overextended; ox_inventory native |
| Standalone / vMenu | Freeroam, racing, drift | No character or economy system |
The Overextended stack — oxmysql, ox_lib, ox_inventory, ox_target, ox_doorlock — is shared across frameworks; ox_inventory officially supports ox_core, ESX, Qbox and ND_Core. A full comparison: ESX vs QBCore vs Qbox.
- Start from the framework’s txAdmin recipe, then add scripts one at a time.
- Buy scripts that support your framework (or bridge several) and read their dependency list first.
- Never run two frameworks on one server.
- Keep a list of every resource, its version and where it came from.