Jobs

Introduction

This tutorial turns Jobs into a clean, developer-friendly guide for QBCore/FiveM. You will follow a step-by-step flow, copy the relevant code patterns, and learn the “why” behind the setup.

Requirements

• QBCore installed and running on a dev server
• Basic Lua knowledge and comfort reading FiveM patterns
• A test workflow for iterating safely (dev server, not production)
• Optional: a code editor with Lua/FiveM helpers (VS Code recommended)

Step-by-Step Guide

Step 1: Job definitions

In this step, you will apply the job definitions concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 2: Assigning a job

In this step, you will apply the assigning a job concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 3: Going on duty

In this step, you will apply the going on duty concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 4: Verification

In this step, you will apply the verification concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 5: See also

In this step, you will apply the see also concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Step 6: Next steps

In this step, you will apply the next steps concept as a practical change: define the pieces, wire them together, then verify the behavior in your dev server.

Code Example

QBCore = exports['qb-core']:GetCoreObject()
 
QBCore.Shared.Jobs['tow'] = {
  label = 'Tow Truck',
  defaultDuty = true,
  grades = {
    ['0'] = { label = 'Rookie', salary = 50 },
    ['1'] = { label = 'Driver', salary = 75 }
  }
}

Tips & Best Practices

• Keep authority on the server: validate inputs before money/database operations.
• Start with one resource/module at a time, then refactor after you verify it works.
• Use callbacks for request/response flows and events for push/UX updates.
• When you run loops, avoid freezes: always yield with Wait() (client/server) and cache hot values.