- Grimoire Mod Manager not working usually traces back to a bad game path, an unapplied profile, or a mod conflict.
- Mods not loading in Deadlock: verify the correct profile is active and restart the game after applying changes.
- Startup failures: restore a known-good snapshot before re-enabling mods one at a time.
- CrossOver and Linux: confirm Grimoire and Deadlock run in the same prefix or bottle with read/write access.
- Vanilla restore: use Grimoire's undeploy or snapshot workflow instead of manual file deletion.
Why Grimoire Mod Manager Stops Working
When Grimoire Mod Manager is not working as expected, the cause almost always falls into one of a few recurring categories. The manager itself is a free, open-source Deadlock mod manager that handles GameBanana browsing, load order, conflict detection, profiles, Hero Locker, and vanilla launches — so most failures come from the connection between the manager, the game installation, and the active mod loadout.
The table below maps the most common failure patterns to their likely root causes:
| Symptom | Likely Cause | First Action |
|---|---|---|
| Grimoire will not open | Permission prompt blocked or incomplete first-run setup | Re-launch and allow the security prompt |
| Mods enabled but no effect in-game | Profile not applied, or another mod overrides the same file | Check conflict indicators, restart Deadlock |
| Deadlock crashes after enabling a mod | Incompatible replacement or conflicting loadout | Disable the newest mod, restore a snapshot |
| Wrong skin or sound plays | Load order puts another mod in the override position | Move the preferred mod to the final position |
| Changes appear ignored | Game still running with cached assets | Fully exit the game, apply, then relaunch |
Always exit Deadlock completely before installing, removing, or reordering mods. Changing managed files while the game is running can prevent updates from applying correctly and produce confusing "not working" symptoms.
Fixes by Failure Type
Manager Fails to Start
- Re-run the installer or portable build
- Allow OS security prompts on first launch
- Verify the app data folder is writable
Mods Not Loading
- Confirm the correct profile is active
- Review load order and conflict warnings
- Restart Deadlock after applying changes
Game Crashes or Misbehaves
- Disable the most recent mod
- Restore a known-good snapshot
- Test with a minimal profile, then re-enable
When diagnosing a broken setup, disable all but the suspected mod, test, then re-enable entries one at a time. Record the working order and change only one variable per test — this quickly separates conflicts, priority errors, and installation problems.
Step-by-Step Recovery Workflow
Follow this sequence whenever Grimoire or your modded Deadlock setup breaks. Each step makes the smallest controlled change possible so you can identify the exact point of failure.
Close Everything
Exit Deadlock fully — to the desktop, not the background — and close Grimoire. Wait for both processes to end before making changes.
Verify the Game Path
Open Grimoire's settings and confirm it points to the actual Deadlock installation directory. Do not select a shortcut, library folder, or unrelated parent directory.
Restore a Known-Good State
Restore the latest working snapshot or profile. Launch the restored setup before re-enabling any mods to confirm the baseline works.
Reintroduce Mods One at a Time
Re-enable mods individually, testing after each change. The first entry that reproduces the problem is your culprit — disable it, update it, or adjust its priority.
Confirm and Save
Once everything works, save the arrangement as a profile and export a backup copy so recovery takes seconds next time.
Create or preserve a snapshot before any load-order experiment. If a test causes new conflicts or the original assets stop appearing correctly, restoring that snapshot returns you to a clean state immediately.
Platform-Specific Problems
Grimoire supports Windows, Linux, and macOS setups, but each platform has its own quirks when things go wrong.
| Platform | Common Issue | Resolution |
|---|---|---|
| Windows | SmartScreen or permission blocks on first launch | Review the prompt and allow Grimoire to continue |
| Linux | AppImage not executable | Make the AppImage executable before launching |
| Linux (Debian) | Package not applying system-wide | Use the Debian package for distro-managed installs |
| macOS / CrossOver | Manager and game in different bottles or prefixes | Point Grimoire at the installation the active client uses |
| All | Read/write denied on mod or game directories | Check folder permissions for the selected paths |
On macOS CrossOver or Linux compatibility layers, verify the active bottle or prefix and apply a small test profile. If the target files do not change in the expected installation, Grimoire is pointed at the wrong game directory.
Restoring Vanilla Deadlock
If you want to remove all active replacements and return to an unmodded setup, do it through Grimoire's workflows rather than manual deletion.
- Disable active mods or switch to an empty profile
- Use Grimoire's restore, undeploy, or snapshot workflow
- Verify the original game installation is selected
- Launch Deadlock without mods to confirm the clean state
- Keep an exported profile file separately if you may want the same loadout later
Not Working? Run These Checks First:
- Deadlock fully closed before any mod changes
- Correct game installation path selected in Grimoire
- Active profile applied after the last change
- Conflict warnings reviewed in the mod list
- Known-good snapshot or exported profile saved
For issues this guide does not cover, check the official documentation at the Grimoire docs, report bugs on GitHub Issues, or join the official Discord linked at grimoiremods.com — enter from the official site to avoid impersonated servers.
FAQ
Q: Why is my mod enabled in Grimoire but not showing in Deadlock?
Three common reasons: another mod overrides the same file, the game needs a full restart to reload the cached asset, or the selected profile was not applied after the change. Confirm the correct profile is active, check conflict indicators, temporarily disable competing replacements, then restart Deadlock.
Q: Grimoire Mod Manager is not working after a Deadlock update — what should I do?
Game updates can break installed mods or shift the game directory. Close both the game and Grimoire, verify the game path, restore a known-good snapshot, and check whether the affected mods have updated versions on GameBanana before re-enabling them.
Q: Deadlock crashes right after I enable a new mod. How do I fix it?
Disable the most recently added mod first. If the crash continues, restore a previous snapshot and test with a minimal profile. Re-enable mods individually and record the first change that reproduces the crash — that mod is incompatible or conflicts with your loadout.
Q: How do I get my original unmodded game files back?
Disable all active mods or switch to an empty profile, then use Grimoire's restore, undeploy, or snapshot workflow. Avoid manually deleting files. Launch Deadlock without mods to confirm the clean state, and keep an exported profile if you want to reinstall the loadout later.