Identify the mod first. Then install the right system.

Non-negotiable boundary: never carry Story Mode mods into GTA Online

Rockstar's published statement generally addresses non-commercial third-party projects for its single-player PC games and contains important limitations; it is not a license or endorsement. GTA Online uses BattlEye. Rockstar says modified graphics software can create technical issues and official online play requires BattlEye. Keep a verifiably clean route to GTA Online and never use mod menus, altered archives, script loaders, cheat tools, or anti-cheat bypass instructions there.

Legacy and Enhanced are separate compatibility targets

On PC, “works with GTA V” is no longer enough information. Record whether the installation is GTA V Legacy or GTA V Enhanced, then match every loader, framework, plug-in, archive edit, vehicle pack, and troubleshooting instruction to that edition. Similar folder names do not make the binaries or internal game data interchangeable.

1. Open the game's launcher or executable properties and record the edition plus build before downloading anything.
2. Check the framework's own current compatibility page—not an old video description, repost, or search snippet.
3. Check the individual mod page for the same edition. A compatible base framework does not automatically make every dependent plug-in compatible.
4. Keep Legacy and Enhanced ledgers, archives, configuration, and test results separate. Never copy an entire working folder from one edition into the other.
5. After a title update, pause the profile until the foundation pages confirm the new build. As of July 27, 2026, both the LCPDFR status page and Script Hook V page report current Legacy and Enhanced compatibility, but that status can change with the next update.

Phase 1: prepare the clean game

1. Confirm the edition. Record storefront, Legacy or Enhanced edition, executable location, and current game build. Do not assume a mod supports both PC editions.
2. Launch Story Mode cleanly. Reach a playable save before adding files. A broken clean game cannot prove a mod caused the problem.
3. Back up local saves and configuration. Protect irreplaceable progress separately from the installation folder.
4. Use the launcher's file verification. Start from known original files. Keep a clean profile or a reliable procedure that restores one before official online play.
5. Create a mod ledger. Record name, author, source URL, download date, game edition, version, dependencies, files added, files replaced, key bindings, and removal instructions.
6. Scan downloads. Use current security software. Do not disable protection for an unknown executable, password-protected archive, repost, or shortened download chain.

Phase 2: identify the package before copying anything

The filename and readme should tell you which pathway applies. If the author does not name the supported game edition, required loader, destination, configuration changes, test method, and uninstall path, stop. Popularity does not replace documentation.

Phase 3: build only the foundation you need

Script Hook V for native ASI scripts

Alexander Blade's Script Hook V project provides the runtime many single-player ASI scripts expect. Use the project page at dev-c.com, verify compatibility with the installed GTA V build, and follow the archive's instructions. Do not download a renamed copy from an advertisement or repost site. After a GTA V title update, Script Hook V may need an update before dependent scripts work again.

Script Hook V .NET for managed scripts

Script Hook V .NET depends on Script Hook V and lists .NET Framework 4.8 plus the Visual C++ 2019 x64 runtime. Its maintainers instruct users to keep the ASI and matching API DLLs from one build together and place user scripts in a scripts folder. The project currently warns that some newer GTA builds require a sufficiently recent nightly build. Read the current release notice instead of copying an old tutorial's version number.

OpenIV for archive and package workflows

OpenIV is used by mods that alter GTA archives or arrive as OIV packages. Use its mods-folder workflow so modified copies are separated from original archives. For an OIV package, inspect the author and package instructions, open Package Installer, and select the mods-folder destination when it is supported. Manual replacements must follow the exact mirrored archive path given by the author. Never improvise a target because two packages contain similarly named files.

LSPDFR and RAGE Plugin Hook for police roleplay

Install and verify base LSPDFR before any callouts or police add-ons. LCPDFR's official installation check expects the LSPDFR folder, Plugins folder with LSPD First Response, and RAGEPluginHook.exe. Launch through RAGE Plugin Hook, confirm police-station markers and duty behavior, then add one callout, backup, dispatch, computer, vehicle, uniform, or lighting layer at a time.

Every major GTA V mod category—and what usually breaks

