Configuration

Page dedicated to how to configure our Police MDT [V2]

Languages

The language of the tablet is set inside Config.NUI.

• en-US: English

• fr-FR: French

• pl-PL: Polish

• de-DE: German

• es-ES: Spanish

• pt-PT: Portuguese

• ja-JP: Japanese

• it-IT: Italian

• ko-KR: Korean

Config.NUI = {
    defaultLangCode = "en-US",
    -- Languages offered in the tablet's own language switcher.
    -- Remove entries you do not want players to be able to pick.
    langs = {
        { code = "en-US", name = "English", iconUrl = "https://.../gb.webp" },
        { code = "pl-PL", name = "Polski",  iconUrl = "https://.../pl.webp" },
    }
}

Commands & Keybinds

General

• /qf_mdt_police_v2 (DELETE): Toggle the MDT Dashboard.

• /qf_mdt_police_v2badge (B): Show/Hide Officer Badge. /badge works as a short alias.

• /bodycam: Toggle the bodycam overlay. /showbodycam and /hidebodycam force one state.

Dispatch

• /qf_mdt_police_v2_fastgps (E): Set the GPS to the latest dispatch alert.

• /qf_mdt_police_v2_dispatch (HOME): Open the MDT straight on the dispatch page.

Camera Mode

• /qf_mdt_police_v2_capturephoto (ENTER): Start capturing a photo.

• /qf_mdt_police_v2_blocknuifocus (L-ALT): Block the NUI focus.

• /qf_mdt_police_v2_cameratakephoto (SPACE): Take the photo.

• /qf_mdt_police_v2_cameratogglefocus (L-ALT): Toggle mouse focus.

• /qf_mdt_police_v2_cameratoggleflashlight (F): Toggle camera flashlight.

• /qf_mdt_police_v2_cameratoggleside (R): Switch between Front/Back camera.

Radar

• /qf_mdt_police_v2radartoggle (U): Toggle the entire Radar system.

• Front Radar Settings

  • /qf_mdt_police_v2radarshowfront (F5): Show Front Radar.

  • /qf_mdt_police_v2radarhidefront (F6): Hide Front Radar

  • /qf_mdt_police_v2radartoggleinteractfront (PGUP): Lock/Unlock Front Radar target

• Back Radar Settings

  • /qf_mdt_police_v2radarshowback (F7): Show Back Radar.

  • /qf_mdt_police_v2radarhideback (F8): Hide Back Radar

  • /qf_mdt_police_v2radartoggleinteractback (PGDN): Lock/Unlock Back Radar target

Note: Both the keys and the command names come from Config.ToggleMDT, Config.Camera, Config.Badge, Config.Radar and Config.Dispatch in config/config.lua — the names above are the defaults.

Running several tablets side by side (Config.Base)

Every module stores its data in its own MySQL table, named after the resource (qf_mdt_police_v2_*). Config.Base lets you point any module at a different table, which is how you run more than one tablet at the same time — e.g. qf_mdt_police_v2 plus a sheriff copy — each with its own events, exports and faction logic, while sharing selected data.

-- Make the sheriff tablet share the police fines, tags, records, warrants,
-- cases and evidences, but keep its own officers, announcements and radio codes.
Config.Base = {
    fines            = "qf_mdt_police_v2_fines",
    tags             = "qf_mdt_police_v2_tags",
    entityNotes      = "qf_mdt_police_v2_entity_notes",
    mugshots         = "qf_mdt_police_v2_mugshots",
    warrants         = "qf_mdt_police_v2_warrants",
    warrantOfficers  = "qf_mdt_police_v2_warrant_officers",
    warrantCitizens  = "qf_mdt_police_v2_warrant_citizens",
    cases            = "qf_mdt_police_v2_cases",
    caseOfficers     = "qf_mdt_police_v2_case_officers",
    caseCitizens     = "qf_mdt_police_v2_case_citizens",
    evidences        = "qf_mdt_police_v2_evidences",
    evidenceOfficers = "qf_mdt_police_v2_evidence_officers",
    evidenceCitizens = "qf_mdt_police_v2_evidence_citizens",
}

