Guide · Setup
Dispatch scripts and quiet-hours calls
Your dispatch script is where officers see calls. Quiet-hours calls should land there too, looking like any other call, so officers don't need a second screen. Here's how the common FiveM dispatch scripts work with Overshift today.
At a glance
| Script | Frameworks | With Overshift |
|---|---|---|
| ps-dispatch | QBCore, Qbox | Full support: calls hold back for real alerts, plus real-alert radio lines, acknowledgements, pick-ups and response times. |
| cd_dispatch | QBCore, ESX | Calls and blips, and calls hold back for real alerts. Built from its public docs and not yet checked on a live server; tell us how it goes. |
| qs-dispatch | QBCore, Qbox, ESX | Calls, blips and radio lines, and calls hold back for real alerts. Pick-ups and response times not measured yet. |
| rcore_dispatch | QBCore, Qbox, ESX | Calls, blips and radio lines, and calls hold back for real alerts. Pick-ups and response times not measured yet. |
| core_dispatch | QBCore, ESX | Calls, blips and radio lines. Real alerts aren't seen yet, so calls go by the quiet timer and player count. Pick-ups and response times not measured yet. |
| lb-tablet | QBCore, Qbox, ESX | Calls, blips and radio lines. Real alerts aren't seen yet, so calls go by the quiet timer and player count. Pick-ups and response times not measured yet. |
| None | Any | An on-screen notice and a map blip for officers on duty. |
Frameworks are the ones each script is commonly run on; check the script's own page for what it supports.
How Overshift picks one
On start, Overshift looks for the scripts above in that order and uses the first one that's running. /overshift doctor prints which one it picked. To choose yourself, set Config.Dispatch.resource in config.lua, for example 'qs-dispatch'.
If a dispatch update changes its API and a call is rejected, the call still reaches officers as an on-screen notice, and the server console says so. A dispatch update never silently swallows calls.
Any other script
If you run a custom or less common dispatch, point Overshift at it with a small function in the config:
Config.Dispatch = {
resource = 'auto',
custom = function(alert)
-- alert.title, alert.code, alert.priority (0 critical .. 3 low), alert.message,
-- alert.street, alert.coords, alert.service, alert.jobs, alert.targets
exports['my-dispatch']:NewCall(alert.title, alert.message, alert.coords, alert.jobs)
end,
}
Want your script supported properly? Tell us which one. Requests decide what we add next.
EMS, fire and tow
On Patrol and up, Overshift also sends medical, fire and tow calls, each with its own quiet timer and only while someone from that service is on duty. They go through the same dispatch script, routed to the jobs in Config.Services. See the docs.