FleetCore.Garage v1.0.0

Physical Diagnostics, Maintenance & Repair Locations for FleetCore

Created & Developed by LaVante Pettigrew

FleetCore.Garage brings FleetCore’s persistent vehicle simulation into physical service locations throughout the game world.

FleetCore recognizes your vehicle.

FleetCore.Garage helps you keep it in service.

Pull a FleetCore-tracked vehicle into a supported service location, run a diagnostic inspection, select an available service, and allow the Garage to repair or maintain the same persistent vehicle FleetCore has been tracking throughout your patrol.

This is an optional addon.

FleetCore.Garage is not required to use FleetCore.

Install it only if you want physical service-location gameplay connected directly to FleetCore’s mechanical simulation.

What FleetCore.Garage Does

FleetCore.Garage provides physical locations where supported FleetCore vehicles can receive diagnostics, maintenance, and repairs.

Instead of repairing every mechanical problem through a trainer or instantly resetting the vehicle, Garage turns service into part of the patrol experience.

The basic service process is:

FleetCore recognizes the vehicle
        ↓
Garage detects the service location
        ↓
Vehicle enters an authorized service area
        ↓
Garage requests a FleetCore vehicle snapshot
        ↓
Available diagnostics and services are displayed
        ↓
Player selects an authorized service
        ↓
Vehicle is secured and shut down
        ↓
Service is performed
        ↓
FleetCore updates the persistent vehicle
        ↓
Garage creates a service record
        ↓
Vehicle returns to service

The vehicle leaving the Garage is the same persistent vehicle that entered—with its existing identity, mileage, operational history, and updated mechanical condition.

Optional Addon — Not a Requirement

FleetCore.Garage is a separate addon for FleetCore Core.

FleetCore works independently.

You do not need FleetCore.Garage to use:

• FleetCore’s mechanical simulation

• Persistent vehicle condition

• Fuel consumption

• Vehicle profiles

• Tire and suspension simulation

• Mechanical failures

• Vehicle history

• Shift reports

• The FleetCore Control Center

• The FleetCore Vehicle Monitor

Install FleetCore.Garage only if you want to bring those systems into physical service departments and repair locations.

FleetCore.Garage requires:

FleetCore Core v1.0.1

Garage Bridge API 1.3

FleetCore.Garage cannot operate without a compatible installation of FleetCore Core.

Current Service Network

FleetCore.Garage v1.0.0 includes a tested network of full-service, tire-service, and electrical-service locations.

Mission Row Fleet Service Department

Mission Row is the central FleetCore.Garage service facility.

It includes:

• Four functioning service bays

• Physical garage-door access

• Full vehicle diagnostics

• Comprehensive maintenance

• Mechanical repairs

• Tire service

• Electrical service

• Fluid service

• Cosmetic-damage repair

• Full-service maintenance

• Persistent service records

Each Mission Row bay is independently recognized.

You can pull into any available supported bay and begin the Garage interaction without being restricted to one exact parking position.

Mission Row is intended to serve as the primary full-service department for the FleetCore network.

Sandy Shores Tire Service

The Sandy Shores location provides tire-focused service for vehicles operating in and around Blaine County.

Available service can include:

• Tire diagnostics

• Tire-pressure service

• Tire repair

• Tire replacement

• Tire rotation

• Related tire maintenance

This is a specialized location and does not provide every service available at Mission Row.

Paleto Tire Service

Paleto includes a second specialized tire-service location for vehicles operating in northern Blaine County.

Available service can include:

• Tire diagnostics

• Tire-pressure service

• Tire repair

• Tire replacement

• Tire rotation

• Related tire maintenance

Like Sandy Shores, the Paleto tire shop is limited to its assigned service capabilities.

Paleto Municipal Electrical Service

Paleto Municipal provides electrical-system diagnostics and service.

Available service can include FleetCore systems classified as electrical, such as:

• Battery condition

• Charging-system condition

• Alternator service

• Starter service

• Related electrical repairs

Paleto Municipal does not perform every mechanical service available at Mission Row.

Location-Specific Service

Not every Garage location can repair every problem.

FleetCore.Garage uses service capabilities assigned to each location.

A tire shop provides tire service.

An electrical facility provides electrical service.

Mission Row provides the complete service department.

This prevents every location from functioning as an identical repair marker and gives each part of the Garage network a defined operational role.

If the vehicle requires a service that is not available at the current location, it must be taken to an appropriate facility.

