"Duty" is a concept every roleplay server relies on, but new server owners often don't fully understand what it does or why it matters. Here's how duty systems work and why they're essential — especially for service jobs.
What "duty" means
A duty system tracks whether a player is actively working their job or not. A police officer can be on duty (actively policing, receiving pay, using police powers) or off duty (a regular civilian who happens to have the police job). The duty toggle is the switch between these states.
Why duty matters
Duty solves several important problems:
- Roleplay clarity. An off-duty cop shouldn't be arresting people. Duty makes "am I working right now?" explicit.
- Payment control. Players should earn their job salary while working, not permanently. Duty gates paycheck.
- Power gating. Police/EMS abilities should only apply while on duty. This prevents an off-duty officer from using police powers in casual play.
- Server realism. Duty counts show how many officers/medics are actually available, which matters for balance and dispatch.
- Preventing abuse. Combined with server-side validation, duty stops players from flashing job powers whenever they like.
On/off duty toggling
At its simplest, duty is a toggle — the player switches on or off duty, usually from a job menu or multijob interface. While on duty they get their job's pay, powers, and often uniform/equipment; off duty they don't.
Station duty points
More grounded servers use station duty points — the player must physically go to their station (police department, hospital) to toggle duty, rather than switching anywhere. This is especially important for police and EMS because:
- It stops random players going "on duty" in the middle of the street
- It reinforces that starting work means going to your workplace
- It keeps the roleplay believable
Station-locked duty is a hallmark of well-run service jobs.
How duty ties into pay
Most frameworks pay job salaries on a timer *while on duty*. So duty directly controls the economy — players earn by actually working. This is why duty and job economy balance are connected: your salary values assume players earn them while on duty, not passively.
Duty across frameworks
QBCore and ESX handle duty somewhat differently (QBCore has its own duty concept; ESX setups often use esx_duty-style approaches). A good duty/multijob system supports the framework you run — or both. The important thing is that duty is enforced server-side so it can't be spoofed.
Duty and multijob together
Duty and multijob go hand in hand — players hold multiple jobs and toggle duty on whichever they're currently working. A quality multijob system builds duty in cleanly, including station-locked duty for service jobs.
Duty done right
At Viper Development, our FiveM multijob script includes built-in duty toggling with QBCore duty support and an esx_duty-style approach, plus station-locked duty for jobs like police and EMS — all validated server-side. It's duty handled properly.