Anything you leave out keeps its own default table, so that data stays private to the faction. When a table is shared, every tablet pointing at it must use the same value, and related tables have to be shared together:

• warrants ↔ warrantOfficers + warrantCitizens

• cases ↔ caseOfficers + caseCitizens

• evidences ↔ evidenceOfficers + evidenceCitizens

1. Configuring Ranks (Grades)

In config.lua, the Config.Grades table controls the hierarchy visible in the MDT. This must match your framework's job grades (ESX/QBCore/QBOX) to ensure correct label display.

-- config.lua
Config.Grades = {    
    {id = 0, name = "Cadet"},     
    {id = 1, name = "Officer I"},    
    {id = 2, name = "Officer II"},    
    {id = 3, name = "Sergeant"},    
    {id = 4, name = "Lieutenant"},    
    {id = 5, name = "Chief"}
}
-- Ensure 'id' corresponds to the grade integer in your database.

2. Customizing Fines

You can add new categories and fines in Config.FineList.

-- config.lua
Config.FineList = {    
    {        
        id = "1", -- Unique Category ID        
        label = "Traffic Laws",        
        items = {            
            {                    
                id = "1",                 
                label = "Speeding (> 50 km/h)",                 
                fine = 500,                 
                jail = 0 -- Optional: Jail time in months/minutes            
            },            
            {                
                id = "2",                 
                label = "Reckless Driving",                 
                fine = 1000,                 
                jail = 5            
            }        
        }    
    }
}

3. Dispatch Colors & Vehicles

The dispatch system uses specific color codes for vehicles. These are defined in Config.Dispatch.Colors. When creating custom alerts, you can use these or standard RGB values.

---

Server-side Exports

Use these exports in your other resources to interact with the MDT backend.

AddLog

Adds an entry to the Audit Log. Useful for tracking evidence locker access, armory usage, or boss menu actions.

Syntax:

exports.qf_mdt_police_v2:AddLog(source, tag, text, color, fields, args)

Parameters:

Parameter	Type	Description
source	number	Player Source ID.
tag	string	Category tag (e.g., 'armory', 'evidence', 'boss').
text	string	Log message.
color	string	Color theme ('blue', 'red', 'green', 'orange').
fields	table	(Optional) Key-value pairs for extra metadata.
args	table	(Optional) Arguments for translation if text is a locale key.

Example (Armory Usage):

-- Triggered when a player withdraws a weapon
local weaponName = "WEAPON_PISTOL"
local ammoCount = 50

exports.qf_mdt_police_v2:AddLog(    
    source,     
    "armory",     
    "Withdrew weapon from armory",     
    "red",     
    {         
        weapon = weaponName,         
        ammo = ammoCount,        
        serialNumber = "WX-12345"     
    }
)

---

Client-side Exports

Use these exports to integrate the MDT UI and systems with other scripts (e.g., Robbery scripts, Radar systems).

CreateDispatchAlert

Triggers a dispatch notification for all on-duty police.

Syntax:

exports.qf_mdt_police_v2:CreateDispatchAlert(coords, title, description, code, colorRGB, maxOfficers, duration)

Parameters:

Parameter	Type	Description
coords	vector3	Location of the alert.
title	string	Alert Header.
description	string	Detailed info (e.g., street name, vehicle info).
code	string	10-Code (e.g., '10-90').
colorRGB	table	{r, g, b} format.
maxOfficers	number	(Optional) flashing limit of units.
duration	number	(Optional) Time in ms the alert stays on screen.

Example (Bank Robbery):

-- Triggered when a player starts hacking a vault
local plyPed = PlayerPedId()
local coords = GetEntityCoords(plyPed)
local streetName = GetStreetNameFromHashKey(GetStreetNameAtCoord(coords.x, coords.y, coords.z))

exports.qf_mdt_police_v2:CreateDispatchAlert(
    coords,    
    "Bank Robbery in Progress",    
    "Silent alarm triggered at " .. streetName .. " Fleeca Bank.",    
    "10-90",    
    {255, 0, 0}, 
    15, 
    10000
)

