Repository navigation
Linux Mod Manager
GameAtlas 2.4 includes a Linux-only managed mod library for users who do not have the official Windows Vortex workflow.
Windows users should continue to use Vortex or the game-specific official tool. The GameAtlas managed deployment interface is not shown on Windows.
GameAtlas creates or uses a per-game folder under:
~/Games/VortexMods/<Game Name>/
Place an extracted mod folder or a supported ZIP, RAR, or 7z archive in that folder, then select Refresh.
On Bazzite, /home/<user> and /var/home/<user> refer to the same home storage.
Select Extract & Preview for a supported archive. ZIP extraction is built in. RAR and 7z extraction uses detected lsar/unar support.
Extraction rejects unsafe paths, links, special files, password-protected archives, excessive entry counts or expanded sizes, and case-only collisions. Installers and scripts are never executed automatically.
Select an extracted folder to preview its payload. Review:
- File count and expanded size.
- Destination strategy.
- Existing game files that would be replaced.
- Overlap with other managed mods.
- The effective game-relative layout.
Select Install & Enable only when the preview matches the mod author's instructions. Fully exit the game first.
When GameAtlas recognizes an Unreal Engine package layout, it routes .pak payloads to the appropriate game content location rather than blindly copying them into the installation root. Because games can customize their folder structure, always verify the displayed destination.
Each installed mod records its source, payload, enabled state, priority, backups, metadata, and applicable Nexus provenance.
Disabling removes that mod's active layer while preserving its managed payload and metadata. Enabling rebuilds the effective deployment according to current priority and conflicts.
When two managed mods provide the same destination file, the higher-priority enabled mod wins. Reordering triggers a managed redeployment so the game directory reflects the current order.
This resolves file ownership between managed mods; it cannot determine whether two mods are logically compatible.
Profiles store groups of enabled mods and their effective order. Switching profiles redeploys the library to match the selected profile.
- Purge removes managed files from the game while retaining the library.
- Redeploy rebuilds the active deployment from managed state.
- Verify compares deployed files and backups with recorded state.
- Repair attempts to restore a consistent managed deployment.
- Remove uninstalls the selected managed mod and restores the correct lower-priority or original files.
Keep the managed-library data if you want GameAtlas to preserve rollback, verification, and redeployment capabilities.
Managed mods can store a display name, version, author, source page, notes, and Nexus game/mod/file identity.
An upgrade is transactional: GameAtlas prepares the new payload, preserves the mod's enabled state, profile membership, and priority, and advances its metadata only after the replacement succeeds.
See Nexus Mods Integration for automatic update detection and guided downloads.
- FOMOD installers are not supported.
- Nexus Collections are not supported.
- Game-specific installers and scripts are not executed.
- Plugin load orders outside file priority are not universally managed.
- Game updates and unmanaged manual changes can invalidate recorded state.
- GameAtlas cannot guarantee mod compatibility.
Use Verify after game updates or unexpected manual changes. Keep independent backups for important installations.