Mod Install Check

The Mod install check looks inside your GTA V folder and tells you whether your installed mods are in the right place— the single most common reason a mod silently fails to load or the game crashes on startup. It's off by default and marked Beta while the list of known mods grows.

Unlike the crash analysis, this check doesn't need a log. It can do a base review from your GTA V folder alone, so you can verify a fresh install before you even launch the game. (A log still helps confirm a mod actually loaded — this check confirms the files are where they belong.)

How to turn it on

  1. Open the Settings (the cog icon).
  2. Switch Mod install check on.
  3. Make sure your GTA V folder is set so the app knows where to look.
  4. Open or re-open a log. The results appear as a Mod install check section in the report.

Everything is read-only — the app only looks at where files are; it never moves, changes, or installs anything.

How it works

For each mod it knows about, the check looks for that mod's key file in the exact folder it's supposed to live in, and reports one of:

  • Installed correctly— the mod's file is in the right folder (and its required dependencies are present).
  • In the wrong folder— the file exists, but in a place the game won't load it from. The most common example is an LSPDFR plugin sitting in Plugins instead of Plugins\LSPDFR. This is flagged in red and added to What to fix.
  • Missing a required file — the mod is installed, but a file it depends on (for example RAGENativeUI.dll) is missing, so it won't load. Also surfaced in What to fix.
  • Not detected— you don't have that mod, so it's skipped and not shown.

The check understands the different homes mods use, so it won't wrongly flag something that's correctly placed:

  • LSPDFR plugins (most callout packs and add-ons) → Plugins\LSPDFR
  • RAGEPluginHook plugins (e.g. DLSv2, EUP Menu, Cop Holster) → Plugins
  • ASI mods (e.g. ELS-V, PLD, Siren Limit Adjuster) → the GTA V root, next to GTA5.exe

Fixing what it finds

  • In the wrong folder — move the named file to the folder shown, then restart the game. For example, move SuperCallouts.dll from Plugins into Plugins\LSPDFR.
  • Missing a required file— reinstall the mod (or its dependency) following the mod's own instructions, making sure every file ends up where the readme says. Shared dependencies like RAGENativeUI.dll usually belong in the GTA V root.

Where the app has a mod page link, it's shown next to the result so you can grab the latest version.

Mods it currently checks

The list grows over time. Each mod is checked against the folder it's supposed to live in:

ModInstall documentation last checked
686 Callouts30/06/26
Arrest Manager30/06/26
Assorted Callouts30/06/26
Better EMS30/06/26
Coastal Callouts30/06/26
Computer+30/06/26
Cop Holster30/06/26
DLSv2 (Dynamic Lighting System)30/06/26
ELS-V30/06/26
EUP Menu30/06/26
Grammar Police30/06/26
LSPDFR+30/06/26
PeterU Callouts30/06/26
PLD (Police Locator Display)30/06/26
PoliceSmartRadio30/06/26
SirenSetting Limit Adjuster30/06/26
SuperCallouts30/06/26
Traffic Policer30/06/26
UnitedCallouts30/06/26

EUPFR Basic is also recognised, but as a pure data/uniform mod (no plugin file) its placement can't be verified the same way.

What it can't do

  • It checks file placement, not whether a mod works once loaded — your log is still the best tool for runtime errors.
  • It only knows the mods on the list above. A mod that isn't listed simply won't appear; it isn't a sign anything is wrong.
  • It needs to know your GTA V folder. If it can't tell where the game is, it asks you to set it in Settings.

Privacy

The mod install check runs entirely on your computer. It only reads which files exist and where, and the results stay on your machine as part of your report unless you choose to share that report. Nothing is uploaded automatically.

See also System check and GTA V folder.

Still need help? Contact support.