Full Release • LSPDFR Response Management

# Callout Response

A configurable response-management plugin for LSPDFR that gives patrol, state, tactical, medical, fire, and scene-service units a smarter role during active callouts.

Installation Guide View Features Configuration Notes
Manual Requests Local, state, SWAT, EMS, fire, and coroner-style response options.
Automatic Backup Profiles and priorities can drive automatic response behavior.
Staged Roll-In Hold units outside the scene until the player or safety logic releases them.
Provider Friendly Built around Native LSPDFR, Ultimate Backup, and Policing Redefined style workflows.

Overview

## Built for better callout response flow.

Callout Response is designed to make backup and service response feel more controlled during LSPDFR gameplay. Instead of every request being a simple unit spawn, the plugin focuses on response packages, staged arrival, state/local patrol blending, configurable prompts, and safer service-unit release.

01

### Request What You Need

Use the manual request menu for direct response options such as Local Patrol, State Patrol, SWAT, ambulance, fire, and coroner-style units.

02

### Let Profiles Work

Automatic backup can use configured response logic to prepare units when a callout is active, while still giving the player control over prompts and release behavior.

03

### Control the Scene

Staging, Prompt Release, and Safety Release help prevent service units from rushing into dangerous scenes before the player is ready.

Core Systems

## Features focused on dispatch realism.

### Manual Backup Request Menu

A focused request menu for the units players actually need during active calls. Callout Response keeps the player-facing manual flow simple instead of hiding core requests behind complicated status boards.

Local Patrol State Patrol SWAT EMS Fire Coroner

### Automatic Response Logic

Automatic backup can prepare units based on configured response behavior. Players who prefer less prompting can tune the system toward a more automatic flow.

ResponseProfiles.xml Priority Ranges Unit Counts

### Prompt Release

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.

Y/N Prompts Persistent Prompting Player-Controlled Roll-In

### Safety Release

Safety Release allows patrol/SWAT to roll in normally while EMS, fire, and coroner-style services can remain staged until safer conditions are met.

Service Hold Scene Safety Release Distance

### State / Local Patrol Mix

Patrol response can blend Local and State units. General patrol can use one percentage while pursuit response can use a more state-heavy mix.

General State % Pursuit State % Provider Aware

### Global Responder Behavior

Mimic Lights and AI Siren Cycle behavior can apply more broadly to nearby responder vehicles, not only units directly created by Callout Response.

Mimic Lights AI Siren Cycle Scan Radius

Installation

## Drag, drop, verify, patrol.

### Install Requirements

Make sure Grand Theft Auto V, RAGE Plugin Hook, and LSPDFR are installed and working before installing Callout Response.

### Copy Plugin Files

Place the included plugin files into the standard LSPDFR plugin folder structure. Keep the CalloutResponse folder with the DLL and included configuration/data files.

Grand Theft Auto V/ └─ Plugins/ └─ LSPDFR/ ├─ CalloutResponse.dll └─ CalloutResponse/ ├─ Config.ini ├─ ResponseProfiles.xml └─ additional included data files

### Install Optional Audio

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.

Grand Theft Auto V/ └─ lspdfr/ └─ audio/ └─ scanner/ └─ CalloutResponse/ └─ custom/

### Configure In Game

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

## Tune it for your patrol style.

### Recommended Full Release Notes

Ready

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, and responder behavior.

24

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.

### Example Config Areas

[Staging] Enabled=True ReleaseMode=PromptRelease SafetyReleaseDistance=125 [PatrolMix] GeneralStatePercent=50 PursuitStatePercent=80 [ResponderBehavior] MimicLights=False AISirenCycle=False ScanRadius=300

### Prompt Release

Best for players who want manual approval before staged response units roll into the callout area.

### Safety Release

Best for players who want patrol response to remain active while services wait for safer conditions.

### Fully Automatic Style

Disable backup prompts and use Safety Release or disabled staging if you prefer a lower-interaction setup.

Provider Behavior

## Works with the response ecosystem you use.

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.

i

Provider behavior can vary based on your installed versions and XML setup. If a specific provider unit does not appear, verify that the provider itself is installed, configured, and able to spawn that unit independently.

Release Notes

## Full release highlights.

### Added

Staged roll-in, Prompt Release, Safety Release, persistent prompts, configurable patrol mix, and broader responder light/siren behavior.

### Improved

Manual backup request flow, auto backup handling, staged blip cleanup, provider-aware patrol selection, and CRConfig organization.

### Cleaned Up

Removed experimental overhead from the release scope and kept the mod focused on response management.

### Recommended Testing

Test manual requests, auto backup, staging, service release, local/state patrol mix, and global mimic/siren settings.

Support

## Reporting issues clearly helps.

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.

### Useful Report Details

- RAGE Plugin Hook log
- Active callout name
- Provider installed: Native, UB, PR, or multiple
- Prompt Release or Safety Release mode
- Whether the request was manual or automatic
- What unit type failed or behaved incorrectly

### Before Reporting

- Confirm the plugin loads cleanly.
- Confirm dependencies are installed correctly.
- Check Config.ini for unsupported values.
- Verify provider XMLs work in the provider itself.
- Try reproducing the issue on a simple callout.