Burnsie

Press the panic button. Dispatch calls it in over the scanner with your real location and the cavalry comes in waves: patrol first, SWAT if things stay bad, air support if they get worse. Go down, and the system calls it in for you. When the threat clears: "we are Code 4, no further units required," blips fade, and the city goes back to work. Join our Discord for more information, beta testing, and updates: https://discord.gg/9xETbK6227 Features One chord: (default Ctrl+B, controller supported, optional hold-to-confirm with a "disregard last" chirp for accidental taps) triggers the full choreography: radio squelch, radio animation, panic tone, zone-aware scanner broadcast at your actual position. Staged escalation: patrol immediately; SWAT/NOOSE and helicopters only join while you're still in danger. Threat stays clear → automatic Code 4. Prefer the classic everything-at-once blast? One config switch. Honest unit tracking: every unit that actually spawns is blipped, tracked and arrival-detected — the status bar shows units genuinely on scene (helicopters count while overhead), not wishful requests. OFFICER DOWN: drop below critical health (or get dropped) and the distress call goes out automatically — officer-down audio, EMS forced into the response, screen effects, visible wounds. You don't press anything; that's the point. Second Chance (experimental, on by default): instead of instant respawn, bleed out on a timer — if EMS reaches you in time, you're stabilized and keep playing. Situation-aware dispatch: in a pursuit, backup joins the chase; on a rooftop or in the water, an air unit leads; on Cayo Perico / North Yankton the response adapts to what can actually spawn there. Plays nice with your setup: agency left to your backup.xml/region packs (or force one), callouts held during panic and restored after, and a clear warning if another panic-capable plugin is installed instead of double dispatch. Optional Extras AI officers who go down near you get called in by name; smart shots-fired auto-panic (only when hostiles actually engage, less-lethal excluded); incident report files after every panic. For developers: a public API (PanicButton.API.PanicProvider) to trigger, cancel, or listen to panic events. Controls (all configurable): Ctrl+B panic · End cancel/Code 4 · console: PanicButtonTrigger, PanicButtonCancel, PanicButtonReloadConfig Join our Discord for more information, beta testing, and updates: https://discord.gg/9xETbK6227

Burnsie.Common is the shared framework library used by Burnsie's LSPDFR plugins — starting with PanicButton V1, with more on the way. It does nothing on its own. Install it when one of those plugins lists it as a requirement. One copy serves every Burnsie plugin, so you never download the same machinery twice. What's inside (for the curious): two assemblies that handle the unglamorous parts of a well-behaved plugin - correct on/off-duty lifecycle, crash-proof police scanner audio (validated against the audio files actually on your install), backup dispatching with real unit tracking and arrival detection, config files that document themselves, keybinds that stay quiet while you're typing or paused, and audio/visual helpers that fail gracefully instead of taking the plugin down. Installation: extract — the plugins folder merges into your Grand Theft Auto V root directory (the folder with GTA5.exe). No configuration, no keybind. Upgrading from the old BurnsCommon (v1): delete BurnsCommon.dll. Requirements: RAGE Plugin Hook 1.124+, LSPDFR 0.4.9+. For plugin developers: documented public API, IntelliSense XML included, full developer guide in the repository. Semantic versioning — plugins built against 2.x keep working across 2.x updates. You can access fully documentation via https://www.burnsieshideout.com/docs/burnsie-common/developer-guide Join our Discord for more information, beta testing, and updates: https://discord.gg/9xETbK6227