Brave Police Backup sends police backup requests, map routes and alert sounds. The inspected resource imports qb-core on both client and server; it is not a standalone or ESX release.
Match the folder and sound setup
Place the folder containing fxmanifest.lua in resources. If you keep the repository name brave_policebackup, use ensure brave_policebackup after qb-core. The README’s ensure police-waypoint example only matches a folder actually named police-waypoint. For sound alerts, copy code1.ogg, code2.ogg, code3.ogg and code99.ogg into your InteractSound sound directory and start that dependency first.
HOME requests foot-pursuit backup, INSERT vehicle-pursuit backup, PAGEUP armed-robbery backup and END Code 99. Players can change registered bindings in FiveM’s keybinding settings. The client includes a 30-second cooldown and removes map blips after 40 seconds; neither value establishes server-side authorization.
Review permission and rate checks
The backup server handler checks the police job, but does not enforce on-duty status or its own cooldown. The separate sound-broadcast event has no sender job check. Before public use, validate the sender, duty policy, permitted alert codes, coordinates and request frequency on the server. Keep sound names on an allowlist. Do not assume optional notification branches remove the qb-core dependency.
Test ordinary police and civilian accounts, off-duty behavior, repeated requests, all four sounds and simultaneous alerts. Confirm that recipients receive the correct route and that blips expire. Back up the resource and sound files before replacing them.