Installing Mods

Installing Mods

The install engine

What it is. The core engine: it analyzes a mod, maps each file to its target directory, and deploys it through the full safety pipeline. Use it whenever you add a new mod (.oiv, .asi, .dll, .lua, .zip, or a folder).

How to use it.

1. Click Select File or Select Folder.
2. Check the detected file count shown below the buttons.
3. Click Install.

Under the hood. The pipeline is: analyze → map targets → safety gate → conflict check → double-consent (if needed) → on-demand elevation → backup → deploy → verify → rollback on failure. Typical mappings: .asi and loader .dll → game root; .lua → scripts\; .oiv → handled through the OpenIV core.

If any file would touch a protected core binary, the entire install is blocked. If existing files would change, you must give double-consent first. Any failure triggers an automatic rollback from the backup set — see Safety Model.

Install blocked? The mod tried to write a protected/core file (by design). Install failed? It was rolled back; check the newest file in logs\.

.zip archives

Selecting a .zip unpacks it into a private temp folder automatically — you never need to extract it yourself first; its contents are then analyzed exactly like a folder. Archive extraction is read-only toward the source .zip — the private temp folder is the only place written to.

.rar and .7z are not auto-extracted (there is no extractor for them built into .NET, and this tool avoids adding a third-party dependency just for that); pick those with your normal archive tool, then select the extracted folder instead.

Could not open this .zip? The archive is corrupt or password-protected — extract it yourself and select the folder. .rar/.7z are not supported? Extract with your usual archive tool first.

Menyoo XML files

What it is. Installs Menyoo save files (.xml) into the correct menyooStuff subfolder so Menyoo can load them in-game — object-spooner maps, saved vehicles, outfits, and weapon loadouts.

How to use it.

• Automatic: click Select File, choose the .xml, and the app reads its root element to pick the right subfolder. Then click Install.
• Manual: click Menyoo XML to reveal four buttons, then click the one for the folder you want. A file picker opens; choose the .xml and click Install. The four targets are:
  • Outfit → …\Grand Theft Auto V\menyooStuff\Outfit
  • Spooner → …\Grand Theft Auto V\menyooStuff\Spooner
  • Vehicle → …\Grand Theft Auto V\menyooStuff\Vehicle
  • WeaponsLoadout → …\Grand Theft Auto V\menyooStuff\WeaponsLoadout

Auto-detection inspects the XML root element (e.g. SpoonerPlacements → Spooner, Vehicle → Vehicle, OutfitStyle/Ped → Outfit, WeaponLoadout/Loadout → WeaponsLoadout). The folder names are fixed and match Menyoo's on-disk layout exactly. The file is then deployed through the standard install pipeline: overwriting an existing save triggers double-consent and the original is backed up first.

"Not a recognized Menyoo XML"? The root element wasn't recognized; turn on Menyoo XML and pick the correct folder button to place it manually.

Add-on vehicles (dlcpacks)

What it is. Installs add-on content packaged as a folder containing dlc.rpf.

How to use it.

1. In Settings, choose Assisted or Advanced (Safe mode rejects dlcpacks — see Managing Installed Mods → Install Modes).
2. Select the folder that contains dlc.rpf and click Install.
3. Assisted: paste the copied line into dlclist.xml in OpenIV and save. Advanced: the entry is added automatically to the dlclist.xml you configured.

The pack is copied to mods\update\x64\dlcpacks\<name>\ (the name is lowercased). The registration line is dlcpacks:\<name>\. The app never writes inside encrypted .rpf archives. Uninstalling removes the dlcpack files and, in Advanced, the dlclist.xml entry.

Not detected as a dlcpack? The selected folder (or one sub-folder) must directly contain dlc.rpf.

Mod conflict detection

What it is. A pre-install check that warns when a mod you're about to install would overwrite files already deployed by another installed mod. It runs automatically on every install — you don't trigger it manually.

If overlaps are found, a dialog lists each conflicting file and the mod that already owns it. Choose Install anyway to continue (you still pass through the normal overwrite double-consent) or Cancel to stop with no changes. Detection is advisory and read-only; it never changes files by itself.

The Installed Mods page also warns when two or more enabled mods already overlap — same file, or the same dlcpack name — see Managing Installed Mods.