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:

1. Back up your existing plugins\LSPDFR\FleetCore folder.

2. Preserve any customized INI settings or vehicle profiles.

3. Copy the updated files into the GTA V directory while maintaining the packaged folder structure.

4. Replace the previous FleetCore DLL when prompted.

5. 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.