-
Notifications
You must be signed in to change notification settings - Fork 0
Managing Installed Mods
What it is. A persistent list of every mod you've installed, with editable details — use it to curate the information that appears in the Excel export, or just to review what's installed.
Click Edit on a row to fill in Name, Link, Mod Type, Install Type, Spawn
Name, Show Name, and File Type. Files and Install Location are filled
automatically. Records are stored in installed_mods.json in the data directory and saved
immediately after every change. Editing only changes metadata — it never touches deployed game
files.
List looks empty? Only mods installed through this app are tracked; mods added by hand won't appear.
The Installed Mods page warns when two or more enabled mods overlap — either deploying to the same file (one overwrote the other) or registering the same dlcpack name — listing each conflict and the mods involved. This is advisory only; nothing is changed automatically.
What it is. Temporarily turns a mod off (and back on) without uninstalling it — handy for isolating conflicts or crashes, or for testing without a mod while keeping it ready to re-activate.
Each installed-mod row shows an Enabled/Disabled tag and a toggle button. Click Disable to deactivate, Enable to reactivate.
Disabling moves the mod's deployed files into a per-mod staging folder (disabled\<id>\) and
restores any originals the mod had overwritten, so the game returns to a clean state. Enabling
moves the staged files back into place. A small manifest records each file's original
location. Protected core files are never moved.
This is the same mechanism Game Setup and Launch → Launch Clean uses to temporarily disable every enabled mod for GTA Online.
Toggle did nothing? If the staging data is missing, the app marks the mod enabled to avoid getting stuck; re-install the mod if files are gone.
What it is. Removes a mod's deployed files and restores the originals it had overwritten, for when you want a mod gone for good.
Click Uninstall on a row and confirm the double-consent prompt. The deployed files are
deleted (protected files are always skipped), the backup set is restored, and for Advanced
add-ons the dlclist.xml entry is removed. The record is kept and moved to the uninstalled
set (so it still appears in the Excel export).
Uninstall failed? Check logs\; some files may be locked by a running game — close GTA V
and retry. (Uninstall is also blocked outright while the game process is detected as running.)
What it is. Controls how add-on content that needs dlclist.xml registration is handled,
plus the update-check toggle.
Open Settings from the sidebar and choose a mode:
- Safe — loose files and folders only.
-
Assisted — deploys the dlcpack folder, copies the
dlclist.xmlline to your clipboard, and opens the mods folder so you can apply it in OpenIV. -
Advanced (EXPERIMENTAL) — additionally auto-edits a writable
dlclist.xmlyou point to. It cannot write inside encrypted.rpfarchives.
Every settings change shows an "I know what I'm doing" acknowledgement that states exactly
what changed and what it does; cancelling reverts. Enabling Advanced first shows a
mandatory risk waiver (extreme risk, possible game-file corruption, you assume all risk)
gated behind a checkbox. Settings persist in settings.json.
Add-on won't register in Advanced? Make sure the configured dlclist.xml exists and is
writable (loose, not inside a .rpf).
What it is. Exports your installed/uninstalled mods to a styled .xlsx workbook — useful
to share your setup, back up your mod list, or move to another machine.
Click Export to Excel, choose a location, and save. The workbook has two sheets — Install Mods and Uninstall Mods — each with nine columns (Name, Link, Mod Type, Install Type, Spawn Name, Show Name, File Type, Files, Install Location), a frozen styled header, a clickable Link column, and rows sorted by Name.
Nothing to export? Install at least one mod first. Export failed? Make sure the target file isn't open in Excel.