Force Duty Diagnostics 2.0.0

(0 reviews)

Force Duty Diagnostics

A LSPDFR plugin that provides advanced crash detection, plugin fingerprinting, and diagnostic logging during the LSPDFR duty‑switch process. This tool identifies which plugin crashes when going on duty, generates detailed crash reports, and scans your plugin installation for missing or broken files.

No More Force Duty Crash

The correct response to criticism

ForceDuty Diagnostics is not a replacement for RPH.log. It solves a specific problem RPH.log cannot: identifying which plugin crashes during the duty‑switch event. RPH.log does not show which plugin threw the exception — it only shows that the event failed. This plugin fingerprints each handler, logs the responsible plugin, reconstructs its path, and generates a dedicated crash report. Developers still request RPH.log because it contains startup information and unrelated plugin logs, but ForceDuty Diagnostics provides the missing link: the exact plugin responsible for ForceDuty crashes.

What the plugin actually does (and RPH.log cannot)

**1. It identifies which plugin crashed during duty switch**

RPH.log does not tell you which plugin threw the exception. It only shows:

Unhandled exception in OnDutyStateChanged

Your plugin shows:

PLUGIN CRASH DETECTED during duty switch!
Plugin: StopThePed
Path: Plugins/LSPDFR/StopThePed/StopThePed.dll
Exception: Object reference not set...

That is the entire purpose of the mod.

This is not “copying exceptions.” This is fingerprinting plugin handlers, something RPH cannot do.

2. It reconstructs plugin paths even when assemblies load from memory

RPH.log cannot do this. Your plugin can show:

Exact DLL path
Plugin folder
Plugin name
Whether the plugin was loaded from memory

This is critical for debugging.

3. It isolates duty‑switch crashes from unrelated noise

RPH.log is full of:

Fiber ticks
Native calls
Game events
Unrelated plugin spam
LSPDFR internal logs

Your plugin produces a clean, focused diagnostic log.

4. It generates per‑plugin crash reports

RPH.log is one giant file. Your plugin creates:

CrashReports/StopThePed/StopThePed_Crash_2026-06-02.log

This is far more useful for mod developers.

5. It detects missing dependencies BEFORE crashes happen

RPH.log only shows the crash after it happens.

Your plugin warns:

ERROR: RAGENativeUI.dll is missing! StopThePed may crash.

This is preventative diagnostics, not reactive logging.

Why developers still ask for RPH.log

Developers ask for RPH.log because:

It contains startup logs
It contains plugin load order
It contains game version
It contains RPH version
It contains native call failures
It contains fiber exceptions
It contains non‑duty‑switch crashes

Your plugin is not meant to replace RPH.log. It is meant to fill the one gap RPH.log cannot fill:

Which plugin crashed during ForceDuty?

That’s it. That’s the mission. And it does that perfectly.

Features

Crash Fingerprinting

When LSPDFR switches duty states, Force Duty Diagnostics:

Wraps every plugin subscribed to OnOnDutyStateChanged
Detects when a plugin throws an exception
Identifies the exact plugin responsible
Logs the plugin name and DLL path
Captures the full exception and stack trace

This makes it easy to pinpoint which plugin is breaking ForceDuty or causing duty‑switch crashes.

Timestamped Crash Reports

Every detected crash generates a standalone crash report:

Saved per‑plugin
Timestamped down to the millisecond
Includes plugin name, path, exception, and stack trace
Organized for long‑term debugging and tracking

Crash reports are stored in:

Plugins/LSPDFR/ForceDutyDiagnostics/CrashReports/

Plugin Integrity Scanner

On startup and every duty change, the plugin scans:

Plugins\
Plugins\LSPDFR\
All subfolders recursively

It checks for:

Missing DLLs
Missing config files
Empty or incomplete plugin folders
Incorrectly installed plugins

This helps identify installation issues before they cause crashes.

Duty Change Diagnostics

Whenever the player goes on duty or off duty, the plugin logs:

Duty state
Thread ID
Game time
Player position
Plugin scan results
Crash fingerprints (if any)

This creates a complete picture of what happened during the duty switch.

Cleanup & Stability

ForceDuty Diagnostics is fully passive:

Does not modify LSPDFR behavior
Does not interfere with other plugins
Only observes, logs, and reports
Generates clean, timestamped logs

All logs are stored in:

Plugins/LSPDFR/ForceDutyDiagnostics/ForceDutyDiagnostics.log

Requirements

RagePluginHook
LSPDFR

Installation

Place ForceDutyDiagnostics.dll into:

Grand Theft Auto V\Plugins\LSPDFR\

The plugin loads automatically when LSPDFR starts.

Known Bugs

There are currently no confirmed bugs, but the plugin is actively monitored and updated as needed.

If you encounter any issues, check the RPH.log for my plugin to see if there are any encounters.

Latest Game Version 3751.0 Current Game Version 3788.0

Edited Wednesday at 06:05 AM4 days by TimmyLuke017 Gaming

What's New in Version 2.0.0

Released Wednesday at 12:37 AM4 days

What's New in Version 2.0.0

What got updated?

2.0.0 - 6/2/26

