- Grimoire Mod Manager fix mods starts with one rule: change one variable, test, repeat.
- Mods not loading usually trace to load order, wrong game path, or another mod overriding files.
- Snapshots and profiles let you restore a known-good loadout before experimenting further.
- Always close Deadlock before installing, disabling, or reordering mods.
- Restore a snapshot when multiple changes make the problem unclear.
Why Mods Break: Common Failure Categories
When Grimoire Mod Manager users report that mods stopped working, the cause almost always falls into one of a few categories. Before touching anything, identify which category your symptom belongs to — this single step saves the most time.
| Symptom | Likely Category | First Action |
|---|---|---|
| Mod enabled but no effect in-game | Load order / conflict | Check conflict indicators |
| Game crashes after new mod enabled | Incompatible combination | Disable the newest mod first |
| Grimoire cannot find Deadlock | Wrong game path | Re-select the real install directory |
| Mod appears installed but not registered | Extraction / archive structure | Re-import, keep author's folder layout |
| Everything worked until a game update | Stale deployment | Restore, then re-apply mods one by one |
| Wrong mod takes priority | Load order position | Move preferred mod to effective override slot |
Close Deadlock completely before managing mods. Changing managed files while the game is running can prevent updates from applying correctly, and cached assets may keep showing old results even after a correct fix.
Fix Mod Conflicts with Load Order
When two or more mods replace the same Deadlock file — two skins for the same hero, two crosshair packs, two audio replacements — only one can win. Grimoire's conflict detection highlights these overlaps, and the load order decides which replacement is actually applied.
Visual Mods
- Two skins on one hero cannot both show
- Give the preferred skin the higher priority
- Disable duplicates when testing
HUD and Crosshairs
- Full HUD packs override small tweaks
- Place the pack that defines the final layout on top
- Only one crosshair replacement appears
Audio Packs
- Overlapping sound events compete for files
- Some sounds may come from each pack
- Use order to pick the desired source
When a broad combined pack fights with a specialized mod, place the specialized mod above the broad pack so its focused change stays visible. Specialized overrides general.
Step-by-Step: Isolate and Fix a Broken Mod
This isolation workflow resolves most "mods not loading" cases without rebuilding your entire setup.
Preserve Your Working State
Export the current profile to a .modprofile.json file or save a snapshot before making any change. This gives you a guaranteed way back.
Confirm the Basics
Verify the correct profile is active, the game path points at the real Deadlock installation, and Deadlock is fully closed.
Disable the Suspect Mod
Disable only the most recently added or suspected mod, apply the change, launch Deadlock, and test the exact affected asset.
Binary-Test Conflicts
For a flagged conflict, disable one side and test, then re-enable it and disable the other. The failing side (or the interaction) reveals itself quickly.
Restore or Rebuild
If experiments made things worse, restore the known-good snapshot and reintroduce mods one at a time, testing after each addition.
Change only one variable per test — one mod, one reorder, one setting. Record the working order so you can reproduce it and spot the first change that reintroduces a problem.
Recovery Scenarios and Platform Checks
| Scenario | Recommended Fix |
|---|---|
| Game will not start after mods applied | Restore latest known-good profile/snapshot, test clean launch, re-add mods one by one |
| Want to return to vanilla | Disable all mods or switch to an empty profile, use restore/undeploy workflow, verify clean launch |
| macOS CrossOver issues | Confirm Grimoire and Deadlock use the same bottle and the real game directory |
| Linux permission problems | Verify the manager can read/write both mod and game directories; test with a small profile |
| Mod count limits | Trim duplicates and disabled leftovers; keep the active loadout lean |
Never point Grimoire at a shortcut, a library folder, or a parent directory. Selecting anything other than the actual Deadlock installation is one of the most common reasons deployment silently fails.
Fix-It Checklist:
- Deadlock fully closed before changes
- Correct game installation path confirmed
- Working profile exported or snapshot saved
- Conflict indicators reviewed in the mod list
- Only one variable changed per test
- Known-good snapshot restored if needed
FAQ
Q: Why is my mod enabled in Grimoire Mod Manager but not showing in Deadlock?
Usually another mod overrides the same file, the game needs a restart to reload the asset, or the active profile was not applied after your change. Check conflict indicators, disable competing replacements, apply the profile, and restart the game.
Q: How do I fix two mods that replace the same file?
Keep both enabled and change only their relative order, placing the preferred replacement in the effective override position. Apply the loadout and restart Deadlock. If the result is unchanged, disable one mod and binary-test to find the culprit.
Q: When should I restore a snapshot instead of troubleshooting?
Restore a known-good snapshot when a load-order experiment creates new conflicts, original assets stop appearing correctly, or several stacked changes make the source of the problem unclear. Then reintroduce mods one at a time.
Q: Can I get my original unmodded game back?
Yes. Disable active mods or switch to an empty profile, use Grimoire's restore or undeploy workflow, and launch Deadlock without mods to confirm the clean state. Keep your exported profile if you want the same loadout later.
For official documentation and release notes, see the Grimoire docs and the GitHub repository.