Skip to main content

General Dispatch Center Settings: Simulation Impact

How dispatch center configuration settings affect the simulation environment, gameplay mechanics, and player experience.

Updated today

ResQueServe can operate in two modes:

  • Real Dispatch Operations: No simulation component, real-world emergency dispatch management (not described here)

  • Simulation Mode: Includes simulated missions, units, and gameplay mechanics (SIM Dispatcher)

This guide focuses on SIM Dispatcher. All settings discussed here affect how the simulation generates missions, controls unit behavior, and creates gameplay scenarios for players. As a dispatch center administrator or owner, you'll use these settings to configure how your dispatch center operates within the ResQueServe simulation platform.

Basic Information

Name

The name of your dispatch center. This name is combined with your selected category to form the full display name. For example, if you choose category "Leitstelle" and name "Berlin," the full name becomes "Leitstelle Berlin."

  • Displayed in the dispatch center directory and browse pages

  • Shown in the session interface and player views

  • Used in Discourse forum topics (if public)

Category

Different dispatch center types including native classifications. Defines the type/classification of your dispatch center, which automatically prepends a localized prefix to your dispatch center name. Contact us for adding more language native categories.

  • Automatically adds the localized category prefix to your dispatch center name

  • Helps organize and categorize dispatch centers in the directory

  • Makes it easier for players to find dispatch centers matching their region/language

Example:

  • Category: "Integrierte Regionalleitstelle"

  • Name: "München"

  • Full Display Name: "Integrierte Regionalleitstelle München"

Address Package

Selects which geographic address database your dispatch center will use. Address Packages are collections of geographic address data (countries, states, cities, districts, streets). They define the geographic scope within which your dispatch center operates.

Without an Address Package, players cannot start new sessions. The Address Package provides all the geographic locations used in mission generation or address search boxes.

Impact on Gameplay:

  • Defines available locations for mission generation

  • Determines available streets, districts, and cities for address lookup

  • Provides the geographic framework for unit routing and navigation

Address

Sets the physical headquarters location of your dispatch center.

  1. Click "Set Address" button

  2. Select from addresses available in your chosen Address Package

  3. Choose the specific location (Country → State → City → District → Street)

Your dispatch center MUST have an Address Package assigned before.

Call Center Configuration

These settings define emergency contact numbers and instructions displayed to users when they need to contact the dispatch center.

Call Numbers

  • Call Number - Emergency: Emergency hotline number for urgent calls
    ​Example: 112, 911

  • Call Number - Patient Transport: Non-emergency patient transport booking line
    ​Example: 19222

  • Call Number - Office: Administrative office number for general inquiries

Call Instructions

Call Text - Emergency, Call Text - Patient Transport and Call Text - Office are displayed in the simulation dialog as first message. For example: "911, what is your emergency?".

Operations and Mission Settings

Keywords Per Operation

Controls how many keyword input fields appear in the Operation Desk when creating or managing operations. Keywords represent operation classifications that define how units and resources are dispatched:

  • Each keyword has associated dispatch amounts for different unit types

  • Keywords can indicate urgency level, transport type, fire alarm status, police involvement, etc.

  • They determine which units and how many are automatically suggested during dispatch

Impact on Gameplay:

  • If set to 1: Operators see a single full-width keyword selection field

  • If set to 2-6: Multiple keyword dropdowns appear (displayed in 2 columns)

  • Operators must select the specified number of keywords when creating an operation

  • Selected keywords determine automatic unit dispatch suggestions

  • More keywords = more complex/flexible operation classification

Example Usage:

  • Set to 1 for simple dispatch centers with straightforward operations

  • Set to 3-4 for complex dispatch centers needing detailed operation classification

  • Each keyword's dispatch amounts sum together to calculate total unit requirements

Operations Per Year

Sets the expected annual mission frequency for your dispatch center. This setting defines the baseline mission generation frequency that your dispatch center expects to handle annually. It has no effect on the actual mission frequency. It's only purpose to calculate the starting operation id value. It prevents always set to "1" at session start.

Max Players

Sets the maximum number of concurrent players/operators allowed in your dispatch center. Limits visible workplaces in the Realm interface (capped at minimum of 10 or MaxPlayers)

Service Type Toggles

These three toggles enable or disable entire service branches of your dispatch center. At least one must be enabled for your dispatch center to function.

Is Dispatching Patient Transports

