Priority and state

The Installed tab is the source of truth for how Modrex presents your managed mods. Disk layout still matters, so Modrex writes only the parts that each game target supports safely.

Visual order

Drag mods and folders in the Installed tab to organize them. Folder order and mod order are saved by Modrex and restored when you reopen the app.

Priority is scoped to siblings in the same folder and target. Mods in different folders or different targets do not share one global order.

Filename prefixes

Some Unreal .pak targets load files alphabetically. For those targets, Modrex writes numeric prefixes such as 001_ and 002_ to the filenames on disk.

Keep higher-priority .pak mods higher in the list. Modrex translates that visual order into filenames the game can load predictably.

Directory-based targets are not renamed for priority. Modrex still tracks them, lets you place them in folders, and lets you enable or disable them.

Enabled state

Disabling a mod preserves the file but moves it out of the active target so the game ignores it.

For file-based .pak targets, disabled files are kept under a disabled folder with a .disabled suffix. For directory targets, disabled folders are moved under that target’s disabled folder.

Enable the mod again to move it back to the active target.

Untracked mods

Modrex periodically scans each game’s mod folders for files it isn’t already tracking - for example, mods you placed manually outside Modrex. These show up in the Installed list automatically.

A newly discovered mod is identified by checking its file hash against Modrex’s mod index. A match fills in the real name, modworkshop ID, and version. If there’s no match, the mod still appears, named after its filename, with a negative ID standing in for an unknown modworkshop ID - this isn’t an error, just an unrecognized file. It’s re-checked on later scans in case the index catches up.

Missing files

A missing file badge means Modrex has state for a mod, but the file or folder no longer exists where Modrex expects it. This usually happens after manual deletion, a moved game folder, or external cleanup.

Use Reinstall to restore the files when Modrex can identify the original download, or uninstall the entry to remove the stale state.

State file

Modrex stores managed mod state in .modrex.json inside the active game’s primary mods folder. Keeping the state near the managed files helps the setup travel with the game folder across dual-boot or portable installs.

Older .pd3mm.json state files are migrated automatically.