Vehicle Recognition

FleetCore.Garage recognizes the vehicle through FleetCore Core.

Garage does not create a second, independent copy of the vehicle’s condition.

Through Garage Bridge API 1.3, Garage can safely request information such as:

• Persistent vehicle identity

• Vehicle display name

• Vehicle role

• Odometer mileage

• Fuel level

• Battery and charging condition

• Starter condition

• Cooling-system condition

• Fluid condition

• Engine and transmission condition

• Tire condition

• Suspension condition

• Maintenance requirements

• Other supported FleetCore information

FleetCore remains the authority over the vehicle.

Garage provides the location, diagnostic workflow, service process, and service record.

Garage Diagnostics

When a recognized vehicle enters an authorized service area, FleetCore.Garage can request a diagnostic snapshot from FleetCore.

Diagnostics allow Garage to identify:

• Active mechanical problems

• Maintenance requirements

• Worn systems

• Damaged components

• Services available at the current location

• Services requiring a different location

• The vehicle’s current overall service condition

The available repair options are based on both:

1. The condition reported by FleetCore.

2. The capabilities assigned to the current Garage location.

Garage does not independently invent or overwrite FleetCore vehicle condition.

Service Sessions

FleetCore.Garage uses timed service sessions instead of applying every repair instantly.

When service begins:

• The selected vehicle is secured in the service area

• The engine is forced completely off

• The vehicle is prevented from repeatedly attempting to restart

• Player driving controls are restricted as necessary

• Another Garage service cannot begin while the current service is active

• The selected service runs for its configured duration

The vehicle remains shut down until the service has been completed or the active session has otherwise ended.

When service finishes:

• FleetCore applies the authorized maintenance or repair

• The vehicle is released

• Normal engine operation can resume

• The updated condition persists

• Garage creates a service record

• FleetCore can record the completed Garage activity

The service lock applies to all Garage service categories.

Available Service Categories

Depending on the vehicle’s condition and the current location, Garage service can include:

• Full-service maintenance

• Battery service

• Alternator service

• Starter service

• Electrical-system repair

• Cooling-system service

• Engine-oil service

• Transmission-fluid service

• Brake-fluid service

• Washer-fluid service

• Tire service

• Tire rotation

• Tire repair or replacement

• Suspension service

• Engine repair

• Transmission repair

• Fuel-system service

• Cosmetic-damage repair

• Other authorized FleetCore maintenance

The exact services shown depend on what the location is permitted to perform and what the vehicle currently needs.

Cosmetic-Damage Repair

FleetCore.Garage can repair visible GTA V vehicle damage as part of supported service.

This allows a vehicle damaged during a collision, pursuit, traffic stop, or patrol incident to be returned in pristine cosmetic condition when the selected Garage service includes body repair.

Cosmetic repair does not replace FleetCore’s persistent mechanical system.

Garage coordinates both sides of the process:

• GTA V cosmetic condition is repaired

• Authorized FleetCore mechanical service is applied

• The service is recorded

This allows the vehicle to leave the service department both visually repaired and mechanically updated.

Service Records

FleetCore.Garage creates a service record when a Garage service is completed.

Service records can identify information such as:

• Vehicle identity

• Vehicle display name

• Vehicle role

• Service location

• Service category

• Service performed

• Service date and time

• Odometer mileage

• Condition before service

• Condition after service

• Completed maintenance or repairs

Garage records are stored separately from FleetCore’s normal shift reports while remaining connected to the same persistent vehicle.

Garage service activity can also appear in:

• FleetCore vehicle history

• FleetCore shift reports

• Structured FleetCore event data

This creates a connected operational and maintenance history.

FleetCore records what happened during the patrol.

FleetCore.Garage records what was done to return the vehicle to service.

Garage HUD & Interaction Design

FleetCore.Garage uses contextual bottom-center information instead of permanently occupying FleetCore’s primary diagnostic area.

Garage information can identify:

• The active service location

• The current service bay

• Vehicle-recognition status

• Available interaction

• Active service

• Service progress

• Service completion

• Reasons service cannot begin

Example location displays can include:

FLEETCORE GARAGE • MISSION ROW — BAY 4

FLEETCORE GARAGE • PALETO MUNICIPAL

FLEETCORE GARAGE • SANDY SHORES TIRE SERVICE

The Garage interface is designed to appear when it is relevant and remain out of the way during normal patrol gameplay.