Enables regular (non-urgent) ambulance patient transport missions.

  • Generates MissionCategory.AmbulanceRegular missions

  • Includes scheduled patient transports, hospital transfers, and discharges

  • Patient transport adjustment settings become active (see Section below)

  • Weekend reduction settings for patients apply

When Disabled:

  • No regular patient transport missions generate

  • Patient transport adjustment percentages are ignored

  • Reduces overall mission complexity for urgent-only dispatch centers

Use Cases:

  • Enable for full-service ambulance dispatch centers

  • Disable for fire/rescue-only or urgent-ambulance-only dispatch centers

Is Dispatching Urgent Ambulance

Enables urgent/emergency ambulance response missions.

  • Generates MissionCategory.AmbulanceUrgent missions

  • Generates MissionCategory.AmbulanceUrgentWithDoctor missions

  • Emergency response scenarios become available

  • Weekend reduction settings for urgent ambulance apply

When Disabled:

  • No urgent ambulance missions generate

  • Emergency response capabilities disabled

Use Cases:

  • Enable for emergency medical service dispatch centers

  • Typically always enabled unless running a specialized center

Is Dispatching Fire and Rescue

Enables fire department and technical rescue operations.

  • Generates MissionCategory.FireAndRescue missions

  • Fire incidents and technical rescue scenarios become available

  • Patients can require technical rescue, ladders, or door breaching

  • Weekend reduction settings for fire/rescue apply

When Disabled:

  • No fire or rescue missions generate

  • Patient rescue requirements automatically disabled:

    • IsBehindDoor forced to false

    • RequiresLadder forced to false

    • RequiresTechnicalRescue forced to false

Use Cases:

  • Enable for integrated dispatch centers handling fire and EMS

  • Disable for ambulance-only dispatch centers

Patient Transport Adjustments

These settings appear only when "Is Dispatching Patient Transports" is enabled. They control the distribution and characteristics of regular patient transport missions.

Mission Type Distribution Percentages

These four percentages must sum to exactly 100% and determine the types of regular ambulance transport missions that generate.

Patient Hospital Transfer Percent

Percentage of missions that are inter-hospital transfers (patient moved from one hospital to another).

When Generated: Any time during simulation hours
​Typical Range: 15-30%

Patient Hospital Discharge Percent

Percentage of missions where patients are discharged FROM the hospital.

When Generated: Only between 6:00-17:00 hours (business hours)
​Typical Range: 20-35%

Details:

  • Pickup location: Hospital

  • Destination: Home, nursing home, or rehabilitation clinic (controlled by other setting)

Patient Hospital Ambulant Percent

Percentage of missions that are ambulatory/outpatient transports (non-emergency medical appointments).

When Generated: Only between 6:00-16:00 hours on weekdays
​Typical Range: 10-25%

Details:

  • Lower urgency patient transports

  • Typically for scheduled medical appointments

  • Patients can usually walk with assistance

Patient Hospitalization Percent

Percentage of missions where patients are transported TO a hospital for admission.

When Generated: Any time during simulation hours
​Typical Range: 25-40%

Details:

  • Pickup location: Controlled by "Hospitalization From Home" percentage (see below)

  • Destination: Hospital for admission

The sum of these four percentages must equal exactly 100%. The Event Planner uses weighted random selection based on these percentages to determine the mission type for each regular ambulance mission.

Example Configuration:

  • Hospital Transfer: 25%

  • Hospital Discharge: 30%

  • Ambulant: 15%

  • Hospitalization: 30%

  • Total: 100%

Patient Location and Destination Percentages

These three percentages operate independently and control specific aspects of patient missions:

Patient Hospitalization From Home Percent

When a patient is being hospitalized, this percentage determines the probability that the pickup location is the patient's home (rather than a nursing home, outpatient center, or medical practice).

  • Applies only to hospitalization missions (not transfers or discharges)

  • Probability-based: Higher percentage = more missions start at home addresses

  • Remaining percentage (100 - value) = pickup from institutional locations

Typical Range: 60-80%

Patient Hospital Discharge To Nursing Home Percent

When a patient is discharged from the hospital, this percentage determines the probability that the destination is a nursing home or rehabilitation clinic (rather than returning home).

  • Applies only to hospital discharge missions

  • If triggered: 85% nursing home, 15% rehabilitation clinic

  • Remaining percentage (100 - value) = transport home

Typical Range: 15-30%

Patient Pickup Immediately Percent

Determines the percentage of patient transport missions that have NO pickup deadline (immediate pickup expected).

  • This percentage = missions without time constraints (urgent)

  • Remaining percentage (100 - value) = missions with pickup deadlines of 14-180 minutes

  • Affects mission planning and unit dispatch priorities

