The resource folder was renamed. It checks its own name on start and stops everything if it does not match. Rename the folder back to qs-job-management — with the same name in server.cfg — and restart the server.

The admin check failed. On ESX the player's group must be admin or superadmin; on QBCore and Qbox the core must allow them the admin permission. Installation shows both, and how to change the check in PlayerIsAdmin.

Remember that /boss is the admin panel. A job's boss opens the boss menu at the boss zone, not with this command.

The table could not be created or checked. Make sure oxmysql starts before Job Management and connects — its own console lines say so — and that the database user may create and alter tables. The error after the colon is MySQL's own message. As a fallback, import qs-job-management.sql by hand.

Job Management could not reach your framework within fifteen seconds of starting. The framework must start before it in server.cfg. On Qbox, the qb-core bridge must also be enabled — qbx:enablebridge must not be false.

Config.Locale names a file that does not exist — the warning lists the ones that do — or the file has a JSON mistake, usually a missing comma or quote after an edit. Fix the code or the file and restart. Until then everything shows in English.

SendTextMessage in config/config.lua ships with every line commented out, so the maximum-jobs warning, the license refusal, quit notices and treasury payments are silent. Point it at a notification system — Integrations has ready-made examples.

The player already holds Config.MaxJobs jobs (5 by default), so the new job was not stored and they were set back to unemployed. They need to quit a job from the menu first — or raise the limit.

Config.UseByLicense is on and the player's license is not in Config.AllowedLicenses. Add the full license:… identifier, or turn the restriction off.

Either it is in Config.BlackListedJobs — still stored, never shown — or it was never stored because the player was at the job limit when they received it. Jobs are added when the framework sets them; give the job again once there is room.

The job is not in Config.Jobs. It still works; add it there with a label and an icon to give it a proper card, badges and a place in the admin panel.

Expected: the player is off shift. End shift sets the framework job to unemployed, so dispatch, garages and shops stop treating them as on duty. Start shift puts the job back.

Levels are read only from the Quasar job resources listed in Integrations, and only while that resource is started. Check that it is running, that the job name matches the one it gives players, and that the player has worked it at least once — until then there is no row to read. If the bar looks wrong, align Config.JobProgress with the job script's own curve.

All of these must be true:

• The job has a zone — in Config.BossLocations or set in the admin panel's Location.

• That job is the player's active job — not just on their list.

• The player is the job's boss, an admin, or holds a rank with Open Menu.

• Config.BossLocations is a table — set to nil, it switches the boss menu off for every job.

bossCommand and bossKey are off by default, and when set they only answer to the job's designated boss, for their active job. Ranks with Open Menu use the boss zone.

The treasury, salaries, HR log, statistics, the rank editor, contracts, badges and announcements only answer to the job's boss — and to admins from the admin panel. A rank holding Treasury, Change %, Manage Ranks or Announce sees the button, but the section stays empty. Hire, Fire, Change Grade, employee reports and penalties work for any rank that holds them.

The Jobs tab lists Config.Jobs. Add the new job there with its label and icon, and restart the resource.

On ESX they are written to jobs and job_grades. On QBCore and Qbox they only live in the running core. Copy them into qb-core/shared/jobs.lua or Qbox's shared jobs file to keep them.

It comes from Config.BossLocations — the panel marks it Set in config file. Delete only removes zones placed in game. Remove or edit the entry in the config, or place a new zone in the panel, which overrides it.

The server ID must belong to an online player other than you. The offer is refused when that player already has the job, and accepting it is refused when they are at Config.MaxJobs. Offers expire after 30 seconds (60 from an admin).

The job resource pays its workers directly instead of through AddJobMoney, or the job's cut is 0%. Route the payout through the export:

exports['qs-job-management']:AddJobMoney(source, amount, 'miner')

The same export feeds the statistics, so direct payments leave both empty. Remember the default cut is 1%: small payouts may round down to nothing.

Check all of these:

• The job's Salary Settings in Treasury have been saved at least once — until then the job has no pay schedule.

• The employee's rank has an amount above zero in Ranks.

• The interval has passed since the last payment, and the employee is online at that moment.

• With From treasury balance on, the treasury can cover the amount.

The framework's own paycheck still pays that grade — job_grades.salary on ESX, payment on QBCore and Qbox — on top of the rank salary. Save the rank once in Ranks: that sets its framework salary to 0.

The treasury holds less than the amount, or the employee went offline — payments only reach online players. Nothing was taken from the treasury.

Hours are counted from Start shift to End shift or disconnect. A player who never uses the shift button in the job menu has no shift on record.

The resource holds bosses.json, hrlog.json and the data/ files in memory and writes them back on the next change. Edit them only while the server is stopped.

They are stored inside the resource folder, so replacing the folder replaced them. Restore bosses.json, hrlog.json and data/ from your backup while the server is stopped. The job lists themselves are in the database and are never touched.

The data files carry the state of the server they came from. Reset them as shown in Installation, with the server stopped.

Expected. The chat keeps its last 100 messages in memory only, and a restart of the resource clears them.

