Framework integration: QBCore, Qbox, ESX
Real FiveM servers usually run a framework. A framework answers the same boring questions for every script: who is this player, how much money do they have, what job are they on, what inventory do they carry. This lesson reads like a translation guide. Learn the idea once, then see how ESX, QBCore, and Qbox spell it. Then you build a script that actually acts on it: getting a player, changing their money, and reading their job, the same three moves in three dialects.
The frameworks at a glance
A framework gives your scripts a basic structure so you do not build everything from scratch. Each one has its own docs and its own way of spelling the same ideas. Bookmark the one your server actually runs.
A few facts to keep straight:
- Qbox calls itself a QBCore successor and keeps a QB compatibility bridge. ESX Legacy and QBCore stay separate ecosystems.
ox_libis optional utility code, not a requirement of ESX or QBCore.- The maintained 2026
ox_lib,oxmysql,ox_target, andox_inventoryrepos live under Community Ox. They are community resources, not Cfx.re platform features.
Keep reading the full lesson
Sign in to start, then unlock every step of this lesson and the full FiveM School with a membership.
- Build it
- How it works
- If something went wrong
- What you can do now
- Try it yourself
The remainder of Framework integration: QBCore, Qbox, ESX is available to FiveM School members.