Typical Range: 10-25%

  • Higher percentage = more immediate/urgent patient transports

  • Lower percentage = more scheduled transports with planning flexibility

  • Affects how dispatchers prioritize and plan unit assignments

Weekend Mission Load Reduction

These settings allow you to reduce mission frequency on Saturdays and Sundays to simulate realistic weekend call volumes.

All percentage values are 0-100, where:

  • 100% = No reduction (normal mission load)

  • 50% = Half the normal mission load

  • 0% = No missions of this type generate on that day

Saturday Reduction Settings

  • Reduce Ambulance Saturday Percent: Reduces urgent ambulance missions (AmbulanceUrgent and AmbulanceUrgentWithDoctor) on Saturdays.

    • Typical Range: 70-90% (slight reduction from weekdays)

  • Reduce Patient Saturday Percent: Reduces regular patient transport missions (AmbulanceRegular) on Saturdays.

    • Typical Range: 40-70% (significant reduction due to fewer scheduled appointments)

  • Reduce ICU Transfer Saturday Percent: Reduces intensive care unit transfer missions on Saturdays.

    • Typical Range: 80-100% (ICU transfers remain relatively constant)

Sunday Reduction Settings

  • Reduce Ambulance Sunday Percent: Reduces urgent ambulance missions on Sundays.

    • Typical Range: 65-85% (moderate reduction)

  • Reduce Patient Sunday Percent: Reduces regular patient transport missions on Sundays.

    • Typical Range: 20-50% (major reduction - fewer scheduled transports on Sundays)

  • Reduce ICU Transfer Sunday Percent: Reduces intensive care unit transfer missions on Sundays.

    • Typical Range: 80-100%

How Weekend Reduction Works

  1. The Event Planner checks each hour during simulation

  2. If the current day is Saturday or Sunday, it retrieves the appropriate reduction percentages

  3. The base mission amount for that hour is multiplied by the reduction percentage:

    • adjustedAmount = baseAmount × reductionPercent / 100

  4. If reduction is 0%, missions of that type are completely prevented on that day

Example:

  • Base patient transport rate: 5 missions/hour on weekdays

  • Reduce Patient Saturday Percent: 60%

  • Saturday rate: 5 × 0.60 = 3 missions/hour

Recommendations:

  • Urban dispatch centers: Moderate reductions (70-90% for urgent, 40-60% for patient)

  • Rural dispatch centers: Greater reductions (60-80% for urgent, 20-40% for patient)

  • 24/7 facilities: Minimal reductions (90-100% across the board)

Response Times

Response time settings control how quickly units react to dispatch orders. These are delay times in seconds between receiving a dispatch and actually departing.

Non-Volunteer Response Times

Response Time Non-Volunteer Min
​Range: 10-1,000 seconds
​Typical Range: 30-60 seconds

Purpose: Minimum response delay for professional/full-time units (hauptamtlich).

Response Time Non-Volunteer Max
​Range: 10-100,000 seconds
​Typical Range: 60-120 seconds

Purpose: Maximum response delay for professional/full-time units.

Volunteer Response Times

Response Time Volunteer Min
​Range: 10-1,000 seconds
​Typical Range: 60-120 seconds

Purpose: Minimum response delay for volunteer units (ehrenamtlich).

Response Time Volunteer Max
​Range: 10-100,000 seconds
​Typical Range: 120-300 seconds

Purpose: Maximum response delay for volunteer units.

How Response Times Work

  1. When a unit receives a dispatch order, the system checks if it's a volunteer or non-volunteer unit

  2. A random delay is generated between Min and Max seconds for that unit type

  3. Additional randomization (0-60 seconds) is added for subsequent units from the same station

  4. The unit waits this calculated delay period before departing to the scene

  5. This simulates real-world turnout time (gear up, vehicle check, departure preparation)

Recommended Settings:

Dispatch Center Type

Non-Vol Min

Non-Vol Max

Vol Min

Vol Max

Urban Professional

30s

60s

N/A

N/A

Mixed Urban

30s

60s

90s

180s

Rural Volunteer

45s

90s

120s

300s

Vehicle Speed Settings

These settings control how quickly vehicles move during simulation, affecting arrival times and mission pacing. All values are percentage multipliers of base driving speeds.

Speed Without Siren

Unit Speed Car Percent

Speed multiplier for car-type units driving without sirens activated.

