- Grimoire Mod Manager Deadlock config starts with linking the correct game directory on first launch.
- Load order decides which mod wins when two mods replace the same Deadlock file.
- Profiles and snapshots let you save, share, and restore complete mod configurations.
- Hero Locker handles per-hero skins, ability colors, and sound overrides.
- Vanilla Launch restores the unmodded game without deleting your setup.
Deadlock Config Basics in Grimoire Mod Manager
Grimoire Mod Manager is a free, open-source mod manager for Deadlock that keeps your entire mod configuration in one place. A working Deadlock config in Grimoire covers four layers: the game path, your enabled mod list and its load order, saved profiles, and cosmetic overrides through Hero Locker. Get each layer right and the manager can reliably deploy your mods, detect conflicts, and restore the vanilla game whenever you need it.
The core config surfaces you will work with are summarized below.
| Config Layer | What It Controls | Where in Grimoire |
|---|---|---|
| Game path | Which Deadlock installation receives mods | First-run setup / settings |
| Mod library | Enabled, disabled, and imported .vpk mods | Library page |
| Load order | Priority when files overlap | Library ordering controls |
| Profiles | Saved loadouts, share codes, .modprofile.json | Profiles page |
| Hero Locker | Per-hero skins, ability colors, sounds | Hero Locker view |
Always confirm Deadlock launches normally before configuring Grimoire. A clean base install makes it far easier to tell whether a later issue comes from the game or from your mod config.
First-Run Config: Linking Deadlock
The single most important config step is pointing Grimoire at the real Deadlock installation. Selecting a shortcut, a Steam library folder, or an unrelated parent directory is the most common reason deployments silently fail.
Close Deadlock
Exit the game to the desktop before touching mod files. Changes applied while the game is running may not deploy correctly.
Launch Grimoire
Open Grimoire from your installed application or portable folder and let first-time setup finish. Allow any permission prompts so the manager can access game files and its own data.
Select the Game Directory
When prompted, choose the actual Deadlock installation folder — the one containing the game client, not a shortcut.
Verify the Connection
Check that Grimoire recognizes the game before importing mods. If it cannot find the installation, revisit the path settings.
Enable One Test Mod
Install a single mod, confirm it appears in the library, enable it, and launch Deadlock to verify the pipeline end to end.
Do not point Grimoire at a shortcut, library root, or unrelated parent directory when the manager asks for the actual game location. Wrong paths cause "mods not loading" issues that are easy to mistake for conflicts.
For reference, the official documentation at grimoiremods.com/docs covers first-run setup in detail, and the source code is available on GitHub.
Load Order Config and Conflicts
Load order is the heart of any Deadlock config. When two enabled mods replace the same file, Grimoire uses ordering to decide which one wins — a later or higher-priority entry takes precedence. Deliberate ordering keeps your intended result intact.
| Mod Category | Priority Guidance | Conflict Result If Wrong |
|---|---|---|
| Hero skins | Preferred skin above competing skin for same hero | Lower-priority skin hidden or partially overridden |
| HUD / interface | Full HUD package above small tweaks to same elements | Mixed layout from different packages |
| Crosshairs | Only one active reticle; disable duplicates | Wrong or default crosshair appears |
| Audio packs | Preferred pack above packs changing same sound events | Sounds split between two packs |
| Combined packs | Specialized mods above broad visual packs | Broad pack overwrites specific changes |
When a mod appears installed but does nothing in-game, check the load order first. A competing replacement with higher priority is the most likely cause — not a broken download.
The conflict workflow follows a simple pattern: preserve a snapshot of the working setup, disable one side of the conflict, test, then re-enable and test the other side. This binary comparison tells you whether the problem is the mod itself or the interaction between two mods. If an experiment makes things worse, restore the known-good snapshot and reintroduce mods one at a time.
Profiles, Share Codes, and Hero Locker
Profiles turn a working loadout into a reusable, transferable config. Instead of rebuilding your mod collection by hand, you export it once and switch between setups instantly.
Mod Profile
- Saves the active mod selection as a named loadout
- Switch between competitive, test, and skin configs
- Keep experimental changes isolated from a stable setup
Profile File
- Export to .modprofile.json for backup and transfer
- Import to restore or move configs between installations
- Keep versioned copies before major changes
Share Code
- Compact code-based distribution of a full loadout
- Copy the code without spaces or line breaks
- Recipients import and review before applying
Hero Locker extends the config to per-hero cosmetics. Each hero can have an assigned skin, ability color treatment, or ability sound replacement, applied and removed independently of the rest of the loadout. When several cosmetic mods target the same asset, the selected override plus load order determines what actually appears in-game.
Most cosmetic overrides in Hero Locker affect only your local client. Other players will not see your custom skins, colors, or sounds.
Config Troubleshooting and Restore
Config problems almost always fall into a few recognizable patterns. Match the symptom first, then make the smallest change possible.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Mod enabled but invisible in-game | Higher-priority override or cached assets | Check order, disable competitors, restart game |
| Wrong profile applied | Profile not applied after change | Reapply profile and verify active list |
| Crash after new mod | Incompatible combination | Disable newest mod, restore snapshot |
| Game will not start | Incompatible replacement deployed | Restore latest known-good snapshot |
| Mods work on Windows but not Linux/macOS | Manager and game in different prefixes or bottles | Match prefixes and verify read/write permissions |
Always preserve a working snapshot before troubleshooting. If a repair attempt introduces a new problem, you can return to a clean state instead of untangling several changes at once.
To return to a fully unmodded game, disable active mods or switch to an empty profile, then use Grimoire's restore, undeploy, or snapshot workflow rather than manually deleting files. Launch Deadlock without mods to confirm the clean state, and keep your exported profile separate if you plan to reinstall the same loadout later.
Healthy Config Checklist:
- Game path points to the real Deadlock installation
- One test mod verified end to end before bulk installs
- Working loadout saved as a profile and snapshot
- Load order reviewed for overlapping files
- Vanilla restore tested at least once
FAQ
Q: What does the Grimoire Mod Manager Deadlock config include?
It covers the linked game directory, your enabled mod list and load order, saved profiles with share codes and .modprofile.json exports, Hero Locker cosmetic overrides, and snapshot/vanilla restore settings.
Q: Why does Grimoire need the exact Deadlock folder?
The manager deploys mods into the real game installation. Selecting a shortcut or a Steam library root means files land in the wrong place, which produces mods that never appear in-game.
Q: How do I fix two mods fighting over the same file?
Keep both enabled and change only their relative order, then apply and restart the game. If the result is unclear, disable one side and test, or restore a snapshot and reintroduce mods one at a time.
Q: Can I share my Deadlock mod config with friends?
Yes. Generate a share code or export a .modprofile.json file, send it with any load-order notes, and have recipients import and review the resulting loadout before applying it.