- Grimoire Mod Manager permissions control how the tool reads and writes your Deadlock game files.
- File system access to the Deadlock installation directory is the single most important permission.
- First-launch prompts on Windows, Linux, and macOS must be reviewed and approved before mod deployment works.
- Read and write access to both the game folder and Grimoire's own application data is required.
- Most "mods not loading" reports trace back to wrong paths or blocked write access, not broken mods.
Why Grimoire Mod Manager Permissions Matter
Grimoire Mod Manager is a free, open-source mod manager for Deadlock that installs mods, manages load order, detects conflicts, and saves profiles. To do any of that, it needs permission to modify files inside your Deadlock installation. If those permissions are missing or misconfigured, mods may appear installed in the manager yet never show up in-game.
There are three permission layers to understand:
| Permission Layer | What It Covers | What Breaks Without It |
|---|---|---|
| Game directory access | Reading and writing files in the Deadlock install folder | Mods fail to deploy or do not appear in-game |
| Application data access | Grimoire's config, profiles, and snapshots | Settings, profiles, and share codes fail to save |
| OS security prompts | Windows SmartScreen, macOS Gatekeeper, Linux exec bits | The app refuses to launch on first run |
Before adjusting anything, close Deadlock completely. Changing managed files while the game is running can prevent permission and deployment changes from applying correctly.
Permissions by Platform
Each supported platform handles permissions differently. Here is what to expect on first launch.
Windows
- Installer or Portable builds behave the same for permissions
- SmartScreen may prompt on first launch
- Avoid installing into protected folders like Program Files if write errors appear
- Steam library folders may need normal user write access
Linux
- AppImage must be marked executable before launch
- Debian package installs through the system package workflow
- Check that your user owns the Deadlock prefix or game path
macOS
- Apple Silicon support via native or compatibility setups
- Gatekeeper prompts may appear on first launch; review and allow
- CrossOver users must match bottle paths to the game install
When Grimoire asks for the game location, select the actual Deadlock installation directory. Do not select a shortcut, a Steam library root, or an unrelated parent folder. A wrong path is the most common cause of permission-style failures.
Step-by-Step Permission Setup
Follow this sequence on a fresh install to avoid nearly all permission problems.
Install Deadlock First
Install Deadlock through your normal game library and confirm it launches normally. Close the game fully before continuing, so no files are locked during setup.
Launch Grimoire and Approve Prompts
Open Grimoire from your installed application or portable folder. If the operating system shows a security or permission prompt, review it and allow Grimoire to continue. First launch may request access to game files and its own application data.
Confirm the Game Location
Point Grimoire to the real Deadlock installation directory when prompted. Verify that Grimoire recognizes the game before importing or enabling any content.
Verify Write Access
Install one small test mod, enable it, and launch Deadlock. If the mod appears in-game, read and write permissions are working end to end.
Snapshot Your Working Setup
Once deployment works, save a snapshot or export a profile. This gives you a known-good state to restore if a later permission or conflict issue appears.
A single test mod that appears in-game confirms both the game path and file permissions are correct. You can then build out your full loadout with confidence.
Troubleshooting Permission Errors
When something goes wrong, match the symptom to the likely permission cause before making changes.
| Symptom | Likely Permission Cause | Fix |
|---|---|---|
| Grimoire will not launch | OS security prompt was dismissed, or AppImage not executable | Re-run and approve the prompt; mark AppImage executable |
| Mods enabled but absent in-game | Game path wrong, or write access blocked | Re-select the real install directory; check folder write rights |
| Profile or settings not saving | Application data folder access blocked | Run from a normal user account; avoid restricted system folders |
| Mods deploy on one setup but not another | Different prefix, bottle, or install used by the launcher | Match Grimoire's path to the active game client installation |
| Changes have no visible effect | Game running with cached assets during change | Close Deadlock fully, apply the loadout, restart |
Start with the visible symptom and make the smallest controlled change possible. Preserve a working profile or snapshot before troubleshooting so you can always return to a clean state.
Use this checklist whenever permission problems appear:
Permission Fix Checklist:
- Close Deadlock and Grimoire completely
- Confirm the game path points to the real install directory
- Approve any pending OS security prompts on relaunch
- Verify the account has read and write access to game and app data folders
- Deploy one test mod and confirm it appears in-game
- Save a snapshot of the working configuration
FAQ
Q: Does Grimoire Mod Manager need administrator permissions?
Not usually. Grimoire only needs read and write access to the Deadlock installation folder and its own application data. Run it from a normal user account; only use elevated permissions if your game folder requires them for writes.
Q: Why do my mods show as enabled but never appear in-game?
This is typically a path or permission problem rather than a broken mod. Confirm the correct profile is active, verify the game path points to the actual Deadlock installation, check load order and conflict indicators, and restart Deadlock after applying the loadout.
Q: How do permissions differ for the Linux AppImage versus the Debian package?
The AppImage must be marked executable before it will launch, and your user must own or have write access to the game directory. The Debian package installs through the system package workflow and follows standard user-level file permissions afterward.
Q: Can I restore the original game files if permission changes go wrong?
Yes. Disable active mods or switch to an empty profile, then use Grimoire's restore, undeploy, or snapshot workflow. Verify the correct original installation is selected and launch Deadlock without mods to confirm the clean state.