Examples:

  • 100% = Normal speed (base driving time)

  • 75% = 25% slower than normal (realistic for traffic)

  • 125% = 25% faster than normal

Unit Speed Truck Percent

Speed multiplier for truck-type units (fire trucks, larger ambulances) driving without sirens. Typically set 10-20% lower than car speed to reflect larger vehicle constraints

Speed With Siren

Unit Speed Car Siren Percent

Speed multiplier for car-type units driving with sirens/lights activated. Typically set 10-30% higher than non-siren speed to simulate emergency response advantages.

Unit Speed Truck Siren Percent

Speed multiplier for truck-type units driving with sirens/lights activated. Typically set 10-20% higher than non-siren truck speed

How Vehicle Speeds Work

  1. Route calculation determines base driving duration for each route segment

  2. The simulation adjusts the drive duration based on:

    • Unit type (car vs. truck)

    • Siren status (on vs. off)

    • Configured speed percentage

  3. Calculation: adjusted_duration = base_duration × duration_multiplier

  4. Duration multiplier calculation:

    • If percentage > 100%: multiplier = 1 + (percentage - 100) / 100

    • If percentage ≤ 100%: multiplier = 1 - (100 - percentage) / 100

  5. All route segments are adjusted before travel begins

  6. Estimated arrival times sum the adjusted segment durations

Note on Speed Percentages: Despite being labeled "Speed %", these settings actually function as duration multipliers, not speed multipliers. The behavior is:

  • Higher percentage = Longer duration = Slower arrival

  • Lower percentage = Shorter duration = Faster arrival

Examples:

  • 60-second base route at 50% setting = 60 × 0.50 = 30 seconds (FASTER - half the time)

  • 60-second base route at 100% setting = 60 × 1.00 = 60 seconds (NORMAL - unchanged)

  • 60-second base route at 150% setting = 60 × 1.50 = 90 seconds (SLOWER - 1.5x the time)

  • 60-second base route at 200% setting = 60 × 2.00 = 120 seconds (SLOWEST - double the time)

Recommended Settings:

Scenario

Car

Truck

Car+Siren

Truck+Siren

Description

Fast-Paced Action

60%

70%

50%

60%

Quick arrival times

Balanced

100%

100%

80%

90%

Standard pacing

Realistic Urban Traffic

140%

150%

110%

120%

Slower, more realistic

Heavy Traffic

180%

200%

150%

170%

Significant delays

Standby Position Options

Unit Status When Unit Is On Standby Location

Defines which status code is displayed for units positioned at their assigned standby location.

Available Status Codes:

Code

Status Name

Description

0

UrgentSpeakRequest

Unit needs urgent communication

1

OnDutyAlongWay

On duty, en route or stationed (default)

2

OnDuty

General on-duty status

3

OnTheWay

Currently driving to a location

4

OnScene

Arrived at scene/operation

5

SpeakRequest

Unit requests to speak with dispatch

6

NotOnDuty

Off-duty/unavailable

7

DriveToDestination

Transporting to destination

8

ArrivedAtDestination

Completed transport, at destination

9

Individual

Custom/individual status

Recommendations:

  • Status 1 (OnDutyAlongWay): Most common, indicates ready for dispatch

  • Status 2 (OnDuty): Clear "ready" signal for dispatch operations

  • Status 9 (Individual): For custom dispatch center workflows

Public Visibility

Is Public

Controls whether your dispatch center is publicly visible and accessible in the community directory.

When ENABLED (Public):

  • Appears in the public browse/directory listing

  • Can be discovered by any user browsing dispatch centers

  • Automatically creates a Discourse forum topic in country-specific category

  • Forum topic is displayed and unarchived

  • Indexed in search systems for easy discovery

  • Anyone can view and potentially join sessions (depending on other settings)

When DISABLED (Private):

  • NOT visible in public directory

  • Only accessible by admins or owner

  • No Discourse forum topic created (or existing topic is hidden/archived)

  • Not indexed in search

Recommendations:

  • Keep private during initial setup and testing

  • Switch to public only when fully configured and tested

  • Monitor for automatic visibility changes due to configuration errors

Advanced Options

These advanced toggles control specific operational behaviors and dispatch protocols. Each option can be independently enabled or disabled to customize your dispatch center's functionality.

Status 6 Is Set By Dispatch Center

Specifies that Status 6 (NotOnDuty) will be set only by the dispatch center, not by units themselves.