showOfficerBadge

Displays the badge ID card on screen.

Syntax:

exports.qf_mdt_police_v2:showOfficerBadge(data)

Data Structure:

{    
    name = "Officer Name",    
    badge = "Badge Number",    
    gradeLabel = "Rank Name",    
    mugshot = "URL to image (optional)",    
    licenses = {        
        { label = "Weapon License", active = true },        
        { label = "Driving License", active = false }    
    }
}

Example:

exports.qf_mdt_police_v2:showOfficerBadge(
{    
    name = "Robert Smith",    
    badge = "9921",    
    gradeLabel = "Chief of Police",    
    licenses = {        
        { label = "Advanced Driving", active = true },        
        { label = "SWAT Tactics", active = true }    
    }
})

AddHeistZone (Map)

Adds a visual zone to the live map, useful for ongoing robberies.

Syntax:

exports.qf_mdt_police_v2:AddHeistZone(zoneData)

Example:

exports.qf_mdt_police_v2:AddHeistZone({    
    id = "pacific_standard",    
    name = "Pacific Standard Robbery",    
    position = { x = 255.2, y = 210.0 }, 
    radius = 60.0,    street = "Vinewood Blvd",    
    thumbnailUrl = "https://example.com/bank-image.jpg"
})

RemoveHeistZone

Removes a heist zone when the event is over.

Example:

exports.qf_mdt_police_v2:RemoveHeistZone("pacific_standard")

---

Camera & Radar Exports

Bodycam

Control the immersion overlays.

exports.qf_mdt_police_v2:showBodycam()

exports.qf_mdt_police_v2:hideBodycam()

exports.qf_mdt_police_v2:toggleBodycam()

Radar

Control the vehicle radar system programmatically.

-- Force show / hide a radar side ("front" or "back")
exports.qf_mdt_police_v2:showRadar("front")
exports.qf_mdt_police_v2:hideRadar("front")

-- Lock or unlock the current target of a radar side
exports.qf_mdt_police_v2:toggleRadarInteractMode("front")

-- Manually update radar data (e.g. for a tutorial or scripted event)
exports.qf_mdt_police_v2:setRadarData("front", {    
    plate = "FAKE-123",    model = "Buffalo",    speed = 150,    speedDisplay = "km/h"
})

Other exports

Export	Description
GetMugShotBase64(ped, transparent)	Renders a mugshot of the ped and returns it as a base64 string.
showDispatchAlert(data)	Draws a dispatch alert on screen without going through the dispatch system.
updateReactions(data)	Updates the unit reactions shown on an alert that is already on screen.
ShowHeistZones(zones) / SetHeistZones(zones)	Replaces the whole list of heist zones on the live map at once.
SetShootingZones(zones)	Replaces the whole list of shots-fired zones on the live map.
AddShootingZone(zone)	Adds a single shots-fired zone. Same shape as AddHeistZone.
RemoveShootingZone(id)	Removes a shots-fired zone by id.

Dispatch Integrations & Custom Alerts

Compatibility

Enable 3rd party script compatibility by editing config/config.lua.

-- Enable external dispatch scripts in config/config.lua
Config.Dispatch = {
    Integration = {
        rcore_dispatch = true, -- Set to true to automatically bridge alerts
        core_dispatch = false,
        opto_dispatch = false,
        tk_dispatch = false,
        _0r_dispatch = false,
        frkn_police_dispatch = false
    },

    -- Set to false if your external dispatch already draws its own alerts
    -- and you end up seeing every alert twice.
    ShowOnScreenAlerts = true
}

Custom Alerts

Control and send dispatch alerts to the MDT programmatically.

