Qbox
SupportedFramework
Qbox is not QBCore with a new name, and FiveStaff does not treat it as one
It keeps QBCore’s database shape and almost none of its export surface. FiveStaff talks to qbx_core directly, reads items with ox_inventory’s field names rather than qb-inventory’s, and lets the core do the loading on an offline write.
What FiveStaff reads
- The character from qbx_core’s GetPlayer export, flat rather than off a core object
- Cash, bank and crypto
- The job and its grade
- Owned vehicles by plate
- Items with ox_inventory’s count and metadata, not qb-inventory’s amount and info
What staff can change
- Set an item count, or remove an item
- Set a balance
- Set a job and a grade
- Give or take an owned vehicle
Every one of these goes through the same pipeline as a ban: permission-checked, written to the audit log with what it was before, and revertible in one tap.
Money and jobs go through the core even when nobody is online
Qbox’s SetMoney and SetJob take either a source or a citizen id, and load, change and save the character themselves. FiveStaff uses that rather than writing the column, so the framework’s own rules — and its own logging — still run on a change a staff member made at four in the morning.
The inventory is still asked about
Qbox expects ox_inventory and refuses to run with qb-inventory, but FiveStaff still detects what is there rather than assuming, because a server that has swapped it is a server whose item edits would otherwise go to the wrong place.
Point it at your Qbox server
Sign in with Discord, add your server, and drop one resource into it. Free for 3 staff, and nothing to cancel if it is not for you.