How to Mod Gothic 1 Remake

Before installing anything

1. Open the game once without mods and record the build displayed in Settings.
2. Copy the entire SaveGames folder somewhere outside the game and local-app-data folders.
3. Read the mod description for its required loader, dependencies, supported build, and uninstall steps.
4. Keep the original archive. It is your file manifest if a manual uninstall becomes necessary.

The commonly reported Windows save path is:

C:\Users\<name>\AppData\Local\G1R\Saved\SaveGames\

Identify the mod type first

The install location follows the mod type, not the filename alone. The G1L author documentation currently maps common types to these locations:

• UE4SS Lua or DLL mods: ...\G1R\Binaries\Win64\Mods\
• Pak mods: ...\G1R\Content\Paks\~mods\
• Blueprint plugins: ...\G1R\Mods\
• Engine.ini tweaks: %LOCALAPPDATA%\G1R\Saved\Config\Windows\Engine.ini
• ReShade presets and fyryNy's Loader: ...\G1R\Binaries\Win64\

Install with one method

G1L

Run the launcher from its documented release source, let it detect the game, install UE4SS only when the selected mod needs it, then import the untouched archive. Enable one mod and launch through the same profile. G1L's author documentation describes automatic save backups, dependency warnings, and reversible toggles, but it remains an unofficial community tool.

Vortex

Install the Gothic 1 Remake support extension from Nexus, then use Vortex only for mods whose page supports that workflow. A Vortex button does not override a mod author's requirement for a separate loader or manual dependency.

Manual installation

Use manual installation for a small, well-documented mod when the author lists every destination and removal step. Copy one archive's files, keep a text record of what changed, and do not combine it with a manager profile during the first test.

Test the installation

1. Launch the same clean save copy used for testing.
2. Confirm the mod's documented behavior instead of assuming that a successful game launch means it loaded.
3. Exit and check the manager diagnostics or loader log when the behavior is absent.
4. Add the next mod only after the first one works across a restart.

If the game launches but the mod has no effect, move to the mods not working diagnostic rather than reinstalling everything at once.

Before and after a game update

Disable or remove mods before the official update. Verify the clean installation, launch it once, and check the new build. Then update the manager, required loader, dependencies, and individual mod before enabling the first item on a copied save.