Guide · Setup
Police calls for Qbox servers
Qbox servers run into the same problem as everyone else at 4am: two officers on duty, a quiet radio, and nothing to roll on. Qbox keeps QBCore's player data, so most of what works on QBCore works here. These are the parts worth checking.
Who counts as on duty
Qbox stores duty on the player's job as job.onduty, the same field QBCore uses. Officers clock in and out at your duty points or with your duty command, and anything that sends police calls should read that flag. Overshift counts an officer as on duty only while job.onduty is true, so off-duty cops never get pinged.
Job names and job types
Qbox jobs carry a type as well as a name. Overshift treats any job with type leo as police, so most Qbox PD setups work without edits. If your police jobs use another type, add their names to Config.PoliceJobs (the defaults are police, sheriff, bcso and sasp). EMS, fire and tow jobs live in Config.Services, and EMS also matches the ems job type.
Dispatch on Qbox
ps-dispatch is the most common choice on Qbox, and Overshift sends calls to it directly. qs-dispatch, rcore_dispatch, core_dispatch, lb-tablet and cd_dispatch work too. Without a dispatch script, calls show as an on-screen notice and a map blip. See dispatch scripts compared and automatic calls in ps-dispatch.
Install
ensure ox_lib ensure qbx_core ensure your_dispatch_script ensure overshift
Overshift finds qbx_core on its own. If you also run the qb-core bridge, it still picks Qbox first. Restart, then run /overshift doctor as an admin. It should show Qbox, your dispatch script, and your officers on duty. /overshift test sends one call now.
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 can be changed under Config.Quiet.