-- Send a custom dispatch alert manually from any server script
TriggerEvent('qf_mdt_police_v2/server/addCustomDispatch', {
    id = "custom_robbery_123",        -- (Optional) Unique ID, system generates one if empty
    title = "Store Robbery",          -- Alert title/name
    code = "10-90",                   -- Dispatch code
    color = {255, 0, 0},              -- RGB color table or HEX string (e.g., "#FF0000")
    street = "Route 68",              -- (Optional) Street name or location description
    x = 100.5,                        -- X coordinate of the alert
    y = -213.2,                       -- Y coordinate of the alert
    z = 32.5,                         -- Z coordinate of the alert
    max_officers = 6,                 -- (Optional) Maximum officers that can react (default: 10)
    duration = 5000                   -- (Optional) Duration the alert stays on screen in ms (default: 5000)
})

1. Client-Side Export

You can use the following export directly in any client-side script.

-- @param coords vector3 - The coordinates of the incident
-- @param title string - The title of the dispatch alert
-- @param description string - The detailed description
-- @param code string - The dispatch code (e.g., "10-13")
-- @param colorRGB table - An array containing RGB values (e.g., { 251, 45, 55 })
-- @param maxOfficers number - Maximum number of officers that can respond (e.g., 10)
-- @param duration number - The duration the alert shows on screen in milliseconds (e.g., 5000)

local coords = GetEntityCoords(PlayerPedId())
exports['qf_mdt_police_v2']:CreateDispatchAlert(    
    coords,     
    "Officer Down",     
    "An officer has been injured and requires immediate assistance.",     
    "10-13",     
    { 251, 45, 55 },     
    10,     
    5000
)

2. Server-Side Event (or Client TriggerServerEvent)

If you need to trigger a dispatch from the server, or prefer passing a data table, you can use the built-in server event.

local dispatchData = {    
    x = 100.0,           -- [Required] Coordinate X    
    y = -200.0,          -- [Required] Coordinate Y    
    z = 30.0,            -- [Required] Coordinate Z    
    title = "Robbery",   -- [Required] Dispatch Title    
    code = "10-90",      -- [Required] Dispatch Code        
    color = {255, 0, 0}, -- [Optional] RGB table or HEX string (e.g., "#FF0000"). Defaults to blue.    
    street = "Route 68", -- [Optional] Street name. Defaults to empty.    max_officers = 10,   -- [Optional] Maximum responding officers. Defaults to 10.    
    duration = 5000,     -- [Optional] Screen duration in ms. Defaults to 5000.    
    id = "custom_id_1"   -- [Optional] A custom unique ID if you need to manage it later
}

-- If triggering from a SERVER script:
TriggerEvent('qf_mdt_police_v2/server/addCustomDispatch', dispatchData)

-- If triggering from a CLIENT script:
TriggerServerEvent('qf_mdt_police_v2/server/addCustomDispatch', dispatchData)

Resetting Officer Hours

The Police MDT tracks on-duty hours for all officers. These hours can be manually reset via a server callback. The system verifies if the player executing the reset has the appropriate job permissions defined in Config.Jobs.

• Callback Name: qf_mdt_police_v2/resetOfficerHours

• Target Identifier: id (Character Identifier / CitizenID / License)

Code Example

local officerId = "POLICE_001"

CALLBACK.TriggerServerCallback('qf_mdt_police_v2/resetOfficerHours', function(result)    
    if result.success then        
        print("Officer hours have been reset successfully.")    
    else        
        print("Error: " .. result.error)    
    end
end, officerId)

Duty Status Change Hook

We have added a server-side hook that triggers whenever an officer changes their duty status via the MDT (e.g., clicking "Available" or "Unavailable"). This is useful for synchronizing the MDT state with other job-related systems or triggering custom events.

• Location: config/server/editable.lua

• Function: EDITABLE.OnStatusChange(source, status)

Usage Example

This hook is defined in the editable configuration file and can be used to trigger framework-specific duty events:

function EDITABLE.OnStatusChange(source, status)
    -- Triggered for status: "available", "unavailable"
    
    if status == "available" then
        -- Example: Triggering a custom onDuty event
        TriggerEvent('examplepolicejob:onDuty', source)
    elseif status == "unavailable" then
        -- Example: Triggering a custom offDuty event
        TriggerEvent('examplepolicejob:offDuty', source)
    end
end