Removed RageNativeUI and NativeUI due to an error that was given

[6/2/2026 9:18:51 PM.164] Unhandled exception occurred in console command "ForceDuty" [6/2/2026 9:18:51 PM.164] Exception type: System.IO.FileNotFoundException [6/2/2026 9:18:51 PM.164] Exception message: Impossible de charger le fichier ou l'assembly 'RAGENativeUI, Version=1.9.2.0, Culture=neutral, PublicKeyToken=null' ou une de ses dépendances. Le fichier spécifié est introuvable.

2.0.0

Short Description

A diagnostic tool that identifies which plugin crashes during LSPDFR duty switches, generates detailed crash reports, and scans

AI disclosure

The author has disclosed that AI tools were used in creating the following aspects of this file:

Description
Images
Mod and Mod Content (Substantial)

GTA 5 Jedi Master, Michael21107, 0pheIia and 4 others
5
1
1

Download this file

File Information

Views 4,397
Downloads 638
Submitted Tuesday at 06:57 AM5 days
Published Wednesday at 12:37 AM4 days
Updated Wednesday at 12:37 AM4 days
File Size 21.43 kB
Compatibility All Versions
Special Features No More BEEP sound once a Plugin Crashes. Bypasses the Force Duty Shutdown and lets you keep playing LSPDFR. Note the logs will be logged silently.
Requires RAGE Plugin Hook
Minimum LSPDFR Version 0.4.9
Script/Plugin Type LSPDFR plugin
Maximum LSPDFR Version
Hide AV false +ive [Staff] No

Inside the File

Loading, please wait...

Followers

Previous File SBS - Suspicious Behavior System

Next File West Coast Callouts

User Feedback

14 Comments 0 Reviews

JM Modifications

Members

Tuesday at 10:10 AM5 days (edited)

TimmyLuke is at it again. W.

Edited Tuesday at 10:10 AM5 days by JM Modifications

TimmyLuke017 Gaming

Members Author

Tuesday at 04:11 PM4 days (edited)

5 hours ago, JM Modifications said:
TimmyLuke is at it again. W.

Thank you! Let me know if it is working for you right now it's in Alpha. I have tested it like 4 to 5 times already. I have never seen anyone create a plugin like this one. I have worked tiredness on this plugin since 3 AM Est this morning.

Edited Tuesday at 04:12 PM4 days by TimmyLuke017 Gaming

0pheIia

Members

Tuesday at 04:46 PM4 days

bro i love you. lmao you dont understand how bad I NEEDED THIS!

AlOutlaw

Members

Tuesday at 05:22 PM4 days

this could be huge thank u

TimmyLuke017 Gaming

Members Author

Tuesday at 05:23 PM4 days

30 minutes ago, 0pheIia said:
bro i love you. lmao you dont understand how bad I NEEDED THIS!

There are logs that log stuff separately from different plugins in Crashlogs. This is mainly useful for Developers and Non-Developers. It helps identify which plugin is causing a crash. RPH log does not. They should have implemented this a long time ago.

0pheIia and Ickthy
2

SSStuart

Members

Tuesday at 07:23 PM4 days (edited)

Interesting idea!

