ESX
SupportedFramework
ESX is the least like the others, and that is where tools get it wrong
Its accounts are not QBCore’s accounts, its job is two columns rather than one blob, and an owned vehicle’s model is a hash. FiveStaff handles each of those as ESX actually keeps them instead of translating them into somebody else’s shape.
What FiveStaff reads
- The character out of the users table, by identifier
- Money, bank and black money — ESX’s three, not QBCore’s
- The job and the grade, from their two columns
- Owned vehicles out of the owned_vehicles table, by plate
- Items from whichever inventory resource is running
What staff can change
- Set an item count, or remove an item
- Set a balance on an account ESX actually has
- 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.
An account name it does not have is refused, not translated
QBCore’s cash and crypto do not exist here; ESX has money, bank and black money. A write naming an account this framework does not have comes back refused rather than being quietly mapped onto the nearest one, because the nearest one is somebody’s money.
Vehicle models are hashes, and a plate survives a revert
An owned vehicle’s row holds its properties with the model as a spawn hash, so FiveStaff hashes a model name it is given and reads one back as a hash. The plate round-trips exactly, which is what one-tap revert needs. Modifications and colours are not restored by a revert, and the panel says so where it offers one.
Point it at your ESX 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.