Gothic 1 Remake Mods Not Working: Fix Checklist

Start with the clean-game test

1. Back up SaveGames and the current mod profile.
2. Disable the manager profile or remove the last manually installed mod according to its own uninstall notes.
3. Verify the game files in the store client.
4. Launch the game without mods and open a copied save.

If the clean game also fails, stop changing mod folders. Repair the base installation or current game configuration first. If the clean game works, the failure is isolated to a loader, dependency, mod file, configuration change, or save state.

The game starts but the mod has no effect

Check these in order:

1. Wrong mod type: pak, UE4SS, blueprint, ReShade, movie, and configuration mods do not share one destination.
2. Missing dependency: UE4SS Lua and DLL mods need UE4SS; blueprint plugins may require SimpleModLoader; fyryNy plugins require that loader.
3. Wrong layout: the current G1L documentation supports the game's expected flat layout while respecting an existing supported nested UE4SS install. Do not mix both by hand.
4. Disabled profile or mod: confirm the item is enabled in the same profile used to launch the game.
5. Build mismatch: compare the game's current build with the mod page and latest file date.

Do not solve an unknown format by copying the archive into several folders. Duplicate pak files and duplicate loaders make the next failure harder to isolate.

Failed to load UE4SS.dll

Use the manager's documented Fix UE4SS or reinstall the exact loader build required by the current mod instructions. Keep one supported layout, then retest with one UE4SS mod.

G1L's current health check also flags a missing Visual C++ runtime, a broken UE4SS proxy, or another DLL injector beside the game executable. Treat the diagnostic as a lead, not proof: record the message before changing files, and use the tool's copy-diagnostics output when asking the author for help.

The game crashes after a patch

Alkimia's official update guidance warns that mods can produce abnormal behavior across game updates. Return to this sequence:

1. Disable all mods and restore modified configuration files.
2. Verify game files and launch the updated clean game once.
3. Check the build in Settings.
4. Update the manager or loader.
5. Update one mod and test a copied save.
6. Reintroduce the remaining mods individually.

A mod works on a new save but not the main save

That result points to a save-state or persistent script difference rather than a basic install failure. Keep the main save untouched, reproduce the result on copies, and read the mod's removal warning before loading a heavily modded save without its dependencies.

What to include in a support request

• Game build and store
• Manager, loader, and mod versions
• Exact archive name and source URL
• Install method and active profile
• Full error text or diagnostic output
• Whether the clean game launches
• Whether the problem also occurs on a copied new save

This evidence lets a mod author distinguish a broken release from a local path or dependency problem.