However, it seems that if a crash occurs before this plugin loads (for example, if another plugin requires RNUI but it's missing), the crash isn't logged.

I might be wrong, but I just tested the plugin with a crash during ForceDuty, and I don't see any information in either the log or the “CrashReports” folder.

Edited Tuesday at 07:25 PM4 days by SSStuart

TimmyLuke017 Gaming

Members Author

Tuesday at 07:44 PM4 days

18 minutes ago, SSStuart said:
Interesting idea!
However, it seems that if a crash occurs before this plugin loads (for example, if another plugin requires RNUI but it's missing), the crash isn't logged.

I might be wrong, but I just tested the plugin with a crash during ForceDuty, and I don't see any information in either the log or the “CrashReports” folder.

Check your RagePluginHook.log and send me the error you're getting, and I will update it in the plugin I might remove the RageNativeUI dependency from the plugin itself because it is not required.

SSStuart

Members

Tuesday at 07:49 PM4 days

2 minutes ago, TimmyLuke017 Gaming said:
Check your RagePluginHook.log and send me the error you're getting, and I will update it in the plugin I might remove the RageNativeUI dependency from the plugin itself because it is not required.

...
[6/2/2026 9:18:51 PM.036] LSPD First Response: [ForceDutyDiagnostics] OnOnDutyStateChanged fired. New state: ON DUTY
[6/2/2026 9:18:51 PM.164] ====================================================================================================
// I have installed Stop The Ped but not RNUI :
[6/2/2026 9:18:51 PM.164] Unhandled exception occurred in console command "ForceDuty"
[6/2/2026 9:18:51 PM.164] Exception type: System.IO.FileNotFoundException
[6/2/2026 9:18:51 PM.164] Exception message: Impossible de charger le fichier ou l'assembly 'RAGENativeUI, Version=1.9.2.0, Culture=neutral, PublicKeyToken=null' ou une de ses dépendances. Le fichier spécifié est introuvable.
[6/2/2026 9:18:51 PM.164] Stack trace: at 0VM/W\*2;V(K4x2|eGR3\&el@!(.⁭⁯⁭⁯⁫‍⁪‍⁫‪⁯‮‪‎‫‏⁫‭‏‏⁫‮⁫‮⁭‎⁬‫‪‫‪‪‎⁮‎‮(Keys )
[6/2/2026 9:18:51 PM.164]    at 0VM/W\*2;V(K4x2|eGR3\&el@!(.⁬‮⁭‫⁫⁬‪‬‪‬⁫⁮‌‮‍‏⁫‍⁮‌‎⁮‏‮⁪‏‭⁬‎‍⁫‌‭⁮⁭‎‬⁬‭‮(Keys , Keys )
[6/2/2026 9:18:51 PM.164]    at ‭⁫‎‏‏⁯‪⁭⁬⁪⁪‍⁮‏‌⁪‫⁫‎‎⁪⁬‫‮‍⁬‎‎⁯‫⁮‭‌‬⁪‎‎⁬‮⁫‮.⁯‌‌⁮‎‍⁫‌‫‭‌‬‫⁮‌‌⁮‭‭‏‭‌‫⁪‫‍‌‭⁫⁬‭‎‬‌‎⁫‌⁫‏‮()
[6/2/2026 9:18:51 PM.164]    at ‫‬‫⁭⁯‮‭‭⁯‎‏‌‮‌⁬‭⁯‪⁮⁬⁬⁯⁬‌⁭‫‮⁭‏⁮⁮‍⁮‭‌‍‮.‪⁬‭‫⁮‭‎‍‫⁮⁯‪⁮‌‍⁫⁬‫⁭‍⁪⁭‌⁭‬‭‏⁯⁭‮‭‫⁮‬‮‎⁬⁪‮(Boolean )
[6/2/2026 9:18:51 PM.164]    at LSPD_First_Response.Mod.API.Functions.OnDutyStateChangedEventHandler.Invoke(Boolean onDuty)
[6/2/2026 9:18:51 PM.164]    at OglpPkMKzqttTPIgCqXXIyTjIiLn.PWUtVAAUYtuczEPxTTYWMCCfeqhk(Boolean ) in D:\GTA V\LSPD First Response\LSPD First Response\Mod\PlayerDutyController.cs:line 69
[6/2/2026 9:18:51 PM.164]    at OglpPkMKzqttTPIgCqXXIyTjIiLn.AegQlubIjZYzoFisbARJbgyuRgBH(Boolean , Boolean ) in D:\GTA V\LSPD First Response\LSPD First Response\Mod\PlayerDutyController.cs:line 371
[6/2/2026 9:18:51 PM.164]    at OglpPkMKzqttTPIgCqXXIyTjIiLn.VNjpBNgzINdfjMBzdOWrHLvelvDK(Boolean , Boolean , Boolean ) in D:\GTA V\LSPD First Response\LSPD First Response\Mod\PlayerDutyController.cs:line 291
[6/2/2026 9:18:51 PM.164]    at LSPD_First_Response.Mod.Utils.ConsoleCommands.Command_ForceDuty(Boolean keepCurrentOutfit, Boolean keepLoadout, String agency) in D:\GTA V\LSPD First Response\LSPD First Response\Mod\Utils\ConsoleCommands.cs:line 253
[6/2/2026 9:18:51 PM.164] ====================================================================================================
...

(The issue with RNUI is not related to ForceDutyDiagnostics)

SuperPyroManiac

Community Team

Wednesday at 12:42 AM4 days

Community Team

This plugin appears to do very little except copy exceptions it detects into its own log. Frankly for support purposes the RPH.log would be more accurate. Even with error from this plugin itself the dev asks users to send the actual RPH log. Just saying.

TimmyLuke017 Gaming, Lepoisson, williamperish and 2 others
2
1
2

TimmyLuke017 Gaming

Members Author

Wednesday at 01:08 AM4 days

23 minutes ago, SuperPyroManiac said:
This plugin appears to do very little except copy exceptions it detects into its own log. Frankly for support purposes the RPH.log would be more accurate. Even with error from this plugin itself the dev asks users to send the actual RPH log. Just saying.

I have updated the AI disclosure

AI was used as a development assistant, not as an automated code generator. It supported the creation of Force Duty Diagnostics. AI was used as a development assistant to help design the diagnostic architecture All logic and behavior were directed and validated by the developer.

craio2lk and SuperPyroManiac
2

sxopgaming

Members

Wednesday at 06:41 AM4 days

Bro this is anti crash for lspdfr

nova2727

Members

Wednesday at 10:56 PM3 days

This mod does not help locate the crash files

williamperish and TimmyLuke017 Gaming
2

TimmyLuke017 Gaming

Members Author

Thursday at 03:14 AM3 days

4 hours ago, nova2727 said:
This mod does not help locate the crash files

No but it locates the crash of what plugin it came from in the logs. But it should automatically make the logs once there is a force duty crash if you're not experiencing a force duty crash then it will not automatically make the logs plus it stops the annoying sound from force duty crash sound that most of us hate.