Map Blips & World Markers

FleetCore.Garage includes:

• Map blips for registered Garage locations

• Proximity-based world markers

• Location-specific interaction areas

• Garage-bay recognition

• Entry and exit detection

World markers are proximity-based and do not need to remain visible from across the map.

Map and world-marker behavior can be configured through the Garage INI.

Garage also performs cleanup when the addon unloads so its blips, markers, service sessions, and other active resources are not intentionally left behind.

Separate Onboarding

FleetCore.Garage has its own first-run introduction.

During a fresh installation:

1. FleetCore Core loads first.

2. FleetCore onboarding must be completed.

3. Garage waits in a dormant state.

4. FleetCore authorizes the addon.

5. Garage presents its own onboarding.

6. Garage initializes after acknowledgment.

The handoff can occur during the same game session.

A GTA V restart is not required after completing FleetCore’s introduction.

Garage onboarding is tracked separately from FleetCore onboarding. Resetting or introducing a future major FleetCore module does not require the entire FleetCore system to repeat the same onboarding process.

Enable or Disable Garage

FleetCore.Garage can be enabled or disabled through:

plugins\LSPDFR\FleetCore\Garage\FleetCore.Garage.ini

Disabling Garage prevents its normal service-location gameplay from initializing.

FleetCore Core continues operating normally.

The setting is reversible. Garage can be re-enabled through its configuration without permanently changing FleetCore’s vehicle data.

If the Garage INI is missing, FleetCore.Garage can generate a new default configuration file.

Configuration

FleetCore.Garage uses its own configuration independently of FleetCore Core.

The main Garage configuration is located at:

plugins\LSPDFR\FleetCore\Garage\FleetCore.Garage.ini

Configuration areas include:

• Garage enabled or disabled state

• Garage onboarding acknowledgment

• Debug behavior

• Map blips

• World markers

• Marker visibility and proximity

• Service behavior

• Other Garage-specific options

FleetCore Core and FleetCore.Garage maintain separate onboarding and configuration states.

Changing Garage settings does not require replacing the main FleetCore Core INI.

Installation

FleetCore.Garage requires an existing working installation of:

• Grand Theft Auto V

• RAGE Plugin Hook

• LSPDFR

• FleetCore Core v1.0.1

• Garage Bridge API 1.3

• Microsoft .NET Framework 4.8

To install FleetCore.Garage:

1. Install and verify FleetCore Core v1.0.1.

2. Copy the included plugins folder into the main Grand Theft Auto V directory.

3. Preserve the packaged folder structure.

4. Confirm that both plugin DLLs are present.

5. Start GTA V through RAGE Plugin Hook.

6. Go on duty.

7. Complete FleetCore onboarding if it has not already been acknowledged.

8. Complete the separate FleetCore.Garage introduction.

9. Bring a FleetCore-recognized vehicle to a supported service location.

The resulting installation should include:

Grand Theft Auto V
└── plugins
    └── LSPDFR
        ├── FleetCore.dll
        ├── FleetCore.Garage.dll
        └── FleetCore
            ├── FleetCore.ini
            └── Garage
                └── FleetCore.Garage.ini

Additional Garage data and record folders are created or included as required by the packaged release.

Uninstallation

FleetCore.Garage can be removed without removing FleetCore Core.

To stop using Garage:

1. Allow any active service session to finish.

2. Unload the plugins or close the game.

3. Remove FleetCore.Garage.dll.

4. Remove the Garage configuration or data folder only if you do not want to preserve Garage settings and service records.

Do not remove FleetCore.dll or the main FleetCore data directory if you want to continue using FleetCore Core and retain persistent vehicle information.

Release Testing

Before release, FleetCore.Garage v1.0.0 was tested for:

• Separate addon loading

• FleetCore dependency detection

• Missing-Core behavior

• Dormant Garage waiting

• Same-session FleetCore-to-Garage handoff

• Separate Garage onboarding

• Startup branding

• Garage enable and disable behavior

• Reversible configuration settings

• Automatic INI regeneration

• Location detection

• Entry and exit detection

• All four Mission Row service bays

• Sandy Shores tire service

• Paleto tire service

• Paleto Municipal electrical service

• Vehicle recognition

• Vanilla and addon vehicle handling

• Unknown vehicle handling

• Garage diagnostics

• Full-service maintenance

• Tire service

• Electrical service

• Cosmetic-damage repair

