Gothic 1 Remake Mods: Install, Fix, and Manage Mods

Choose the page that matches the problem

• Starting from a clean game: use How to Mod Gothic 1 Remake for the backup-first install sequence and format-specific paths.
• The game or mod stopped working: use Gothic 1 Remake Mods Not Working to separate a loader failure, missing dependency, patch mismatch, and save problem.
• Choosing a tool: use Gothic 1 Remake Mod Manager for the current G1L, Vortex, and manual-install tradeoffs.

These pages intentionally do not compete for the same search phrase. This hub answers the broad mods query; each child page owns one distinct task.

What is current on PC

G1L is an unofficial, game-specific manager whose author documentation covers pak files, UE4SS Lua and DLL mods, blueprint plugins, Engine.ini changes, ReShade presets, and several other layouts. Nexus also lists a Gothic 1 Remake support extension for Vortex. Neither tool turns every archive into the same format, and the instructions supplied by the individual mod remain authoritative.

The rules that apply to every install

1. Confirm the game build and the mod's supported build.
2. Back up SaveGames and any configuration file the mod changes.
3. Use one manager or one manual method for the first test.
4. Enable one mod, then load a copied save.
5. Remove mods before an official update and prove the clean game works before restoring them.

The commonly reported Windows save path is:

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

Why mods fail after patches

An official patch can change game files, loaders, or assumptions used by a mod. Alkimia's patch guidance tells players to remove mods before updating. A safe recovery therefore begins with a clean launch, not with installing another loader on top of the first one.

If the clean game fails too, verify the installation in the store client before diagnosing the mod. If the clean game works, add back the required loader and one current mod at a time.