lation jobs
lation jobs is an employment system for FiveM that creates or adopts the server's jobs and gangs in game, with hourly pay on duty, a boss menu and a job board.
lation jobs (lation_jobs) runs the jobs and gangs on your server from an in-game admin panel: create new ones, or adopt the ones your framework already has. Employees are paid per hour on duty out of the job's society account at your bank, bosses run their people from a boss menu that also answers the open events of qb-management, qbx_management and esx_society (on ESX it stands in for all of esx_society), and players hold several jobs and apply to new ones from the Work panel. There is no config file: every option lives in the database and is edited in game.
Works on Qbox, QBCore and ESX. Gangs are available on Qbox and QBCore; ESX has none.
Requirements
| Resource | Needed | What for |
|---|---|---|
ox_lib | Required | Callbacks, points, menus |
oxmysql | Required | The tables and the live configuration |
qbx_core, qb-core or es_extended | Required | The framework that holds who works where |
lation_interact, ox_target or qb-target | For places and the job center | Every prompt in the world. lation interact is picked first when it runs. |
| A bank (below) | For society payroll, bonuses and Finances | The job's money |
esx_addonaccount | On ESX | The money of jobs not managed here, and the last bank in the list below. Keep it. |
esx_datastore | For society garages on ESX | The garage that ESX job scripts park society vehicles in |
lation_ui | Optional | The panels follow your lation ui theme, and notifications use it |
| An inventory | For stashes | ox_inventory, qb-inventory, qs-inventory, ps-inventory, origen_inventory, codem-inventory, core_inventory, tgiann-inventory or jaksam_inventory |
| An appearance script | For lockers | illenium-appearance, fivem-appearance, qb-clothing, esx_skin or rcore_clothing |
| A keys script | For garages | qbx_vehiclekeys, qb-vehiclekeys, wasabi_carlock or mk_vehiclekeys; without one, a garage vehicle is handed out unlocked |
jg-advancedgarages | Optional | A garage place can be one of jg's garages |
fmsdk | Optional | Logging to fivemanage |
The bank
A job never holds money of its own. Its balance is a society account at the bank your server runs, and payroll, bonuses, deposits and withdrawals are moves in and out of it. lation jobs picks the first bank it finds running, in this order, unless Config > General > Bank names one:
| Bank | Resource | Frameworks |
|---|---|---|
| lation banking | lation_banking 1.2.0 or newer | All |
| Renewed-Banking | Renewed-Banking | All |
| qb-banking | qb-banking 2.0 or newer | Qbox, QBCore |
| qb-management | qb-management | Qbox, QBCore |
| okokBanking | okokBanking | All |
| wasabi_banking | wasabi_banking | All |
| fd_banking | fd_banking | All |
| tgg-banking | tgg-banking | All |
| snipe-banking | snipe-banking | All |
| ESX society accounts | esx_addonaccount | ESX |
Every bank gives a job its balance, payroll, bonuses, deposits and withdrawals. lation banking adds the rest: Finances shows the bank's own ledger, the bosses and the grades with money permissions are members of the job's account, so they reach it in the bank app whatever job they have active and Open in bank lands on it, and register places list at the bank's point of sale. See access for who becomes a member.
Where the bank lets lation jobs open an account (lation banking, Renewed-Banking, qb-banking and the ESX society accounts), a job has one as soon as it is created. Where it does not, the console names the account to add at the bank. lation banking opens society accounts only while its Config > Accounts > Society accounts is on (and Gang accounts too, for gangs); while it is off, the console says so once.
With no bank running, duty, places, applications and jobs paid by the server keep working. Society payroll, bonuses and the Finances tab wait until a bank runs, and the console says so once.
Install
Follow the install guide, then:
Keep the folder name lation_jobs. A renamed folder prints an error on start and again every 15 minutes.
Ensure it after your framework, ox_lib, oxmysql, your interaction system and your bank, and before the job scripts that open a boss menu. If you run lation ui, it goes first, above ox_lib, because the lation ox_lib fork looks for it when ox_lib starts.
ensure lation_ui # optional
ensure ox_lib
ensure oxmysql
ensure qbx_core # your framework
ensure lation_interact # or ox_target / qb-target
ensure lation_banking # your bank
ensure lation_jobs
ensure [jobs] # the job scripts that open a boss menuensure lation_ui # optional
ensure ox_lib
ensure oxmysql
ensure qb-core # your framework
ensure lation_interact # or ox_target / qb-target
ensure lation_banking # your bank
ensure lation_jobs
ensure [jobs] # the job scripts that open a boss menuensure lation_ui # optional
ensure ox_lib
ensure oxmysql
ensure es_extended # your framework
ensure esx_addonaccount # before your bank
ensure esx_datastore # for society garages
ensure lation_interact # or ox_target / qb-target
ensure lation_banking # your bank
ensure lation_jobs
ensure [jobs] # the job scripts that open a boss menuGive admins the panel. Add this to server.cfg:
add_ace group.admin lation_jobs.admin allowRemove the boss menu it replaces: qbx_management on Qbox, qb-management on QBCore. Delete or rename the folder. lation jobs answers their open events itself, so the job scripts on your server keep opening a boss menu without changes.
On ESX, delete the esx_society folder and set nothing: lation jobs stands in for all of it, with or without lation banking. Scripts that depend on it still start, register their society and find its money, staff and garage (what is answered). Keep esx_addonaccount, and esx_datastore if a job uses a society garage. Until you adopt a job in /jobadmin, its money keeps working and its boss menu says it isn't set up yet.
Restart the server.
If qb-management is still your bank (QBCore before qb-banking 2.0), keep it installed. Its boss menu and this one will then both answer the same opens, and the console warns about it two seconds after start.
There is no SQL to import. Every table (lation_jobs and the lation_jobs_* tables) is created on start, and schema updates run on start too.
You don't need to add managed jobs to your framework's job list either. lation jobs registers every job and gang it manages with the framework on each start: through the core's exports on Qbox and QBCore, and in the jobs and job_grades tables on ESX.
First start
On the first start the tables are created and every setting is seeded from its default, so /jobadmin works straight away. A job center stands at the default spot with a blip, and players can open the Work panel with /work or F6.
Run /jobadmin. The Jobs page lists the jobs managed here and, below them, the jobs and gangs your framework already has.
Adopt a framework job to manage it: its grades come across at their levels, the highest becomes the boss, everyone who holds it keeps their grade, and the framework's pay becomes the starting salary per hour. Or Create a new one.

In the job's editor, set a salary per hour on duty under Grades, hire the first boss under Staff (you can hire yourself), and put down an office and a duty point under Places.
Replace the framework paycheck is on by default: managed jobs are registered with no framework pay, so nobody is paid twice. The framework reads the pay when it learns a job, so this applies after a restart. On ESX 1.16 and newer, it reaches the players already on the server at once.
Admin panel
Create and adopt jobs, grades and pay, places, templates and the live config.
Boss menu
Staff, payroll, finances, applications, forms, notices and leave.
Players
The Work panel, duty, several jobs and the job board.
Configuration
Every live option and its default.
Developers
Exports, events, hooks and Script places.
Still stuck? Ask in our Discord: the people who write the scripts answer.
Last updated