Choose a revision before following a setup tutorial
This guide reviews upstream commit d488316ae7f579740c93f8bd873fc552a48a7038 on November 7, 2026. Its manifest identifies version 3.0.0 and targets GTA V. It is not evidence of GTA VI compatibility. Keep your installed revision beside any configuration instructions.
The README lists qb-core or qbx_core, ox_lib, lsn-radar and PolyZone. Its installation builds the frontend in ui with npm install and npm run build, then starts ps-dispatch. The build clears html; persistent frontend assets belong in ui/public.
Before updating, preserve your working configuration and customized assets outside the build destination. Compare your installed files with the intended revision on staging. An older tutorial can be useful context, but differences in paths, exports or integrations need checking against your actual package.
Separate startup, interface and recipient checks
The reviewed README places configuration in shared/config.lua. Config.Jobs controls recipients; OnDutyOnly, FilterOnDuty and FilteredBroadcast affect duty checks and delivery. Its CustomAlert example uses codeName with a matching Config.Blips entry for map presentation.
The following is a proposed diagnostic sequence, not a report of a server test performed by Magnate. Change one layer at a time and retain the first relevant error. A visible board is only one observation; it does not establish that another player received the same call.
| Layer | Check on staging | Evidence to retain |
|---|---|---|
| Startup | Start the matching dependencies and dispatch resource | First error, resource name and revision |
| Interface | Open the dispatch board after a fresh connection | Visible board and relevant browser-console error |
| Eligibility | Compare an intended responder with an unrelated job | Job, duty state and which player received the call |
| Alert | Trigger one controlled event from its owning script | One matching call with correct location |
| Map | Inspect the call location and any radius | Marker location and alert identifier |
| Recovery | Reconnect the responder and repeat the same event | Whether delivery still works after reconnect |
When an alert does not arrive
Begin with a known eligible test character and one controlled event. Record the character’s job, duty state, installed revision and event timestamp. Check the script creating the alert before changing the display. If no event was generated, changing a blip sprite cannot repair that upstream failure.
Next compare the alert integration with the export documented for your revision. Check spelling, data types and whether the caller runs on the expected side. Avoid copying an arbitrary public event into production merely because it makes a notification appear. Server-owned gameplay outcomes should retain their own authorization checks.
For duplicate calls, count how many integrations fire for the same incident before adjusting notification timing. One robbery resource and a second bridge can both report an event. Reproduce with a single enabled path on staging to locate the duplication.
When the board works but the map or UI does not
A missing map marker and a blank board are different observations. For a marker problem, inspect the alert identifier and its map configuration, then verify the coordinates against the incident. For a blank board, inspect generated frontend files and the first UI loading error before changing job permissions.
Keep custom frontend source and generated output distinct during upgrades. Compare a clean staging build with your customized build, then reintroduce changes in small groups. This isolates a customization failure without claiming that deleting generated files is a universal fix.
Keep dispatch separate from radio, MDT and police jobs
Write an acceptance scenario covering the whole incident: a gameplay script reports an event, an eligible responder receives it, the map identifies the location and the responder communicates with another player. Test each handoff independently. A working voice radio does not prove dispatch routing, and an installed station MLO does not prove police-job permissions.
Use the police-script guide to plan job integration and the radio guide for voice acceptance checks. For a support report, include a minimal reproduction, exact revisions and redacted errors. Do not include account credentials or private player data. These proposed checks do not establish performance at a particular server population.
Questions, answered.
Does ps-dispatch support GTA VI?
The reviewed manifest targets GTA V. This guide does not establish GTA VI compatibility.
Why can I open the board but receive no alerts?
Check the originating integration and recipient job and duty conditions separately. A working interface does not establish alert delivery.
Should I follow an older ps-dispatch tutorial?
Match its revision to your installed resource and compare dependencies, paths and exports before copying configuration.
Sources & editorial notes
Source review: November 7, 2026. Platform announcements can change. This guide separates published facts from Magnate’s original analysis and preparation advice.
- Project Sloth — ps-dispatch pinned README Installation and configuration reviewed November 7, 2026; not a server runtime test.
- Project Sloth — ps-dispatch pinned manifest GTA V target, UI build path and resource imports.
- Cfx — Secure your events Server-side validation of client-triggered actions.
Published by an independent editorial brand. Read our editorial standards.
