Documentation
Learn how the script works, explore its main features, and discover how to configure and use everything with ease.
Quasar Job Management lets players hold several jobs at once and switch between them from a menu, gives bosses a panel to run their business, and gives admins the same panel for every job on the server.
Everything is driven by Config.Interactions — set any entry to nil to disable that trigger.
Menu | Default | Who |
|---|---|---|
Job menu | , key (F5) |
/job166Every player |
Admin panel |
| ESX |
Boss menu | Walk into the job's boss location, press | The boss, plus any grade with |
Boss menu (command/key) |
| The boss only — |
Note the naming:
/bossis the admin panel. The boss menu has no command by default, because it is meant to be used at the job's location.
The boss zone only appears while the matching job is the player's active job, and the blip only draws for players allowed to open that menu.
/job lists every job the player holds:
Grade label, treasury cut, and — for Quasar job resources — level and XP progress
Switch the active job, or toggle duty
Personal stats: hours worked, earnings, treasury contributed
Job chat, shared by everyone in that job
Resign, which deletes the row and any contract tied to it
Config.Position ("right" / "left") sets which side of the screen the menu opens on.
Off duty means unemployed. Toggling duty sets the player's framework job to unemployed grade 0 and clears the duty timer; toggling it back restores the job and grade.
Any script that reads the player's job will see unemployed while they are off duty.
Level and XP are read from the job resource's own table, and only while that resource is started.
Config.JobStatsTables = {
miner = { db = "qs_miner", resource = "qs-minerjob" },
}
Config.JobProgress = { -- xpForLevel(n) = baseExperience * growthFactor ^ (n - 1)
miner = { baseExperience = 3500, growthFactor = 1.1 },
}You never register jobs by hand. The resource listens for your framework's job events, so whatever gives the player a job — a job center, an admin command, another script — is picked up and stored. The job the player is wearing at login is registered the same way.
Config.MaxJobs caps how many jobs a player may hold at once. A player who receives a job beyond the limit is sent back to unemployed and notified.
Config.UseByLicense narrows this further: licenses listed in Config.AllowedLicenses keep the full Config.MaxJobs, everyone else is capped at Config.NoLicenseUserMaxJobs.
Config.BlackListedJobs hides a job from the menu (prisoner by default). It is still stored — just not shown.
Section | What it does |
|---|---|
Employees | Grade, badges, penalties, bonuses, fire, per-employee report |
Hire | Invite an online player, or send a contract |
Ranks | Add, edit and delete grades, and set per-grade permissions |
Treasury | Balance, log, pay an employee, set the cut % |
Salaries | Interval per job, amount per rank, paid from cash or the treasury |
Stats | Earnings, hours worked and treasury contribution |
HR Log | Hire/fire history, last 300 entries per job |
Contracts | List, view and rescind signed contracts |
Announcement | Message pushed to every online employee of the job |
The admin panel has these same tabs for every job, plus Players, Manage Jobs and the server-wide Logs.
A boss is assigned from the admin panel (Boss tab), one per job. Bosses bypass every permission check for their own job, and can resign from the boss menu.
Ranks carry ten flags:
canOpenMenu · canHire · canFire · canManageTreasury · canChangePercent · canChangeGrade · canViewReports · canApplyPenalty · canMakeAnnouncement · canManageRanks
canOpenMenu is the gate — without it, a grade never sees the boss zone. The boss and admins always have all ten.
Each job runs in one of two modes, set per job from the panel:
Mode | How it works |
|---|---|
| The boss picks an online player, who gets an invite to accept or decline |
| The boss writes a contract (role, grade, terms). The employee opens the document, signs it with the signature pad, and only then gets the job |
Rescinding a contract fires the employee and deletes it.
Either way, the target must be under Config.MaxJobs or the hire is refused.
Every job has a balance, a cut % and an optional tax.
Job resources must pay through the export instead of handing money out directly — that is what fills the treasury and feeds the stats:
if GetResourceState('qs-job-management') == 'started' then
exports['qs-job-management']:AddJobMoney(src, task.money, 'miner')
endThe player receives amount - cut, where cut is the job's percent of the payment. The tax % is then burned out of that cut before it reaches the balance — money removed from the economy, not income.
Admins can inject funds from the panel, and bosses distribute to online employees.
Per job: an interval in minutes and, per rank, an amount. A thread wakes every minute and pays every online employee whose rank has a salary above zero.
fromTreasury decides where the money comes from:
On — the payment is debited from the job's treasury, and skipped entirely when the balance cannot cover it.
Off — it is created out of nothing, like a classic paycheck.
Config.DiscordWebhook sends an embed for hires, fires, grade changes, penalties, bonuses, treasury movements, boss changes, announcements and job create/delete. Leave it empty to disable.
The same events are written to the server log (last 2000 entries, readable from the admin panel's Logs tab) and, for hire/fire only, to the HR log per job.
Everything under these paths is outside escrow and safe to edit:
Path | What it holds |
|---|---|
| All settings, plus the |
| Locale loader — missing keys fall back to English |
| 19 languages |
| Framework bridge (player object, name, identifier) |
To point notifications at your own system, fill in SendTextMessage(msg, type) in config/config.lua:
function SendTextMessage(msg, type)
exports["Notify"]:Alert(msg, type)
end