A configurable response-management plugin for LSPDFR that gives patrol, state, tactical, medical, fire, and scene-service units a smarter role during accepted callouts.
Overview
Callout Response makes backup and service response feel more controlled during LSPDFR gameplay. It focuses on response packages, staged arrival, state/local patrol blending, provider-aware backup, configurable prompts, and safer service-unit release.
Use the manual request menu for Local Patrol, State Patrol, SWAT, ambulance, fire, and coroner-style services. The request selector dispatches immediately when Enter is pressed.
Automatic backup can use configured response logic after the callout is accepted. Matching supports more forgiving wording so callout names do not need to be exact 1:1 matches.
Staging, Prompt Release, and Safety Release help prevent service units from rushing into dangerous scenes before the player is ready.
Core Systems
A focused request menu for the units players actually need during active calls. Scroll left/right to select a unit type, then press Enter on the same row to dispatch it.
Automatic backup can prepare units based on configured response behavior. Profile matching supports ordered phrase matching and broader token matching for callouts such as wanted suspect, vehicle fire, dead body, pursuit, and similar names.
Prompt Release keeps staged units under player control. Patrol/SWAT can be approved first, while service units can be held for a separate approval step. Prompts stay active until answered.
Safety Release allows patrol/SWAT to roll in normally while EMS, fire, and coroner-style services can remain staged until safer conditions are met.
Patrol response can blend Local and State units. General patrol can use one percentage while pursuit response can use a more state-heavy mix.
Mimic Lights and AI Siren Cycle can apply to valid backup or pursuit responder units while avoiding random ambient emergency vehicles that happen to be nearby.
Installation
Make sure Grand Theft Auto V, RAGE Plugin Hook, LSPDFR, and .NET Framework 4.8.1 are installed and working before installing Callout Response.
Place the included plugin files into the standard LSPDFR plugin folder structure. Keep the CalloutResponse folder with the DLL and included configuration/data files.
If the release package includes scanner audio or custom phrase folders, place them in the matching LSPDFR audio folders. Keep custom WAV names simple and avoid special characters.
Use CRConfig for the main configuration menu. Advanced users can edit Config.ini and ResponseProfiles.xml manually.
Do not rename the plugin folder or DLL unless the release instructions specifically say to. File paths matter for loading configuration, profiles, and optional audio.
Configuration
Most settings can be managed through CRConfig. Config.ini is best for advanced users who want direct control over response distances, unit counts, staging, prompt behavior, patrol mix, provider preference, and responder behavior.
Supported unit limit: Callout Response is intended to support up to 24 configured/requested backup units. Values above 24 are unsupported and may prevent loading or menu behavior from working correctly.
Best for players who want manual approval before staged response units roll into the callout area.
Best for players who want patrol response to remain active while services wait for safer conditions.
Disable backup prompts and use Safety Release or disabled staging if you prefer a lower-interaction setup.
Callout acceptance behavior: automatic backup and staging prompts are intended to wait until the player accepts the callout. Offered-but-not-accepted callouts should not trigger staged response prompts.
Provider Behavior
| Provider | Purpose | Behavior |
|---|---|---|
| Native LSPDFR | Fallback / base response | Uses standard LSPDFR-compatible backup behavior where supported. |
| Ultimate Backup | Provider-backed response | Uses available Ultimate Backup paths for local/state patrol and supported services. |
| Policing Redefined | Provider-backed response | Uses provider-aware request handling for PR-style local/state and service responses where supported. |
Preferred providers are handled more reliably at startup. If a selected provider becomes available shortly after Callout Response loads, the plugin can refresh and apply the preferred provider without forcing Native.
Pursuit backup can prefer the active suspect/vehicle target instead of defaulting to the player or original callout area when a pursuit is active.
Provider behavior can vary based on installed versions and XML setup. If a provider unit does not appear, verify that the provider itself is installed, configured, and able to spawn that unit independently.
Release Notes
Staged roll-in, Prompt Release, Safety Release, persistent prompts, configurable patrol mix, manual Local/State patrol requests, and backup-only responder light/siren behavior.
Manual backup request flow, auto backup handling, staged blip cleanup, provider startup selection, vague profile matching, pursuit targeting, and CRConfig organization.
Scene fallback behavior, “scene not resolved yet” manual request failures, pre-acceptance staging prompts, and ambient emergency vehicles being affected by global light/siren sync.
Test manual requests, accepted-callout gating, auto backup, staging, service release, profile matching, local/state patrol mix, pursuit backup targeting, and global mimic/siren settings.
Support
If something breaks, include enough detail to reproduce it. A useful report should include your RAGE Plugin Hook log, active callout, installed provider mods, selected release mode, and what happened right before the issue.
Best report format: active callout, selected provider, response mode, requested unit type, whether the request was manual or automatic, and the RPH log.