Documentation
Integrate the script with your server and connect it to your existing systems using the available developer API and events.
Pays a player through the treasury system. This is how a job resource should hand out money — paying the player directly bypasses the treasury and leaves the stats empty.
exports['qs-job-management']:AddJobMoney(source, amount, jobName)Parameters
Parameter | Type | Description |
|---|---|---|
|
number |
Player server ID |
| number | Gross payment, before the cut |
| string | Job the payment belongs to |
The player receives amount - cut, where cut is the job's percent of the payment. The tax % is then burned out of that cut before the rest reaches the treasury balance.
Always guard the call so your resource still works when Job Management is not running:
if GetResourceState('qs-job-management') == 'started' then
exports['qs-job-management']:AddJobMoney(src, task.money, 'miner')
endFires an online player from a job.
exports['qs-job-management']:FirePlayerFromJob(source, jobName)Parameters
Parameter | Type | Description |
|---|---|---|
| number | Player server ID |
| string | Job to remove |
The removal is written to the HR log and the server log, exactly as if it had been done from the boss menu.
Fires a player by identifier, whether they are online or not.
exports['qs-job-management']:FirePlayerFromJobOffline(identifier, jobName)
Parameters
Parameter | Type | Description |
|---|---|---|
| string | Player identifier ( |
| string | Job to remove |
Opens the job menu, the same way /job does.
exports['qs-job-management']:requestJobs()Useful for binding the menu to your own HUD button, phone app or interaction menu.
The framework layer lives outside escrow in client/framework/*.lua and server/framework/*.lua. It resolves the player object, the player name and the identifier for your core.
Bridges ship for ESX, QBCore and QBox. To support a custom core, duplicate the closest bridge and implement the same functions.
The client bridge listens for your framework's job-update events — esx:setJob on ESX and QBCore:Client:OnJobUpdate on QBCore/QBox. Anything that changes a player's job through the core is picked up automatically and written to the multijob table.
If your core fires a different event, add a listener in the bridge and the rest of the resource works unchanged.
Only one table lives in the database:
Table | Holds |
|---|---|
| identifier, job, grade, badges |
Everything else is stored as JSON inside the resource, which makes it easy to read, back up or edit while the server is stopped.
File | Holds |
|---|---|
| The boss of each job |
| Hire/fire history per job |
| Treasury balances, cut %, tax and movement log |
| Boss locations added in game |
| Contracts, signed and pending |
|
|
| Per-grade permission flags |
| Earnings, hours and treasury contribution |
| Hire date, rank history, penalties, bonuses |
| Salary per rank |
| Interval and treasury flag per job |
| Server-wide event log |
Boss locations added from the panel override Config.BossLocations.
Edit these files only while the server is stopped — the resource holds them in memory and writes them back, so live edits will be overwritten.
Example: paying out at the end of a mining task.
if GetResourceState('qs-job-management') == 'started' then
exports['qs-job-management']:AddJobMoney(src, 850, 'miner')
else
-- Fallback for servers without Job Management
endexports['qs-job-management']:FirePlayerFromJob(targetSrc, 'police')Example: cleaning up jobs from a ban routine.
exports['qs-job-management']:FirePlayerFromJobOffline(identifier, 'police')exports['qs-job-management']:requestJobs()Register your job's table so the menu can read its progress:
Config.JobStatsTables = {
myjob = { db = "my_job_table", resource = "my-jobresource" },
}
Config.JobProgress = {
myjob = { baseExperience = 3500, growthFactor = 1.1 },
}The card only shows level and XP while that resource is started.