Installation Guide

Follow these steps to install and configure cd_dispatch3d correctly.

1

1. Codesign Bridge

Framework, Database, and Integration Handling

This resource requires cd_bridge to be installed and running before it can function.

cd_bridge is drag-and-drop and requires no configuration or file editing.

It handles framework connections, database setup, and error handling behind the scenes. When the bridge starts, it automatically detects and initializes all compatible resources — including all Codesign scripts and any Codesign-compatible scripts you have installed.

For installation instructions, see the 👉 full bridge setup guide →.

2

2. Download Resource

Download the Resource from FiveM’s Portal

1. 👉 Download cd_dispatch3d →

2. Unzip the downloaded file

3. In your server’s resources directory, create a folder named [codesign] if it does not already exist

4. Place cd_dispatch3d (and all other Codesign resources) inside the [codesign] folder

Example resources folder with a [codesign] directory

3

3. Configure Resource

Review and Adjust config.lua Options

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

Configure Before Starting the Resource

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.

Keybind settings located in the pause menu

5

5. Replace Old Dispatch Alerts

ℹ️ Notice

Not all dispatch alerts need to be replaced.

cd_dispatch3d now supports the following without any changes:

• cd_dispatch (classic)

• ps-dispatch

• lb-tablet

• redutzu-mdt

• Default ESX police alerts

• Default QBCore police alerts

Only replace alerts if you are using a custom or unsupported police alert system.

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.

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

Once you’ve found the old dispatch alert to replace, continue with Step 6.

Continue with Step 6.

Once you’ve found the old dispatch alert to replace, continue with Step 6.

6

6. Add New Dispatch Alerts

Compatible Integrations by Codesign

On our Resource Integration page, you can find a full list of pre-integrated and compatible scripts that work seamlessly with cd_dispatch3d and MDT integrations.

🔗 View the full list of compatible scripts →

client-side (recommended)

local data = exports['cd_dispatch3d']:GetPlayerInfo()
TriggerServerEvent('cd_dispatch:AddNotification', {
    job_table = { 'police', 'sheriff' },
    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 Alert Variable Reference

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