Qbox
Qbox admin panel and staff tools
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.
Shown on our demo server, which runs QBCore
What FiveStaff sees on Qbox
- Characters from qbx_core
- Money cash, bank and crypto
- Jobs set through qbx_core
- Items ox_inventory’s fields
- Vehicles by plate
Framework data
What FiveStaff reads and changes on Qbox
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
- Move a vehicle to another character, or change its plate, keeping its mods and garage
Every one of these goes through the same pipeline as a ban: permission-checked and written to the audit log with what it was before. Item, money, job and vehicle edits can be put back in one press from the player’s profile.
What your staff can do
Run a Qbox server from one panel
Everything below works from the web panel, from Discord and, for staff who are playing, in game. Each power is its own permission, so you choose who gets which.
Characters and the economy
Every Qbox character with their balances, job and vehicles. Money and jobs are changed by asking qbx_core, online or not; items go through ox_inventory.
- Edit inventories
- Edit money
- Edit vehicles
- Edit jobs
Players and records
Everyone who has ever joined, and everything staff did about it.
Player log and alerts
What every player actually did, searchable, with alerts you write.
Live view and calls
Watch a player's game as it happens, and talk to them.
Reports
A player types /report in game and your team picks it up in seconds.
Bans and appeals
Bans that survive a new account, and appeals you can actually read.
Staff tools in game
Ban, warn and message from the game, with trust scores over every head.
Discord
Logs, slash commands and staff roles, in the Discord you already run.
In the panel
The screens your staff will use
Real screens from the panel, taken on our demo server, which runs QBCore. On yours, the accounts and jobs are Qbox’s own.
Player log
What the player log picks up on Qbox
qbx_core reports every balance change on the same event QBCore does, and ox_inventory says where every item went. FiveStaff listens to both, with no changes to your scripts.
From Qbox
- Every cash, bank and crypto change, with the reason the script gave
- Wages marked as wages, so a payday can be filtered out
- A balance set outright, recorded as the new balance rather than as money received
With ox_inventory
- Items dropped, picked up, given, and taken from another player
- Moves into and out of stashes, boots and gloveboxes, with the plate
- Shop purchases with the price, and crafts with what went into them
- Items created from nothing, with the script that made them
- Items used, and one player searching another
On every server
- Joins and leaves
- Deaths and kills, from the game itself: how, by whom and with what
- txAdmin’s scheduled restarts and shutdowns, and resources stopped or started by hand
- Every line your scripts already send to qb-log, kept word for word
- Your own events, with one line of Lua: exports.fivestaff:logEvent
-- one line, and it is searchable by item and amount
exports.fivestaff:logEvent(source, 'drugs.weed.sold', {
item = 'weed_brick', amount = 5, price = 2500
})The log is off until you switch it on, and a category you leave off costs your server nothing. The player log and alerts
Your resources
The scripts it works with on Qbox
A server picks its inventory, its ambulance job and its clothing separately from its framework. FiveStaff looks for what is actually running and works through it.
Inventories
Detected from what is running, and edited through that resource’s own exports. Where we could not read an inventory’s own code, the server console says so at start, so you can try one item edit on a test character first.
-
ox_inventory -
qb-inventory -
ps-inventory -
lj-inventory -
qs-inventory -
codem-inventory -
core_inventory -
origen_inventory -
tgiann-inventory -
ak47_qb_inventory -
Renewed-Inventory -
disc-inventory -
mf-inventory -
qb-inventory-old
Bills and fines
Recognised while it is running, so a payment reads as the bill or fine it was rather than as money spent.
-
qbx_policebills, fines and speed-camera fines
Heal and Revive
Revive goes through your ambulance script, so its own death screen and timers are cleared too, rather than a player being stood up the script still thinks is dead.
-
qbx_medical -
qb-ambulancejob -
ps-ambulancejob -
esx_ambulancejob -
wasabi_ambulance -
wasabi_ambulance_v2 -
tk_ambulancejob -
sky_ambulancejob -
brutal_ambulancejob -
osp_ambulance -
p_ambulancejob -
plt_ambulance_job
Reload appearance
Draws a player again from what their clothing script saved, for somebody invisible or stuck as the wrong model.
-
illenium-appearance -
qb-clothing
The small print
Where Qbox is different
The details a tool gets wrong when it treats every framework as the same one, and what FiveStaff does instead.
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. It matters most for jobs: Qbox keeps which jobs a character holds in a table of their own, and writes both places itself.
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.
Install
Put it on your Qbox server
One resource, a few lines in server.cfg, and no changes to your framework or your scripts.
-
1
Add your server
Sign in to the panel with Discord, press Add server, give it a name and choose a plan.
-
2
Download the resource
On your server’s dashboard, press Download the resource. The fivestaff folder inside already holds your server key, so there is nothing to fill in.
-
3
Add it to server.cfg
Upload the folder to your resources, keeping its name exactly fivestaff, and add the lines opposite anywhere after qbx_core and ox_inventory start.
-
4
Restart and check
Restart, or type ensure fivestaff in the server console. Within seconds the dashboard says Online. FiveStaff finds Qbox from qbx_core, even with the qb-core compatibility resource running beside it.
-
5
Connect your game database
Under Settings, Database, connect a read-only database user and choose the Qbox table layout, so staff see every character, offline ones included.
ensure fivestaff
# lets FiveStaff update itself, and staff start and stop resources
add_ace resource.fivestaff command.restart allow
add_ace resource.fivestaff command.start allow
add_ace resource.fivestaff command.stop allowOnly if it guessed wrong
Most servers never need these. They go above ensure fivestaff.
set fivestaff_framework "qbox"
set fivestaff_inventory "ox_inventory"When FiveStaff starts, the server console says which framework and inventory it is using. Try one edit on a test character before your staff use it on a player.
Why staff use it
Built for the people who keep a Qbox server fair
A record of every player, a log of every action, and powers handed out one at a time.
One record for every player
Whichever character somebody is on, their warnings, bans, reports and notes sit on one profile, and a ban checks every identifier they connect with — so a new account is not a fresh start on your Qbox server.
Nobody needs in-game admin
Your team is a list in the panel. Staff act from the panel, from Discord or in game with /staff, and you hand out no ace permissions to make that work.
Each power is its own permission
Edit money, Edit inventories, Edit vehicles and Edit jobs are separate permissions, so a trial moderator can read the player log without being able to set a balance.
Every change has a before
The audit log records who did what and what it was before, and item, money, job and vehicle edits can be put back in one press.
Questions people ask first
Qbox runs a qb-core compatibility resource. Will FiveStaff mistake it for QBCore?
No. When qbx_core is running, FiveStaff treats the server as Qbox even with the qb-core compatibility resource started beside it, and uses Qbox’s own exports.
Do item edits go through ox_inventory?
Yes: through ox_inventory’s exports while the player is on, and with ox_inventory’s field names in your database when they are not. If you have swapped it for another inventory FiveStaff knows, that one is used instead.
Which ox_inventory events end up in the player log?
Drops and pick-ups, items given to and taken from another player, moves into stashes, boots and gloveboxes, shop purchases with their price, crafts with their ingredients, items created from nothing with the script that made them, items used, and one player searching another.
Does an offline job change keep the character’s other jobs?
Yes. FiveStaff asks qbx_core to make the change, and Qbox loads the character, updates its job and the jobs it holds together, and saves it — as it would for one of its own commands.
Can an edit be undone?
Item, money, job and vehicle edits are written to the audit log with what they were before, and can be put back from the player’s profile under Framework, Edits. A vehicle that is put back keeps its plate but not its modifications.
Can staff change a character’s name?
Yes, while the character is not in game. That change is written straight to your database, so the database user FiveStaff connects with needs to be able to update the players table, and it cannot be undone in one press.
Running something else?
Each framework has a page of its own, in its own words.
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.
No card · 3 staff free · One resource