• Timed service sessions

• Engine shutdown during service

• Restart-attempt prevention

• Multiple-service prevention

• Service completion

• Persistent FleetCore state changes

• Service-record generation

• FleetCore vehicle-history integration

• FleetCore shift-report integration

• Map blips

• World markers

• Plugin unload cleanup

• Complete patrol and service-network testing

The final comprehensive test included damaging multiple vehicles, repairing an additional collision vehicle, taking the primary persistent vehicle through the complete Garage network, testing location-specific services, completing a full Mission Row service in a randomly selected bay, generating vehicle and Garage records, ending the tour of duty, and unloading the plugins.

All primary in-game release tests passed.

Release Notice

FleetCore.Garage v1.0.0 is the initial public release.

Although Garage has been comprehensively tested, different vehicle packs, plugin combinations, configurations, game builds, and unusual gameplay situations may reveal behavior not encountered during development.

If you encounter a problem, please provide:

What happened

Which Garage location and service bay you were using

Which service you selected

What vehicle you were using

Whether FleetCore recognized the vehicle correctly

What happened immediately before the problem

Whether the problem can be reproduced

Relevant RagePluginHook.log information

Relevant Garage service record

Other vehicle, repair, or gameplay plugins that may be involved

The more information provided, the easier the problem will be to reproduce and resolve.

Known Limitations — v1.0.0

Player Must Remain With the Active Vehicle

The current service workflow is centered on the player and the vehicle occupying the active service area.

A future update may allow Garage to continue recognizing and servicing the selected vehicle after the player exits and walks away, followed by a service-complete notification.

That behavior is not part of v1.0.0.

Supported Locations

Only the service locations registered in the current Garage network are available.

Additional garages, departments, and specialized facilities may be added later.

External MDT Integration

Garage service records are stored through FleetCore’s own reporting structure.

Direct external filing with Nexus MDT, pdComp, or another police-computer system is not currently implemented.

FleetCore Dependency

FleetCore.Garage cannot function as a standalone repair plugin.

It requires a compatible version of FleetCore Core because FleetCore owns the persistent vehicle state that Garage reads and services.

Planned Updates & Future Development

Possible future development may include:

• Vehicle-centered service sessions

• Continued service after the player exits

• Service-complete notifications away from the bay

• Additional service departments

• Additional specialized repair locations

• Expanded diagnostic information

• Additional service categories

• Vehicles being placed out of service

• More detailed Garage service records

• Fleet-management tools

• Additional marker and blip options

• External MDT or reporting integration

• Additional addon compatibility

• Quality-of-life improvements

Planned features are not guaranteed for a specific version or timeframe.

Changelog

v1.0.0 — Initial Public Release

Initial release of FleetCore.Garage.

Includes:

• Separate optional addon architecture

• Separate Garage DLL

• FleetCore Core dependency validation

• Garage Bridge API 1.3 support

• Dormant wait for FleetCore authorization

• Same-session onboarding handoff

• Separate Garage onboarding

• Separate Garage configuration

• Automatic Garage INI regeneration

• Garage enable and disable option

• Registered service-location network

• Four Mission Row full-service bays

• Sandy Shores tire service

• Paleto tire service

• Paleto Municipal electrical service

• Location-specific service authorization

• Proximity location detection

• Entry and exit detection

• FleetCore vehicle recognition

• FleetCore vehicle diagnostics

• Timed service sessions

• Complete engine shutdown during service

• Vehicle immobilization during service

• Prevention of repeated engine-start attempts

• Prevention of overlapping service sessions

• Full-service maintenance

• Tire service

• Electrical service

• Cosmetic-damage repair

• Persistent FleetCore condition updates

• Garage service records

• FleetCore vehicle-history integration

• FleetCore shift-report integration

• Map blips

• Proximity world markers

• Plugin unload cleanup

• Clean-install support

Credits

Created & Developed by LaVante Pettigrew

FleetCore.Garage was designed, developed, and tested as the physical service-department counterpart to FleetCore’s persistent vehicle simulation.

FleetCore makes the vehicle matter.

FleetCore.Garage helps keep it on the road.

Thank you to everyone who downloads, tests, reports problems, and helps the FleetCore system continue to grow.

FleetCore.Garage v1.0.0

Created by LaVante Pettigrew

Diagnostics. Service. Repair. Return to duty.

FleetCore recognizes your vehicle. Garage keeps it in service.