Supervisor Pettigrew

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.
FleetCore.Garage Demonstration Video
A complete FleetCore.Garage demonstration video is now available.
Watch the video to see FleetCore.Garage’s physical service locations, vehicle recognition, diagnostics, location-specific repairs, timed service sessions, cosmetic-damage repair, service records, and FleetCore Core integration in action.
Watch the FleetCore.Garage Demonstration Video on YouTube
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:
The condition reported by FleetCore.
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:
FleetCore Core loads first.
FleetCore onboarding must be completed.
Garage waits in a dormant state.
FleetCore authorizes the addon.
Garage presents its own onboarding.
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:
Install and verify FleetCore Core v1.0.1.
Copy the included plugins folder into the main Grand Theft Auto V directory.
Preserve the packaged folder structure.
Confirm that both plugin DLLs are present.
Start GTA V through RAGE Plugin Hook.
Go on duty.
Complete FleetCore onboarding if it has not already been acknowledged.
Complete the separate FleetCore.Garage introduction.
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:
Allow any active service session to finish.
Unload the plugins or close the game.
Remove FleetCore.Garage.dll.
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.

FleetCore v1.0.1
Vehicle Management, Maintenance & Simulation for LSPDFR
Created & Developed by LaVante Pettigrew
FleetCore changes the way vehicles work during an LSPDFR patrol.
Instead of treating every police vehicle as a disposable GTA vehicle that is effectively brand new every time you spawn it, FleetCore gives vehicles their own condition, mileage, maintenance needs, mechanical systems, service history, damage consequences, fuel use, environmental exposure, and operational history.
Your car matters now. DON'T WRECK IT.
Drive it hard, and components wear. Neglect maintenance, and problems can develop. Damage the vehicle, and that damage can affect other systems. Maintain it properly, and the vehicle can remain in service across multiple tours of duty.
The vehicle you finish a shift with is the vehicle you return to later—including its mileage, fuel level, mechanical condition, maintenance needs, damage history, and previous FleetCore events.
FleetCore is designed for players who want the patrol vehicle itself to become part of the simulation.
FleetCore was developed around my custom Florida-based LSPDFR build, but FleetCore itself is agency- and vehicle-pack independent. You do not need a Florida build to use it.
FleetCore Demonstration Video
A complete FleetCore demonstration video is now available.
Watch the video to see FleetCore’s persistent vehicle simulation, interconnected mechanical systems, diagnostic features, vehicle profiles, reporting, and optional FleetCore.Garage integration in action.
Watch the FleetCore Demonstration Video on YouTube
Vehicle Systems
FleetCore currently simulates:
Battery condition and electrical drain
Alternator condition and charging output
Starter condition and failed-start behavior
Cooling system
Radiator
Water pump
Thermostat
Cooling-fan behavior
Engine temperature
Engine oil
Oil pressure
Transmission fluid
Brake fluid and brake hydraulics
Washer fluid
Timing system
Air conditioning
Tires and individual tire pressure
Tire tread and wear
Spare tire
Suspension
Fuel level and consumption
Fuel pump, filter, tank, and lines
Vehicle mileage
Vehicle inventory
Vehicle damage
Fluid leaks
Burnout-related tire wear
Terrain-related wear
Weather and environmental influence
These systems are not intended to operate as isolated status bars.
FleetCore’s systems interact with the vehicle and with each other.
A weak alternator may stop properly charging the battery. A cooling-system failure can lead to overheating. Poor lubrication can damage the engine. Low tire pressure can accelerate tire wear. Suspension damage can place additional stress on the tires. Fuel-system failures can affect fuel delivery. Electrical condition can determine whether the vehicle continues running—or starts at all.
Severe damage, overheating, neglected maintenance, and continued operation with active faults can eventually leave the vehicle unable to continue operating.
The goal is not simply to tell you something is wrong.
Mechanical condition has consequences.
If you neglect the vehicle long enough, there may come a point where you are not driving back to the station.
You are calling a tow truck.
Persistent Vehicles
FleetCore remembers your vehicles.
Vehicle state is written to persistent data so mileage, mechanical condition, maintenance information, fuel state, damage, and other FleetCore information can survive a complete GTA V restart.
This allows the same patrol vehicle to develop over time instead of becoming a brand-new car every time you launch the game.
Each recognized vehicle can retain its own:
Vehicle identity
Odometer mileage
Fuel level
Battery condition
Alternator condition
Starter condition
Engine and transmission condition
Fluid condition
Tire pressure and wear
Suspension condition
Maintenance information
Damage history
Vehicle inventory
Operational history
Garage service activity
Changing vehicles does not erase the condition of the vehicle you left behind. When FleetCore recognizes that vehicle again, its persistent condition is restored.
FleetCore also maintains backup and recovery information for important vehicle and history data so an unreadable persistence file is less likely to result in the loss of an entire fleet record.
Vehicle Profiles
FleetCore supports configurable vehicle profiles through:
VehicleProfiles.json
FleetCore v1.0.1 includes 43 default vehicle profiles, including profiles for custom vehicles and generic vanilla law-enforcement applications.
Vehicle profiles can assign information such as:
Display Name
Vehicle Role
Fuel Tank Capacity
Fuel Consumption
Terrain Capability
Service Profile
Vehicle-specific simulation characteristics
This is especially useful for addon police vehicles.
Instead of FleetCore knowing your car only as a spawn code, you can tell FleetCore what that vehicle represents in your fleet.
Profiles are stored in an editable JSON file, allowing additional supported vehicles to be introduced without rebuilding the plugin.
Build & Vehicle-Pack Flexibility
I developed and extensively tested FleetCore using a dedicated Florida-centered LSPDFR build with custom law-enforcement vehicles and agency-specific vehicle roles.
You do NOT need my Florida build to use FleetCore.
FleetCore is designed to work independently of any particular state, agency, department, or vehicle pack.
The included vehicle profiles can be customized to fit your own setup.
You can change vehicle identities, operational roles, fuel capacities, terrain capabilities, and applicable service profiles to represent the vehicles in your fleet.
Example vehicle roles can include:
Patrol
Traffic Enforcement
Pursuit Intervention
Criminal Interdiction
Unmarked or Ghosted Enforcement
Patrol or Utility
Supervisor
Administrative
Specialized Enforcement
You are not required to use the roles or vehicle identities from my Florida build.
Change them.
Build your own fleet.
FleetCore will use the configured vehicle profile and respond according to the characteristics and service configuration assigned to that vehicle.
FleetCore can therefore be adapted for a highway patrol or state police setup, municipal police department, sheriff’s office, federal fleet, fictional department, or completely custom LSPDFR build.
Your fleet. Your rules. Your simulation.
Vehicle Damage
FleetCore does not treat GTA V’s normal vehicle-repair behavior as a complete mechanical reset.
A trainer or another plugin may repair visible GTA V damage without automatically clearing FleetCore’s persistent mechanical condition.
That means a vehicle can appear cosmetically repaired while still having:
Mechanical damage
Cooling-system problems
Electrical faults
Fluid degradation
Tire wear
Suspension damage
Engine or transmission problems
Overdue maintenance
Vehicle damage can also affect multiple FleetCore systems instead of remaining an isolated body-damage value.
FleetCore is intended to make collisions, pursuits, overheating, neglect, and mechanical failures continue to matter after the immediate event is over.
Fuel & Refueling
FleetCore includes persistent fuel consumption and recognized fuel-station functionality.
Fuel remains associated with the tracked vehicle instead of resetting whenever the player exits the car.
Fuel gameplay includes:
Persistent fuel levels
Vehicle-specific fuel capacities
Configurable fuel-consumption rates
Low-fuel warnings
Fuel leaks
Fuel-system component condition
Engine shutdown when fuel is exhausted
Recognized fuel stations
Configurable refueling controls
The included:
FuelStations.json
contains FleetCore’s recognized fuel-station locations.
Fuel-station interaction may require the vehicle to be stopped with the engine turned off.
Default interaction control:
G — Refuel at a recognized FleetCore fuel station FleetCore v1.0.1 also expands generic vanilla law-enforcement vehicle support so the included fuel and vehicle-profile systems can be adapted more easily to standard LSPDFR fleets.
Tires, Suspension & Terrain
FleetCore monitors tire and suspension condition independently.
Tire gameplay includes:
Individual tire pressure
Pressure loss
Tire wear
Tread condition
Punctures
Blowouts
Burnout-related wear
Tire inflation
Spare-tire inventory
Spare-tire installation
Tire service support
Default roadside controls include:
N — Install spare tire H — Inflate selected tire Suspension condition and terrain exposure can place additional stress on the vehicle and its tires.
Vehicles can also be assigned different terrain capabilities through their profiles, allowing patrol cars, utility vehicles, and off-road-capable units to respond differently to demanding terrain.
Roadside Functions
FleetCore includes roadside-support functionality intended to give you limited options when something goes wrong away from a service location.
Default roadside controls include:
Q — Use jumpbox R — Use emergency fuel can N — Install spare tire H — Inflate selected tire Roadside equipment is not intended to replace proper maintenance or permanent repair.
Sometimes you can get the vehicle going again.
Sometimes you cannot.
Tour of Duty & Reporting
FleetCore does not only maintain the vehicle mechanically. It can also track what that vehicle has been doing.
FleetCore can monitor vehicle activity across a tour of duty.
Vehicle History records relevant FleetCore events, while the reporting system can generate and archive tour or shift reports for later review.
Reports can include information such as:
Tour start and end
Vehicles operated
Starting and ending mileage
Starting and ending fuel levels
Refueling
Mechanical events
Maintenance activity
Service completion
FleetCore.Garage activity
FleetCore generates human-readable text reports alongside structured JSON records.
This allows a vehicle to develop an operational record alongside its mechanical and maintenance history.
The reporting architecture also provides a foundation for possible future MDT and report-management integration without requiring an external MDT for FleetCore itself to operate.
FleetCore Control Center
Press:
F1
to open the FleetCore Control Center.
The Control Center gives you access to FleetCore’s management interface, including areas for:
Vehicle information
Vehicle history
Reports
Settings
System status
FleetCore management functions
This is the central place for managing and reviewing FleetCore during gameplay.
Vehicle Monitor & Diagnostics
Press:
F10
to toggle FleetCore’s diagnostic detail display.
The FleetCore Vehicle Monitor provides information about the currently tracked vehicle and can draw attention to abnormal conditions.
The adaptive display can report information such as:
Battery voltage
Engine temperature
Engine-oil condition
Fuel level
Tire condition
Overall vehicle condition
Active mechanical warnings
The diagnostic system is designed to provide useful information without requiring the player to constantly stare at a maintenance menu.
HUD placement and related behavior can be adjusted through the FleetCore configuration.
Optional FleetCore.Garage Addon
FleetCore v1.0.1 introduces full support for the separately installed FleetCore.Garage addon through Garage Bridge API 1.3.
FleetCore.Garage is optional.
FleetCore remains a complete standalone vehicle-management and mechanical-simulation plugin.
You do not need to install FleetCore.Garage to use FleetCore.
Players who want physical service-location gameplay can install the Garage addon separately.
FleetCore.Garage adds:
Four full-service bays at Mission Row
Tire service at Sandy Shores
Tire service at Paleto
Electrical service at Paleto Municipal
Location-specific diagnostics
Location-specific repair options
Cosmetic-damage repair
Timed service sessions
Persistent Garage service records
Map blips
Proximity world markers
FleetCore vehicle recognition
Service activity added to FleetCore history and shift reports
During service, the selected vehicle is secured in place and kept completely shut down until the service is finished.
FleetCore remains the authority over the vehicle’s persistent mechanical state. Garage communicates with FleetCore through the addon bridge rather than maintaining a separate, conflicting vehicle-condition database.
The vehicle brought into the Garage is the same persistent vehicle FleetCore has already been tracking—with its existing mileage, fuel level, maintenance condition, damage, and operational history.
FleetCore.Garage requires FleetCore v1.0.1.
FleetCore does not require FleetCore.Garage.
First Launch & Onboarding
The first time FleetCore successfully loads, you will receive a dedicated onboarding screen explaining what FleetCore is and how the system works.
Once you acknowledge it, FleetCore remembers that onboarding has been completed and does not display the complete introduction every time you start the game.
Normal launches display:
FleetCore loaded successfully Created by LaVante Pettigrew Your car matters now. DON'T WRECK IT. If you want to see the introduction again, the onboarding state can be reset through FleetCore.
If the optional FleetCore.Garage addon is installed during a fresh installation, Garage waits until FleetCore’s onboarding has been completed before presenting its own separate introduction.
FleetCore receives priority as the parent plugin.
Once FleetCore onboarding is complete, the Garage handoff can occur during the same gameplay session without requiring GTA V to be restarted.
Developer Mode
FleetCore contains extensive diagnostic functionality used during development and testing of its mechanical systems.
Developer Mode is OFF by default in the public release.
When enabled, the configured development controls allow individual systems to be damaged, depleted, serviced, or repaired for testing.
Developer Mode is primarily intended for:
Troubleshooting
Testing
Bug reproduction
Development
Vehicle-profile validation
Developer Mode is not required for normal patrol gameplay.
Configuration
FleetCore’s main configuration file is located at:
plugins\LSPDFR\FleetCore\FleetCore.ini Additional FleetCore configuration and data files include:
VehicleProfiles.json FuelStations.json RoadsideStations.json FleetCore’s configuration provides control over:
Individual simulation systems
Keybinds
Warning thresholds
Wear rates
Fuel behavior
Tire behavior
Damage behavior
Dashboard and HUD behavior
Notifications
Vehicle exclusions
Reporting
Developer controls
Other FleetCore functionality
Major simulation systems can be individually enabled or disabled.
The public release ships with the primary simulation systems enabled and:
DebugMode=False If the main FleetCore INI is missing, FleetCore can automatically generate a new default configuration file.
Existing users should preserve a backup of customized configuration and profile files before replacing them during an update.
Installation
FleetCore requires an existing working installation of:
Grand Theft Auto V
RAGE Plugin Hook
LSPDFR
Microsoft .NET Framework 4.8
To install FleetCore, copy the included:
plugins folder into your main Grand Theft Auto V directory.
Your resulting installation should look like:
Grand Theft Auto V └── plugins └── LSPDFR ├── FleetCore.dll └── FleetCore ├── FleetCore.ini ├── FuelStations.json ├── RoadsideStations.json └── VehicleProfiles.json You do not need to manually create vehicle histories, reports, persistent databases, or backup files.
FleetCore creates its operational data as needed.
Generated folders can include:
FleetCore\Data FleetCore\History FleetCore\Reports The optional FleetCore.Garage addon is distributed separately and is not required for the installation or operation of FleetCore Core.
Updating From v1.0.0
Before installing v1.0.1:
Back up your existing plugins\LSPDFR\FleetCore folder.
Preserve any customized INI settings or vehicle profiles.
Copy the updated files into the GTA V directory while maintaining the packaged folder structure.
Replace the previous FleetCore DLL when prompted.
Review the updated JSON data files before overwriting any personal customizations.
Existing persistent vehicle data can remain in place so previously tracked vehicles retain their histories and mechanical condition.
Release Notice
FleetCore v1.0.1 is the first update to the initial public release.
FleetCore’s core systems and the new Garage bridge went through:
Development testing
Cold-start testing
Persistence testing
Edge-case and abuse testing
Extended real-patrol stress testing
Multiple-vehicle testing
Clean-install testing
Configuration-regeneration testing
Plugin unload and cleanup testing
Garage dependency testing
Same-session onboarding handoff testing
Vehicle-recognition testing
Diagnostic testing
Location-specific service testing
Full-service testing
Tire-service testing
Electrical-service testing
Cosmetic-damage repair testing
Service-history testing
Shift-report testing
Complete patrol and service-network testing
That does not mean there will never be bugs.
FleetCore interacts with many different parts of a vehicle across potentially long gameplay sessions. Different vehicle packs, plugin combinations, configurations, and unusual gameplay situations may expose something that was not encountered during development.
If something breaks or you encounter an unusual bug, please leave a comment on the FleetCore LSPDFR page.
If possible, include:
What happened What vehicle you were using What you were doing immediately before the problem Whether you can make it happen again Relevant RagePluginHook.log information Other vehicle or gameplay plugins that may be involved The more information provided, the easier it will be to reproduce and resolve the problem.
Known Limitations — v1.0.1
FleetCore.Garage Is a Separate Download
The physical Garage and service-location system is not contained inside FleetCore.dll.
It is available through the separate optional FleetCore.Garage addon.
FleetCore Core continues operating normally without Garage installed.
External MDT Filing
Direct external MDT filing is not currently implemented.
FleetCore generates its own text and JSON reports.
Architecture remains reserved for possible future integration with systems such as Nexus MDT and pdComp, but FleetCore does not currently require or claim direct integration with either project.
Any external integration will depend on the integration methods available and any required permission or cooperation from the applicable creator.
Spoken 10-41 and 10-42
FleetCore does not perform its own microphone speech recognition for spoken radio phrases such as 10-41 and 10-42.
External dispatch and duty-state integration may be explored later instead of adding another independent voice-recognition system to FleetCore.
Planned Updates & Future Development
FleetCore v1.0.1 continues the foundation established by the initial release.
Future development may expand or improve:
Mechanical wear
Component failures
Maintenance behavior
Vehicle damage
Fluid behavior
Service requirements
Environmental effects
Fleet management
Vehicle-profile support
Garage integration
Reporting
External plugin integration
Quality-of-life options
Aviation vehicle systems
Marine vehicle systems
Any future major FleetCore module—such as Aviation or Marine—will have its own separate introduction, acknowledgment state, and completion gate rather than resetting FleetCore Core’s onboarding.
FleetCore.Garage Development
FleetCore.Garage now provides the physical service-location gameplay originally planned during FleetCore’s initial release.
Future Garage updates may expand:
Service locations
Repair categories
Garage configuration
Vehicle service records
Fleet-management functions
Out-of-service vehicle behavior
Additional diagnostic options
Optional map and world-marker behavior
Additional interaction and immersion features
FleetCore.Garage will remain optional.
Nexus MDT and pdComp Integration
Possible future integration with Nexus MDT and pdComp may include:
Vehicle histories
Maintenance information
Fleet records
Tour reports
Service records
Vehicle data
These integrations are not currently implemented and will depend on available integration support and permission or cooperation from the applicable creators.
Dispatch & Duty Integration
Future development may explore ways for external dispatch systems to communicate duty states directly with FleetCore.
For example:
Officer goes 10-41 ↓ Dispatch system recognizes it ↓ FleetCore begins the tour Officer goes 10-42 ↓ Dispatch system recognizes it ↓ FleetCore closes the tour ↓ Shift report generated Rather than FleetCore implementing another standalone speech-recognition system, the goal would be to work with existing systems where possible.
Vehicle Profile Expansion
The vehicle-profile system will continue to be expanded and refined.
The goal is to make FleetCore increasingly easy to adapt to different:
Police departments
Sheriff’s offices
Highway patrol and state police agencies
Federal agencies
Vehicle packs
Fictional departments
Specialized units
Vanilla law-enforcement vehicles
Your LSPDFR build does not have to look like mine.
Community Feedback
A major part of continued development will come from seeing FleetCore operate in builds other than my own.
Community feedback will help identify:
Bugs
Compatibility issues
Balancing problems
Mechanical behavior requiring adjustment
Vehicle-pack differences
Features needing additional configuration
Quality-of-life improvements
If FleetCore behaves differently in your setup than it does in mine, I want to know about it.
Important
Planned features are not guaranteed for a particular version or timeframe.
Some future features—especially external plugin integrations—depend on what other creators make available and whether the necessary access or permission can be obtained.
I would rather release an integration when it works correctly than promise something I cannot properly implement.
Changelog
v1.0.1 — Garage Bridge & Vehicle-Profile Update
FleetCore v1.0.1 includes:
Garage Bridge API 1.3
Support for the optional FleetCore.Garage addon
FleetCore vehicle-snapshot support
Authorized Garage service requests
Garage service activity recorded in vehicle history
Garage service activity included in FleetCore shift reports
Improved addon lifecycle behavior
Improved plugin unload and cleanup behavior
Comprehensive world-blip cleanup during unloading
Updated fuel-station data
Expanded generic vanilla law-enforcement support
43 included default vehicle profiles
Improved vehicle identity handling
Improved persistence behavior
Automatic INI regeneration
Stability and compatibility fixes
v1.0.0 — Initial Public Release
The initial public release included:
Persistent vehicle simulation
Interconnected mechanical systems
Battery, alternator, and starting simulation
Cooling and overheating
Engine and transmission systems
Multiple vehicle-fluid systems
Tires and suspension
Fuel consumption and refueling
Fuel-system components
Roadside equipment
Terrain and weather influence
Fluid leaks
Burnout-related wear
Vehicle mileage
Vehicle inventory
Vehicle identity profiles
Configurable vehicle roles
Vehicle service profiles
Vehicle history
Tour-of-duty tracking
Shift-report generation and archiving
FleetCore Control Center
Diagnostic Vehicle Monitor
First-run onboarding
Startup branding
Configurable simulation behavior
Persistent vehicle data
Persistence backup and recovery safeguards
Vehicle-history backup and recovery safeguards
Developer Mode
Clean-install support
Credits
Created & Developed by LaVante Pettigrew
FleetCore was designed, developed, and tested from the ground up as a vehicle simulation and management system for LSPDFR.
Special thanks to the LSPDFR community and the creators whose work helped make the build FleetCore was developed and tested with possible.
Thank you to everyone who downloads, tests, reports bugs, and helps FleetCore continue to grow.
FleetCore v1.0.1
Created by LaVante Pettigrew
Mechanical realism. Operational depth. Persistent progression.
Your car matters now. DON'T WRECK IT.