When Enabled:

  • Units cannot self-report as off-duty, they will call dispatch instead

  • Dispatch center operators have exclusive control over off-duty status

  • Prevents unauthorized unit availability changes

Use Case: Strict dispatch centers with centralized shift management

Units Use Only Status 5 For Speak Request

Restricts units to always use Status 5 when making speak requests to the dispatch center.

When Enabled:

  • Standardizes communication protocol

  • Units must use Status 5 for all dispatch communication requests

  • Eliminates ambiguity in speak request handling

Use Case: Dispatch centers with formal communication protocols

Doctor Uses Siren With Status 7

Enables doctors to use sirens when assigned Status 7 (DriveToDestination).

When Enabled:

  • Doctor units can activate sirens during patient transport

  • Faster transport times for critical patients

  • Reflects emergency medical doctor protocols

Use Case: Dispatch centers with physician response vehicles that transport patients

Units Will Be Suggested In Status 8

Ensures units are suggested in dispatch operations when they reach Status 8 (ArrivedAtDestination).

When Enabled:

  • Units at destination locations remain available for suggestions

  • Allows quick re-dispatch from current location

  • Improves unit utilization efficiency

Use Case: High-volume dispatch centers needing maximum unit availability

Units Tell Patient Destination Verbal

Requires units to verbally inform the dispatch center of their transport destination.

When Enabled:

  • Units must announce destination via radio

  • Adds communication step to transport workflow

  • Increases realism and coordination requirements

Use Case: Dispatch centers emphasizing communication protocols and coordination

Always Use Verbal Call Sign

Mandates the use of verbal call signs for all communications.

When Enabled:

  • All unit communications require proper call sign usage

  • Enforces radio protocol standards

Include Keyword Equipment Even If Dispatch Order Found

Read more here ...

Start Session With Ambulance Regular

Initiates sessions assuming regular ambulance service unless specified otherwise.

When Enabled:

  • New sessions default to regular ambulance operations

  • Faster session startup for routine operations

  • Reduces configuration steps for common scenarios

Use Case: Dispatch centers primarily handling regular patient transports

Is Create Operation On Call Accept Disabled

Disables automatic creation of operations upon call acceptance.

When Enabled:

  • Call acceptance does NOT automatically create an operation

  • Operators must manually create operations

  • Provides more control over operation creation workflow

When Disabled (default):

  • Operations automatically created when calls are accepted

  • Streamlined workflow for standard responses

Use Case: Dispatch centers needing manual review before operation creation

Operation Location From Call Known POI

Uses known points of interest as the default operation location for calls.

When Enabled:

  • Operations default to POI locations when available

  • Faster location entry for frequent locations

  • Reduces manual address entry

Use Case: Dispatch centers with many recurring locations (hospitals, nursing homes, etc.)

Units Drive To Standby Position In Status 3

Resources in drive to their assigned standby area in Status 3.

When Disabled:

  • Units driving to standby position in status 1

Units Drive Back To Standby Position Until Abort Send

Resources continue driving back to the standby area until an abort command is received.

When Enabled:

  • Units persistently return to standby until explicitly aborted

  • Ensures units reach standby positions

  • Requires manual intervention to change course

Use Case: Strict standby protocols with explicit command control

Unit GPS Position Interpolation

GPS positions are interpolated to avoid units appearing "stuck" on routes with few coordinate points.

When Enabled:

  • Unit positions update more frequently on long route stretches

  • Smoother visual movement on map

Use Case: Address packages with limited coordinate detail or long rural routes

Disable Advanced Mobile Location

Disables Advanced Mobile Location (AML) data usage.

When Enabled:

  • AML data is not used for caller location

  • Standard address entry required

  • May be required for privacy or technical reasons

Use Case: Dispatch centers not using AML or privacy-focused configurations

Units Off Duty Will Respond

Units marked off-duty will still respond to dispatches.

When Enabled:

  • Off-duty units remain in suggestion pools

  • Increases available unit pool

  • Simulates callback/volunteer response

Use Case: Volunteer dispatch centers or emergency callback scenarios

Disable Doctor Based EMS

Disables physician-based emergency medical services (doctors will not be required).

When Enabled:

  • No doctor units are required in any case

  • EMS operations do not rely on physicians

  • Simulates non-physician EMS systems

Use Case: Dispatch centers operating paramedic-only EMS systems

Group Districts By ZIP Code

Groups districts by ZIP code within a city.

