Admin menu#

/dispatchadmin opens the admin menu in game. Everything you change there is saved in the database (koja_dispatch_settings) and applies live, without a restart. The values in config.lua are the defaults.

Access#

A player can open the menu when one of these is true:

• their framework group is in Config.Admin.groups (admin, god, superadmin),
• they have the ACE koja-dispatcher.admin (Config.Admin.ace).

add_ace group.admin koja-dispatcher.admin allow

The command is Config.Admin.command. It does nothing from the server console; use dispatchcheck there. Every admin change is printed in the server console and, with Discord logs on, posted to the admin webhook.

Pages#

Every setting has a reset button that shows the default value. Reset all settings puts every setting back to the config.lua value; stations, allowed jobs and created jobs are kept.

Overview#

Refreshes every few seconds. It shows the dispatchers on shift (station and since when), units on duty per department with AI on and off duty and players, active incidents and open calls, the current setup (modes, stations, allowed jobs) and the incident statistics.

Quick actions affect everyone on the server at once:

Modes#

Three choices decide how the whole dispatch works. The page shows a live How calls flow diagram that changes with the modes.

Call sources (mode.calls)#

Generated calls only come while at least one dispatcher is on shift.

Units (mode.units)#

When nobody is on shift (mode.noDispatcher)#

What happens to a real call (/911, phone, API, client alert) when no dispatcher can take it.

Stations#

Dispatch stations (consoles) in the world. A player whose job may dispatch walks up to one to start a shift. There can be up to 40 stations.

Placing a station with the gizmo#

The admin menu hides, a camera orbits a see-through copy of your character that plays the exact sit or stand pose, and you place it with a 3D gizmo. The spot must stay within 25 m of where you stand.

Access & jobs#

Jobs allowed to dispatch. A player needs one of these jobs at the minimum grade or higher. Only those players see the start prompt at a station. A job that the framework does not know is marked. With no job in the list nobody can start a shift. Removing a job does not end shifts that are running.

Create job (ESX and QBCore only). Name (lowercase, no spaces), label, grades (name, label, salary, up to 20) and the lowest grade that can dispatch. The job is created in the framework and added to the allowed list. On ESX it is created with ESX.CreateJob, on QBCore with exports['qb-core']:AddJob. On other frameworks add the job yourself.

Hire. Search online players by name, ID or job and set their job and grade. The list shows who is on shift and whether the grade can dispatch.

Dispatcher ranks. With the career module on, set the rank of online players. Setting a rank moves their XP to that rank's threshold.

Calls & limits#

The generated call settings are greyed out when call sources are real.

Pay#

Paid when the shift ends: minutes worked plus a bonus per score point, scaled by the star rating, up to the maximum payout (0 = no cap). See Config.Pay.

Features#

Dispatcher experience (intro camera, AI callers), automatic alerts (shots, crashes, downed players; only used when call sources include real calls; the switches apply live), map layers (civilians, NPC peds) and field units (scenes, auto waypoint).

Integrations#

koja-mdt status (not installed, running, not started) and its five settings, the Client alerts switch for the client export SendAlert, and a copyable list of the developer exports. See Integrations.

Modules#

Settings of the optional modules, one group per module: career, compat, discord, dynamics, fleet, hospitals, mdt_status, mdt_tools, patrol, phones, pursuit, stats, training, voice. They save and apply live like everything else. Settings that other resources add with the RegisterSetting export appear here too, grouped by the part of the key before the first dot. The full list is in All settings.

Scenarios#

Create, edit, duplicate and disable the 911 scenarios generated calls are drawn from.

• Built-in scenarios can be switched off and given another weight (how often they are drawn, 0 never). They cannot be deleted. Reset restores the default weight.
• Custom scenarios (up to 100) are created from scratch or by duplicating a built-in one. Fields: name, category, priority, caller (any, male, female), distress, scene (none, crowd, fight, fire, injured, crash), 1 to 5 opening lines, answers per question with an optional chance and the extra units the answer reveals, base needs, correct instruction, respond, fail and work time, points, weight, needs transport, prank call, and where it happens (location tags, or up to 10 own places picked on the map or at your position; {location} inserts the place name).
• Test call now rings the scenario at once.

Custom scenarios have no recorded voice lines, so their calls are text only unless AI callers are on. They are stored in koja_dispatch_scenarios.

AI fleet#

Add, remove and disable AI units and stations. At first the fleet comes from Config.AiUnits. Press Copy config and edit to copy it into the editor; from then on the editor overrides Config.AiUnits.fleet and Config.AiUnits.stations.

• Units: callsign, unit type and station (the type must match the station's department). Disabled units on an incident finish the job first; removed units are released at once. Up to 80 units.
• Stations: name, department and position (click the map or use your position). A station with units cannot be removed. Up to 30 stations.
• Reset to config deletes the edited fleet and respawns the units from Config.AiUnits.

If Config.AiUnits.enabled is false, no AI unit spawns even when listed here. The edited fleet is stored in koja_dispatch_ai_stations and koja_dispatch_ai_fleet.

All settings#

Every key below can be changed in the menu, read with GetSetting and changed with SetSetting. Other resources can add their own keys with RegisterSetting (see Server exports). Defaults come from the config option named in the last column.

Core#

Modules#

Module defaults come from the matching Config block (for example pursuit.maxActive from Config.Pursuit.maxActive). career.xp*, career.gate*, mdt_status.*, mdt_tools.* and training.* have their defaults in code.