Qbox Framework Overview

Qbox is a hard fork of QBCore, rebuilt on the Overextended stack. It keeps QBCore’s data model and vocabulary — citizen ids, jobs, gangs, cash and bank accounts — and replaces the plumbing underneath.

Current state

qbx_core, not qbox_core

Every Qbox resource follows the same prefix: qbx_garages, qbx_vehiclekeys, qbx_management, qbx_policejob, and so on.

Built on the ox stack

This is the substantive difference from QBCore. Qbox depends on:

You are therefore learning two APIs, not one. The upside is that ox_lib and ox_inventory knowledge carries over to ox_core and ND Core.

Differences from QBCore

• Job and gang grades are numbers, not strings. This is the single most common conversion bug.
• Multicharacter, queue, multi-job and Discord rich presence are built into qbx_core rather than being separate resources, and are configured through convars in server.cfg.
• Multi-job and multi-gang write to a player_groups table. External multijob resources will corrupt data.
• Access is through exports, not a shared core object: exports.qbx_core:GetPlayer(source).
• MariaDB 10.9.0 is a hard floor — the core uses JSON_VALUE() (10.6.1+) and CREATE INDEX IF NOT EXISTS (10.9.0+).

Full structure reference →

Who it is for

Servers that want QBCore’s ecosystem and script compatibility but a more modern technical foundation, and teams that are already comfortable with ox_lib.

Most QBCore scripts port to Qbox with modest edits, and the Qbox team maintains a compatibility bridge for the common cases. Paid scripts increasingly ship a Qbox build alongside the QBCore one.

Documentation

• docs.qbox.re  — installation, resource reference, guides
• qbx_core exports 
• Converting from QBCore 
• FAQ 

Next steps

• Install Qbox
• Qbox structure
• Framework migration — coming from QBCore