The resource folder was renamed. It checks its own name on start and stops everything if it does not match. Rename the folder back to qs-job-management — with the same name in server.cfg — and restart the server.

The admin check failed. On ESX the player's group must be admin or superadmin; on QBCore and Qbox the core must allow them the admin permission. Installation shows both, and how to change the check in PlayerIsAdmin.

Remember that /boss is the admin panel. A job's boss opens the boss menu at the boss zone, not with this command.

The table could not be created or checked. Make sure oxmysql starts before Job Management and connects — its own console lines say so — and that the database user may create and alter tables. The error after the colon is MySQL's own message. As a fallback, import qs-job-management.sql by hand.

Job Management could not reach your framework within fifteen seconds of starting. The framework must start before it in server.cfg. On Qbox, the qb-core bridge must also be enabled — qbx:enablebridge must not be false.

Config.Locale names a file that does not exist — the warning lists the ones that do — or the file has a JSON mistake, usually a missing comma or quote after an edit. Fix the code or the file and restart. Until then everything shows in English.

SendTextMessage in config/config.lua ships with every line commented out, so the maximum-jobs warning, the license refusal, quit notices and treasury payments are silent. Point it at a notification system — Integrations has ready-made examples.

The player already holds Config.MaxJobs jobs (5 by default), so the new job was not stored and they were set back to unemployed. They need to quit a job from the menu first — or raise the limit.

Config.UseByLicense is on and the player's license is not in Config.AllowedLicenses. Add the full license:… identifier, or turn the restriction off.

Either it is in Config.BlackListedJobs — still stored, never shown — or it was never stored because the player was at the job limit when they received it. Jobs are added when the framework sets them; give the job again once there is room.

The job is not in Config.Jobs. It still works; add it there with a label and an icon to give it a proper card, badges and a place in the admin panel.

Expected: the player is off shift. End shift sets the framework job to unemployed, so dispatch, garages and shops stop treating them as on duty. Start shift puts the job back.

Levels are read only from the Quasar job resources listed in Integrations, and only while that resource is started. Check that it is running, that the job name matches the one it gives players, and that the player has worked it at least once — until then there is no row to read. If the bar looks wrong, align Config.JobProgress with the job script's own curve.

All of these must be true:

• The job has a zone — in Config.BossLocations or set in the admin panel's Location.

• That job is the player's active job — not just on their list.

• The player is the job's boss, an admin, or holds a rank with Open Menu.

• Config.BossLocations is a table — set to nil, it switches the boss menu off for every job.

bossCommand and bossKey are off by default, and when set they only answer to the job's designated boss, for their active job. Ranks with Open Menu use the boss zone.

The treasury, salaries, HR log, statistics, the rank editor, contracts, badges and announcements only answer to the job's boss — and to admins from the admin panel. A rank holding Treasury, Change %, Manage Ranks or Announce sees the button, but the section stays empty. Hire, Fire, Change Grade, employee reports and penalties work for any rank that holds them.

The Jobs tab lists Config.Jobs. Add the new job there with its label and icon, and restart the resource.

On ESX they are written to jobs and job_grades. On QBCore and Qbox they only live in the running core. Copy them into qb-core/shared/jobs.lua or Qbox's shared jobs file to keep them.

It comes from Config.BossLocations — the panel marks it Set in config file. Delete only removes zones placed in game. Remove or edit the entry in the config, or place a new zone in the panel, which overrides it.

The server ID must belong to an online player other than you. The offer is refused when that player already has the job, and accepting it is refused when they are at Config.MaxJobs. Offers expire after 30 seconds (60 from an admin).

The job resource pays its workers directly instead of through AddJobMoney, or the job's cut is 0%. Route the payout through the export:

exports['qs-job-management']:AddJobMoney(source, amount, 'miner')

The same export feeds the statistics, so direct payments leave both empty. Remember the default cut is 1%: small payouts may round down to nothing.

Check all of these:

• The job's Salary Settings in Treasury have been saved at least once — until then the job has no pay schedule.

• The employee's rank has an amount above zero in Ranks.

• The interval has passed since the last payment, and the employee is online at that moment.

• With From treasury balance on, the treasury can cover the amount.

The framework's own paycheck still pays that grade — job_grades.salary on ESX, payment on QBCore and Qbox — on top of the rank salary. Save the rank once in Ranks: that sets its framework salary to 0.

The treasury holds less than the amount, or the employee went offline — payments only reach online players. Nothing was taken from the treasury.

Hours are counted from Start shift to End shift or disconnect. A player who never uses the shift button in the job menu has no shift on record.

The resource holds bosses.json, hrlog.json and the data/ files in memory and writes them back on the next change. Edit them only while the server is stopped.

They are stored inside the resource folder, so replacing the folder replaced them. Restore bosses.json, hrlog.json and data/ from your backup while the server is stopped. The job lists themselves are in the database and are never touched.

The data files carry the state of the server they came from. Reset them as shown in Installation, with the server stopped.

Expected. The chat keeps its last 100 messages in memory only, and a restart of the resource clears them.