Guide · Setup
Police calls for ESX Legacy servers
ESX servers have the same quiet-hours problem as everyone else: a couple of officers on duty, nothing on the radio, and a city that feels empty. A few things work differently on ESX, mostly around who counts as on duty.
Who counts as on duty
ESX Legacy doesn't have one standard duty system. Servers usually use one of two patterns:
- An onDuty flag on the player's job, toggled at a station or with a command.
- Off-duty jobs, where going off duty switches the player to a job like
offpoliceoroffambulance.
Anything that sends police calls has to read your server's pattern, or it'll send calls to an empty PD. Overshift handles both: a player counts as on duty unless job.onDuty is false or their job is an off-duty job.
Job names
Check your police job names against the defaults. Overshift treats police, sheriff, bcso and sasp as police; add yours to Config.PoliceJobs. EMS, fire and tow jobs live in Config.Services.
Dispatch on ESX
qs-dispatch, rcore_dispatch, core_dispatch, lb-tablet and cd_dispatch all run on ESX, and Overshift sends calls to each of them. Without a dispatch script, calls show as an on-screen notice and a map blip. See dispatch scripts compared.
Install
ensure es_extended ensure ox_lib ensure your_dispatch_script ensure overshift
Restart, then run /overshift doctor as an admin. It should show ESX, your dispatch script, and your officers on duty. /overshift test sends one call now; /overshift test ems tests the medical calls on paid plans.
Calls go out only after the city has been quiet for 12 minutes, at most 4 an hour, waiting longer as more players join and stopping at 40 players. All of it is adjustable under Config.Quiet.