- Grimoire Mod Manager use configs means saving Deadlock mod loadouts as reusable Profiles.
- A Mod Profile stores which mods are enabled and their ordering for a specific playstyle.
- Share codes and .modprofile.json files move configs between users and installations.
- Snapshots protect a working setup before you experiment with new loadouts.
- Always apply a profile and restart Deadlock to confirm the config took effect.
What Configs Mean in Grimoire Mod Manager
In Grimoire Mod Manager, a "config" is a saved arrangement of Deadlock mods: which entries are enabled, how they are ordered, and which overrides (such as Hero Locker selections) are active. Instead of toggling dozens of mods by hand every time you want a different setup, you save that arrangement as a Mod Profile and switch between configs in seconds.
Grimoire supports three related configuration layers, and understanding how they differ is the foundation of good config hygiene.
| Config Type | What It Stores | Best Use Case |
|---|---|---|
| Mod Profile | Enabled mods, load order, locker overrides | Switching between playstyles (competitive, skins-only, testing) |
| .modprofile.json file | A full exported profile as a portable file | Backups, migration, archiving versions |
| Share Code | A compact code representing a profile | Sending a loadout to friends or a community |
| Snapshot | A point-in-time capture of your applied setup | Recovery after a failed experiment |
| Vanilla Launch | No mods applied at all | Verifying base-game behavior |
Competitive Config
- Minimal mods, crosshair + HUD only
- Fastest way to keep load clean
- Easy to verify against unmodded play
Cosmetics Config
- Skins, ability colors, sounds via Hero Locker
- Highest overlap risk between mods
- Save before every batch change
Testing Config
- One newly enabled mod at a time
- Isolates conflicts quickly
- Revert with a snapshot restore
Give every profile a name that describes its intent, such as "Ranked-Minimal" or "Skin-Testing". Recognizable names make it far easier to pick the right config under pressure and to spot stale experiments you can delete later.
Creating and Applying a Mod Profile
Building your first config follows a simple sequence: arrange the mods, save the arrangement, then apply it before launching the game. The manager handles the file bookkeeping, but the discipline of saving before changing is yours.
Arrange Your Loadout
Enable the mods you want in this config and set their load order. Place the preferred replacement in the effective override position when two mods touch the same asset.
Save the Profile
Create a new profile from the current active loadout and name it after its purpose. Save before making further changes, so the profile captures exactly what you arranged.
Apply Before Launching
Switch to (or re-apply) the profile so the arrangement is deployed to the game files. Applying after changes is a commonly missed step that makes mods appear inactive.
Restart and Verify
Launch Deadlock only after the profile has applied, and confirm the changed asset in-game. Restart again if a previously cached asset has not refreshed.
Iterate Safely
When experimenting, take a snapshot first, then change one variable at a time. Restore the snapshot if the experiment introduces a conflict you cannot isolate.
| Profile Action | Recommended Timing | Risk If Skipped |
|---|---|---|
| Save profile | Before changing any enabled mod | Config drift, lost arrangement |
| Export .modprofile.json | Before major changes or updates | No recovery point |
| Take snapshot | Before conflict experiments | Harder rollback |
| Apply profile | Before every game launch | Mods appear not to load |
| Delete stale profiles | After testing cycles end | Profile list clutter |
Close Deadlock completely before saving, applying, or reordering configs. Changing managed files while the game is running can prevent updates from applying correctly, leaving your loadout in an inconsistent state.
Sharing and Migrating Configs
Configs are portable. A share code is the fastest way to hand a loadout to another player, while the .modprofile.json export suits backups and moving between machines.
Export the Working Profile
Confirm the desired mods are enabled and ordered correctly, then export the profile to a .modprofile.json file. Keep the file with the profile name and a version note.
Generate the Share Code
Create a share code from the profile you want to distribute. Copy the complete code without adding spaces or line breaks.
Send With Context
Include any required load-order or compatibility notes alongside the code so the recipient knows which mods take priority.
Import and Review
Import the received code or file into Grimoire, then review missing, disabled, or conflicting entries before applying anything.
Apply and Test
Apply the imported loadout and launch Deadlock only after verifying that every expected mod is present and enabled.
An imported config records mod selections and ordering; the underlying mods still need to be installed or available. If entries appear missing after import, install the referenced mods first, then re-apply the profile.
Config Troubleshooting and Recovery
| Symptom | Likely Cause | Fix |
|---|---|---|
| Applied config has no effect in-game | Profile not applied after change, or cached assets | Re-apply profile, restart Deadlock |
| Wrong mod wins after switching configs | Preferred mod not in override position | Adjust load order, re-apply, restart |
| Imported profile shows missing mods | Referenced mods not installed locally | Install mods, re-apply profile |
| Game crashes after config switch | Incompatible combination in the loadout | Restore last known-good snapshot, re-enable one at a time |
| Config appears to revert | Wrong profile active | Confirm the active profile before launching |
Config Safety Checklist:
- Export a .modprofile.json backup before major changes
- Snapshot the working loadout before experiments
- Exit Deadlock fully before changing configs
- Verify the correct profile is active before launch
- Test one changed mod at a time when debugging
When a config experiment goes wrong, restoring a known-good snapshot is faster and more reliable than manually undoing changes. Preserve that safety net before every risky edit, and reintroduce mods one at a time afterward.
Config FAQ
Q: What does 'use configs' mean in Grimoire Mod Manager?
It means saving your Deadlock mod arrangement as a Mod Profile, then switching between saved profiles instead of enabling and disabling mods manually. Each profile records the selected mods, their load order, and related overrides.
Q: How do I share a Grimoire config with a friend?
Generate a share code from the profile and send it along with any load-order or compatibility notes. Your friend imports the code, reviews any missing or conflicting entries, then applies the loadout before launching Deadlock.
Q: What is a .modprofile.json file for?
It is the exported profile file format used for backups, archiving, and transferring a full mod configuration between Grimoire installations. Keep a copy before making major changes so you can always restore the setup.
Q: Why did my config not apply in-game?
Common causes include not applying the profile after making changes, having the wrong profile active, or the game still running with cached assets. Re-apply the correct profile, restart Deadlock completely, and verify the targeted asset.