ShiftWorks (vf_jobs)
Jobs should create rhythm, not chores.
A good civilian job gives players something to do between the chaos. A bad one turns into a grind loop everyone abandons by week two. ShiftWorks is built for configurable routes, zones, pay logic, and job pacing that fits your economy instead of flooding it.

The short answer
ShiftWorks is a FiveM jobs script for civilian work loops, route-based tasks, zone work, and configurable payouts. It is designed for RP servers that want jobs to support the economy without becoming inflation engines or grind systems players abandon. Payouts are config-driven so tuning your economy never requires touching code.
Trust receipts
01 / 08Performance · measured
Declared support — exact tested versions publish with the release QA matrix.
What you can read · escrow
Ships open
- full config surface (≤20 top-level keys)
- locales
- framework bridge glue
- public exports / API
Ships escrowed
- core logic (Cfx asset escrow)
Exact file-level manifest publishes with the release.
Support · SLA
- First response <24h
- S1 hotfix <12h
- free updates within major version
What it does
02 / 08Three complete reference jobs that double as templates: Delivery Driver (route), Sanitation (zone), Fishing (weighted item yield)
Payout formula lives in config: base + per-task + capped streak bonus, then a diminishing-returns curve past a daily task threshold, then a hard daily cap
Per-job cooldowns, duty statebags, live blips — and a fourth job is a config file, not a code change
The server generates every task list, validates every position and timing check, and is the only side that ever calls the money API
Event, statebag and export contract so vehicle-key scripts, HUDs and leaderboards hook in without touching escrowed code
See it run
03 / 08ShiftWorks (vf_jobs) demo loop — capture pending. Real client footage only; no mockups presented as gameplay.
ShiftWorks (vf_jobs) NUI detail — capture pending. Real client footage only; no mockups presented as gameplay.
Captures come from our own test servers, HUD-off, 1920×1080. We never present concept art or mockups as gameplay.
Compatibility
04 / 08Declared support — exact tested versions publish with the release QA matrix.
Every Vice Drip resource talks to your framework through one open bridge module in VF Core — Qbox/ox_lib first-class, ESX Legacy via bridge, QBCore compat — with no hard framework dependency baked into the product. Swap frameworks; keep your stack.
Requirements
05 / 08- Version
- 1.0.0
- fx_version
- cerulean
- Lua
- 5.4 (lua54 'yes')
- Minimum artifact
- not declared by the manifest
- This manifest names only vf_core, but the resource persists job stats and daily caps, so oxmysql has to be running. It is required transitively: vf_core's own manifest declares oxmysql, so the server starts it first either way. Install it.
Requirements are read from each resource's own fxmanifest.lua. We do not publish a minimum artifact build because none of our manifests declare one — run a current recommended artifact and Lua 5.4 will be available.
These come from the resource’s own manifest, not from a marketing sheet — the same file your server reads at start. If a dependency is missing, FiveM says so in the console and the resource does not start; nothing half-runs.
Changelog
06 / 08Straight answers
07 / 08Do I need to write code to add or tune jobs?
No — jobs are config-driven across three archetypes (route, zone, yield) with a deliberately small config surface (≤20 top-level keys). Your economy team tunes payouts, caps, and cooldowns without touching Lua.
How does VF Jobs prevent grinding from inflating my economy?
Diminishing-returns payout curves, per-job cooldowns, and daily caps are built in and configurable. Task completion is validated server-side, so payout events can't be spoofed from the client.
Which frameworks does it work with?
Qbox native, QBCore compat, ESX Legacy via bridge, and standalone — all through VF Core's open bridge, so switching frameworks later doesn't strand the product.
Get it
08 / 08ShiftWorks (vf_jobs)
Escrowed core, open config and bridge — exact manifest at release. First response <24h.
One community per purchase · free updates within the major version · License Terms · Refund Policy
Also in: Starter Bundle · Complete RP Server
Field guides: Qbox vs QBCore vs ESX Legacy in 2026 · How to Vet a FiveM Script Seller Before You Pay · What FiveM Scripts Actually Cost (2026 Price Survey, 13 Stores) · Framework Lock-In · FiveM EMS Script Buyer's Guide (2026) · The Complete FiveM Server Stack · How to Choose FiveM Scripts · FiveM Business Script Buyer's Guide (2026) · FiveM Jobs Script Buyer's Guide (2026) · FiveM Dispatch Script Buyer's Guide (2026) · How to Install a FiveM Script · Diagnosing FiveM Script Conflicts · How to Debug a FiveM Script · Why You Need a FiveM Staging Server (and How to Build One) · ox Stack Explained