When Enabled:

  • Multiple districts with same ZIP code consolidate into one entry

  • Example: "Breitenberg (37115)", "Brochthausen (37115)", "Duderstadt (37115)" become "Duderstadt (37115)"

  • All streets from grouped districts appear together

Use Case: Address packages with granular district data that need simplification

Read more ...

Group Districts By Name

Groups districts by name within each city, consolidating different postcodes.

When Enabled:

  • Districts with same name but different ZIP codes consolidate

  • Example: "London Borough of Ealing" (W7 1JJ, W7 2AA, W7 3BB) becomes one entry

  • Groups by: CityId + DistrictName (ignores ZIP variations)

Use Case: International address packages with multiple ZIP codes per district

Read more ...

Equipment Suggester Includes Previous Suggester Results

Read more ...

Custom Equipment

Define custom, context-specific equipment types for your dispatch center beyond the standard predefined equipment types.

Maximum Slots: 20 custom equipment slots (numbered 1-20)

What Custom Equipment Does:

  • Assists in the suggestion process during dispatch operations

  • Does NOT directly influence simulation outcomes

  • Serves as tags for unit categorization and suggestions before dispatch

  • Allows equipment categorization beyond standard types

How to Configure:

  1. Each slot has a text input for the equipment name

  2. Enter descriptive names for equipment specific to your region/operation

  3. Leave unused slots empty

  4. Assign custom equipment to units in Unit configuration

Examples:

  • Slot 1: "Kindernotarzt" (Pediatric Emergency Doctor)

  • Slot 2: "Rettungshubschrauber" (Air Rescue Helicopter)

  • Slot 3: "Atemschutzgerät" (Breathing Apparatus)

  • Slot 4: "Höhenrettung" (High-Angle Rescue)

Unit Assignment:

  • Units can be assigned custom equipment in their configuration

  • Custom equipment appears in dispatch suggestions

  • Helps dispatchers identify specialized capabilities

Technical Details:

  • Custom equipment slots map to UnitEquipment enum values Custom1 through Custom20

  • Slot number + 24 = enum index (e.g., slot 1 → Custom1 = enum 25)

  • Each custom equipment has: ID, Number (1-20), Text (display name)

Validation:

  • Duplicate slot numbers within a dispatch center are prevented

  • Slot numbers must be 1-20

  • Empty slots are not allowed between

Administrators

Owner-only feature (requires dispatch center owner access). Allows to manage who has administrative access to configure and manage the dispatch center.

Adding Administrators

How to Add:

  1. Click "Add Administrator" button

  2. Modal opens with dropdown of your friends

  3. Select a friend from the list

  4. Friend is added as administrator

Requirements:

  • Can only add users from your friends list

  • User must accept friend request first

  • Recommended dispatch centers have restrictions on owner changes

Administrator Permissions: Administrators can:

  • Edit all general settings

  • Configure mission loads

  • Manage units, areas, and POIs

  • Import data

  • View statistics

  • Manage keywords and task templates

Administrator Limitations:

  • Cannot delete the dispatch center (owner-only)

  • Cannot remove the owner

  • Cannot transfer ownership (owner-only)

Recommendations:

  • Add trusted collaborators who understand dispatch center configuration

  • Clearly communicate roles and responsibilities

  • Review administrator list periodically

  • Remove administrators who are no longer active

Header Image

Owner-only feature. Upload a custom header image for your dispatch center that appears at the top of the dispatch center pages.

File Requirements:

  • Maximum size: 2 MB

  • File types: Image files only (PNG, JPG, JPEG, GIF, etc.)

How to Upload:

  1. Click the file upload area or drag and drop an image

  2. Select image file from your computer

  3. Preview appears before upload

  4. Image is processed and displayed as header

Image Display:

  • Appears at the top of dispatch center pages

  • Visible to all users viewing the dispatch center

  • Can be changed or removed by owner at any time

Recommendations:

  • Use high-quality images representing your dispatch center

  • Consider logo, emblem, or regional imagery

  • Ensure image is clear and professional if dispatch center is public

  • Optimize image size to stay under 2 MB limit

  • Use appropriate aspect ratio for header display

Delete All Reviews

Removes all user reviews/comments from your dispatch center.

Impact:

  • Removes all review content

  • Removes all ratings

  • Resets review count to zero

  • Does NOT affect dispatch center configuration or gameplay

Use Cases:

  • Starting fresh after major changes

  • Removing inappropriate or outdated feedback

  • Privacy concerns with old comments

Caution: This action cannot be undone. All review history is permanently lost.

Did this answer your question?