QBCore
QBCore admin panel and staff tools
FiveStaff reads your QBCore server directly
Characters, bank balances, jobs and garages come off your own server as staff look at a player — not out of a copy FiveStaff keeps. Edits go back the same way, through qb-core while the character is loaded and through the database when they are not.
What FiveStaff sees on QBCore
- Characters by citizen id
- Money cash, bank and crypto
- Jobs job and grade
- Items qb-inventory, or yours
- Vehicles by plate
Framework data
What FiveStaff reads and changes on QBCore
What FiveStaff reads
- The loaded character, its citizen id and the names on it
- Cash, bank and crypto, as QBCore spells them
- The job and its grade
- Owned vehicles out of the player_vehicles table, by plate
- Items out of whichever inventory resource you run
What staff can change
- Set an item count, or remove an item
- Set a balance on any of the three accounts
- 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 QBCore 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 QBCore character with their cash, bank, crypto, job and garage. Staff set an item count, a balance or a job, and give, move, re-plate or remove a vehicle.
- 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 QBCore demo server. Every name, plate and licence in them is invented.
Player log
What the player log picks up on QBCore
Switch the player log on and it starts with what QBCore and your resources already announce. Nothing in your scripts has to change.
From QBCore
- 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 qb-inventory and its family
- Items added and removed, from qb-inventory’s own log lines
- Gives, drops and shop purchases told apart from the rest
- Moves into and out of stashes, boots and gloveboxes
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 QBCore
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, fines and vehicles
Recognised while they are running, so a payment reads as the bill or fine it was rather than as money spent.
-
qb-vehicleshopcars bought, financed or sold by a dealer -
qb-phoneinvoices paid and declined -
qb-policejobbills and 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 QBCore is different
The details a tool gets wrong when it treats every framework as the same one, and what FiveStaff does instead.
Your inventory resource is detected separately
QBCore ships with qb-inventory, and plenty of servers swap it for another — and the resource that owns the slots is the only thing that can change them while somebody is playing. FiveStaff looks for what is actually running — qb-inventory, ps-inventory, lj-inventory, qs-inventory, codem, origen, core_inventory, ox_inventory and the rest — and uses its exports and its column names. Setting fivestaff_inventory in your server.cfg names it when the guess is wrong.
An older qb-core still works
Newer builds export GetPlayer and GetPlayerByCitizenId directly; older ones only hand out the core object. FiveStaff tries the direct exports first and falls back to the core object, so a server that has not updated in a year is not left out.
An offline edit checks nobody has just joined
Before writing to the database for an offline character, FiveStaff asks QBCore whether that citizen id is loaded. A player who connected a moment ago is edited through the framework instead, rather than behind its back — otherwise the framework writes its own copy back over your change minutes later.
Install
Put it on your QBCore 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 qb-core and your inventory start.
-
4
Restart and check
Restart, or type ensure fivestaff in the server console. Within seconds the dashboard says Online. FiveStaff finds QBCore from qb-core, and your inventory from whichever inventory resource is started.
-
5
Connect your game database
Under Settings, Database, connect a read-only database user and choose the QBCore 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 "qbcore"
set fivestaff_inventory "qb-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 QBCore 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 QBCore 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
Does it work with qb-inventory, or with another inventory on QBCore?
Yes. FiveStaff looks for the inventory resource that is actually running — qb-inventory, ps-inventory, lj-inventory, qs-inventory, codem-inventory, core_inventory, ox_inventory and others — and edits items through its own exports. If yours is installed under another name, set fivestaff_inventory in server.cfg.
Can staff edit a character who is offline?
Yes. Money, items, jobs and vehicles are changed in your database through your game server, after FiveStaff has checked the character has not just logged in. Your game server has to be online for any edit.
What does the player log pick up without any changes?
Every money change QBCore reports, with its reason; every line your scripts already send to qb-log; joins, leaves and deaths; bills and fines from qb-phone and qb-policejob; items added, removed, given and moved from qb-inventory’s own log lines; and, if you run ox_inventory instead, where every item went.
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.
Does it run alongside txAdmin?
Yes. FiveStaff runs next to txAdmin, vMenu and EasyAdmin and switches none of them off, and you can import your existing bans from any of them.
Running something else?
Each framework has a page of its own, in its own words.
Point it at your QBCore 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