• Police and emergency: LSPDFR framework, callouts, dispatch, backup, traffic stops, computers, uniforms, vehicles, sirens, lighting, stations, and agency packs. Common failures are outdated RAGE/LSPDFR versions, missing plug-in dependencies, incorrect plug-in folders, duplicate keys, and conflicting vehicle or ELS configurations.
• Scripts and gameplay: missions, jobs, interactions, companions, cameras, immersion systems, trainers for offline testing, and quality-of-life changes. Common failures are missing Script Hook V or SHVDN, wrong API version, absent runtime, and two scripts controlling the same input or game system.
• Vehicles: replacement and add-on cars, motorcycles, aircraft, boats, emergency fleets, handling, sounds, liveries, and tuning. Common failures are an incorrect DLC list entry, wrong spawn name, missing shared data, game-configuration limits, bad textures, or replacing the same vehicle twice.
• Characters, clothing, and equipment: peds, uniforms, accessories, animations, and weapons. Common failures are slot conflicts, missing textures, incompatible skeletons, and metadata overwritten by another pack.
• Maps and interiors: YMAP placements, MLO interiors, buildings, roads, vegetation, props, and complete areas. Common failures are overlapping maps, missing YTYP definitions, broken collision, duplicate archetypes, and Story Mode instructions applied to a FiveM resource—or the reverse.
• Visuals and audio: lighting, weather, timecycle, textures, roads, vegetation, effects, ReShade presets, sounds, and sirens. Common failures are overlapping visual files, excessive VRAM use, shader-injector conflicts, broken nights or weather, and BattlEye incompatibility. Keep these out of official online play.
• World and traffic: population, dispatch, wanted behavior, pedestrians, traffic density, economy, and handling. Common failures are multiple mods replacing the same data tables or an aggressive setting overwhelming CPU, memory, or engine limits.
• Overhauls and total conversions: coordinated packages touching many categories. Treat one overhaul as the base profile and add only extras its documentation declares compatible.
• Creation tools: CodeWalker and similar authoring tools help inspect or create map data; they are not drop-in gameplay mods. Use the creator's repository and documentation, and work on copies.
• FiveM resources: server-controlled scripts, maps, vehicles, and assets organized as resources, commonly identified by fxmanifest.lua. Install them only on a server you control or administer, follow the resource license, keep secrets server-side, and test client and server consoles.

A stable police-mod build order

1. Clean compatible GTA V Story Mode.
2. Current base LSPDFR package and included/current RAGE Plugin Hook.
3. One successful duty session with no extra plug-ins.
4. One callout pack; verify dispatch, acceptance, completion, and return to patrol.
5. One backup or interaction plug-in; resolve key conflicts immediately.
6. Police vehicles and their required lighting/configuration layer.
7. Uniforms, sirens, computer, radio, stations, and visual polish—one tested layer at a time.

Do not begin with a creator's fifty-mod folder. You lose provenance, permissions, compatibility knowledge, and the ability to identify a crash. Build your own documented stack from primary project pages.

FiveM is a separate path, not a Story Mode mod folder

Cfx.re documents FiveM as its own client and server ecosystem. Players should install the client from FiveM's official site and follow server rules. Server owners place properly structured resources inside their server resources tree and enable them through server configuration. A resource can contain client scripts, server scripts, and streamed assets. Do not copy a Story Mode tutorial into a FiveM server or place a server resource beside GTA5.exe unless the resource author explicitly documents that workflow.

Servers may disallow client plug-ins, and Cfx.re warns that incompatible plug-ins can crash the game. Treat client-side plug-ins, server resources, and Story Mode ASI scripts as three different installation questions.

Test, troubleshoot, remove, and update

1. Test one change. Use the same Story Mode save, location, weather, vehicle, and action when possible.
2. Read the right log. LSPDFR/RAGE, Script Hook V .NET, FiveM, and individual plug-ins can expose different failure evidence. Preserve the log from the failed run before launching again.
3. Reverse the last change first. Remove only the new files or restore the exact copied archive listed in your ledger.
4. Use a half-split for a large stack. Disable half the optional mods, test, then narrow the failing half. Keep the required framework active.
5. After a title update, stop. Check framework and mod project pages. Update the foundation first, then re-enable optional layers individually.
6. Uninstall from records. Use the author's uninstaller when supplied. Otherwise remove only ledgered files and restore clean archives through your protected copy or launcher verification.
7. Verify the clean profile before GTA Online. Re-enable BattlEye and use original files. If you cannot prove the profile is clean, do not connect.