The reversible install workflow
- Record the Gothic build shown by Steam and the mod's tested or last-updated build.
- Back up
SaveGames, configuration files, and the current mod profile. - Choose one install method: G1L, the author's manual steps, or the loader the mod explicitly requires.
- Enable one mod and load a copied test save.
- Exit, check logs or visual behavior, and only then add another mod.
The commonly reported Windows save path is:
C:\Users\<name>\AppData\Local\G1R\Saved\SaveGames\
G1L and loader-specific paths
G1L is a community Windows mod manager, not an official Alkimia tool. Its current listing supports several formats, including package files, UE4SS-style mods, blueprint plugins, ReShade, and Engine.ini changes. That does not make all formats interchangeable.
Before and after an official patch
Alkimia's official patch guidance warns players to remove mods before updating because incompatible files can cause abnormal behavior. Disable everything, update, verify or repair the game files, and launch once without mods. Update the manager and loader before re-enabling the first mod.
Clean recovery order
- Disable the most recently added mod.
- Restore its modified configuration file.
- Verify the game files in the store client.
- Test a copied save in a clean game.
- Restore the backup only after the clean installation launches correctly.
Do not stack multiple Engine.ini packages unless their authors explicitly document compatibility; those files often overwrite the same settings.