qbx_core (Qbox) for FiveM

At a glance

Figures read from the repository on 2026-09-22.

Why servers run it

• Real releases with version numbers, so you can tell which version a bug report is about.
• ox_lib and ox_inventory are dependencies rather than options, which removes a whole class of integration guesswork.
• The player object is close enough to QBCore's that most QBCore scripts run with small changes.
• TypeScript type definitions for the NUI side, and Lua type annotations for the exports.

Installing qbx_core (Qbox)

1. 1. Install the ox stack first

   oxmysql, ox_lib and ox_inventory are required, not optional. Start them before qbx_core.

2. 2. Use the recipe or the release

   Qbox ships a txAdmin recipe. If you are installing by hand, download the latest qbx_core release rather than cloning main.

3. 3. Import the SQL

   The release contains the schema. Qbox uses its own player table layout, so it is not a drop-in on top of an existing QBCore database without a migration.

4. 4. Start in order

   oxmysql, ox_lib, ox_inventory, qbx_core, then your own resources.

Working examples

local player = exports.qbx_core:GetPlayer(source)
if not player then return end

print(player.PlayerData.citizenid, player.PlayerData.job.name)

-- Qbox delegates inventory entirely to ox_inventory
exports.ox_inventory:AddItem(source, 'WEAPON_CUSTOMRIFLE', 1, {
    durability = 100,
    serial = exports.qbx_core:GetPlayer(source).PlayerData.citizenid,
})

What goes wrong

qbx_core (Qbox) — questions people ask

Runs alongside