Installation Guide

Follow these steps to install and configure cd_dispatch3d correctly.

1

1. Download

1. Download your resource from FiveM’s Portal.

2. Unzip the cd_dispatch3d.zip folder and place this folder in your server's resource folder.

2

2. Bridge

This resource is the core of all Codesign scripts. It handles framework connections, database setup, and error handling behind the scenes. When the bridge starts, it automatically detects and starts every compatible resource—including all Codesign scripts and any Codesign-compatible scripts you have installed.

1. Download cd_bridge from FiveM’s Portal.

2. Add cd_bridge to your server start config (server.cfg). Make sure cd_bridge is placed below your framework resource e.g., es_extended, not above it.

ensure cd_bridge

For more information on how to install the bridge, check out the full guide.

3

3. Config.lua

You must review all configurable options in [cd_dispatch3d/configs/config.lua] and adjust them to suit your server’s needs.

Be sure to read the commented help text at the end of each line — it explains the purpose of each configuration option.

The most important config options are in the Important category at the top of config.lua. All other settings are optional.

4

4. Configure Key Binds

Before Starting the Resource

Before launching this resource on your main or live server, we strongly recommend configuring your key binds, as this resource uses FiveM’s Key Mapping system.

Where Can I Configure My Key Binds?

You can configure all key binds directly in [cd_dispatch3d/configs/config.lua].

Why Is This Important?

Once a player joins your server with this resource running, you can no longer force key bind changes through the config file — players must adjust them manually through the in-game pause menu settings. However, any changes you make will still apply to new players who join afterward.

This system is more optimized and gives players the flexibility to customize their key binds for both keyboard and controller use. You can also review the Default Keybinds provided with this resource.

5

5. Add Dispatch Alerts

Compatible Code Snippets Provided by Codesign

On our Resource Integration page, we provide:

• Step-by-step photos

• Custom code snippets

• Exact line edits

These make it easy to set up full compatibility with ESX, QBCore, QBox and paid resources.

👉 Click here for ESX setup →

👉 Click here for QBCore setup →

👉 Click here for QBox setup →

🔗 View the full list of compatible scripts →

1. Find the old alert

• Red → Old dispatch alert

• Green → Old alert replaced with cd_dispatch3d

Not every resource will look the same, but the implementation concept remains identical.

2. Having trouble finding the old alert?

Trigger the Alert Where the Action Starts!

Dispatch alerts should be triggered where the event begins, for example:

• When the robbery starts

• When a crime is committed

❌ Bad Practice Triggering alerts inside an event that already broadcasts to all police:

• Causes duplicate notifications

• Creates duplicate blips

• Results in dispatch spam

✅ Good Practice Trigger the alert:

• At the source of the action

• Before any police broadcast or blip creation

• Let cd_dispatch3d handle visibility and syncing

3. Replace the old alert

client-side (recommended)

local data = exports['cd_dispatch3d']:GetPlayerInfo()
TriggerServerEvent('cd_dispatch:AddNotification', {
    job_table = {'police', 'ambulance'},
    coords    = data.coords,
    title     = '10-15 - Store Robbery',
    message   = 'A ' .. data.sex .. ' robbing a store at ' .. data.street,
    flash     = false,
    sound     = 1,
    blip = {
        sprite  = 431,
        scale   = 1.2,
        colour  = 3,
        flashes = false,
        text    = '911 - Store Robbery',
        time    = 5,
        radius  = 0,
    }
})

server-side

Player Info Export Reference

The following export is used in the example above:

This data structure can be customized in: integrations/client/client_exports.lua

local data = exports['cd_dispatch3d']:GetPlayerInfo()
data.ped       -- Player ped ID (e.g., 123456789)
data.coords    -- Player coordinates (vector3)
data.street_1  -- Street name (e.g., "Palomino Ave")
data.street_2  -- Area name (e.g., "Legion Square")
data.street    -- Full location (e.g., "Palomino Ave, Legion Square")
data.sex       -- Ped sex (e.g., "Male")

Dispatch Notification Variable Reference

Variable Name	Required	Description
job_table		List of jobs that will receive the dispatch alert.
coords		World coordinates where the alert occurred.
title		Title displayed in the dispatch UI, usually 10 codes.
message		Main description shown to responders.
flash		Whether the alert flashes on the UI. (true/false)
blip		Map blip configuration (see below).
blip.sprite		GTA blip sprite ID - More here.
blip.scale		Blip size on the map: 0.1-2.0.
blip.colour		Blip color ID - More here at bottom.
blip.flashes		Whether the blip flashes. (true/false)
blip.time		Time until blip fades and deletes (minutes)
blip.sound		Dispatch alert sound. Editable in BlipSound() (client/other/functions.lua). 1 = single alert, 2 = double alert, 3 = panic alert.
blip.radius		Randomize coords; use a radius blip. 0 disables it, 50–100 recommended.

6. Migrating Old Alerts To New Metho

6

Why is this required?

The resource name changed from cd_dispatch to cd_dispatch3d. Old GetPlayerInfo exports will no longer work unless updated.

Option 1 (Very Easy)

Download and start the provided compatibility resource. All incoming notifications will be fixed automatically—no code changes needed.

717B

cd_dispatch.zip

archive

Open

Option 2 (Recommended)

Search your server files for:

exports['cd_dispatch']:GetPlayerInfo()

Replace with:

exports['cd_dispatch3d']:GetPlayerInfo()

A video guide is provided for this method.