- Grimoire Mod Manager config setup starts with picking the right build for your OS and linking your Deadlock install.
- Game path selection is the single most important step; wrong paths cause most "mods not loading" issues.
- Profiles and snapshots should be created before your first deployment so you can always roll back.
- Close Deadlock fully before changing any mod configuration or load order.
- Verify the connection between Grimoire and the game by enabling one test mod first.
Choosing the Right Grimoire Build
Grimoire Mod Manager config setup begins with selecting the correct package for your operating system. Grimoire supports Windows, Linux, and macOS (Apple Silicon), and each platform offers different package formats that affect how the tool is installed and updated.
| Platform | Package | Best For | Setup Notes |
|---|---|---|---|
| Windows | Installer | Most desktop users | Standard install, appears in Start menu |
| Windows | Portable | Self-contained use | Runs from extracted folder, no install |
| Linux | AppImage | Distros without deb support | Make executable before launch |
| Linux | Debian Package | Ubuntu/Debian-based systems | Managed via system package workflow |
| macOS | macOS Application | Apple Silicon Macs | Follow security prompts on first launch |
Installer Route
- Simplest setup
- Regular desktop integration
- Best for first-time users
Portable Route
- No installation needed
- Keeps app in one folder
- Works from removable drives
Checksum Verification
- Compare local file hash
- Match published release value
- Confirms download integrity
Deadlock must already be installed and able to launch normally before you begin Grimoire Mod Manager config setup. A clean first launch confirms the base game works, and the game should be closed completely before any mod files are touched.
First-Run Configuration Steps
The first session with Grimoire typically involves launching the app, handling permission prompts, and pointing the manager at your Deadlock installation. Follow this sequence to avoid the most common setup failures.
Launch Grimoire
Start Grimoire from your installed application or portable folder and allow first-time setup to finish. If your OS shows a security or permission prompt, review it and permit Grimoire to continue so it can access game files and its own application data.
Confirm the Deadlock Location
When prompted, select the actual Deadlock installation directory. Grimoire needs the real game folder to identify the files it manages, not a shortcut or an unrelated parent directory.
Verify the Connection
Check that Grimoire recognizes the game before importing any content. Revisit the game path settings if the manager cannot find the installation—this is the most common config failure point.
Review the Main Interface
Open the Library view to see installed mods, browse controls, and status indicators. Understanding enable/disable controls now makes troubleshooting far easier later.
Enable One Test Mod
Install a single mod, confirm it registers in the list, enable it, and launch Deadlock to verify. Starting with one mod keeps results easy to isolate.
Do not select a shortcut, a Steam library folder, or a parent directory when Grimoire asks for the game location. Always point to the Deadlock installation itself, otherwise deployments will target the wrong files and mods will not load.
Profiles, Snapshots, and Mod Paths
Once the basic connection works, configure your safety net before adding more mods. Grimoire's Profiles and Snapshots features let you save complete loadouts and restore known-good states, which is essential when experimenting with load order.
| Feature | What It Does | When to Use It |
|---|---|---|
| Mod Profile | Saves selected mods plus their configuration as a loadout | Switching between competitive, test, and cosmetic setups |
| Share Code | Compact code that recreates a loadout on another install | Sharing configs with friends or the community |
| .modprofile.json | Export/import file for full configuration transfer | Backups and migrating between machines |
| Snapshot | Captures current deployment state | Rolling back after a failed experiment |
| Vanilla Launch | Starts Deadlock without mods | Verifying issues are mod-related |
Export your working profile to a .modprofile.json file after confirming your mods are enabled, and take a snapshot before every load-order experiment. This keeps a recoverable state no matter what breaks during testing.
A safe profile workflow follows a simple loop: export the working profile, share or store it, import it when needed, review missing or conflicting entries, and only apply the loadout after verification.
Platform-Specific Config Checks
CrossOver and Linux setups add extra variables because the manager and the game may live in different prefixes or paths. Use this checklist whenever Grimoire behaves differently on macOS CrossOver or Linux.
Platform Config Checklist:
- Confirm Grimoire targets the same Deadlock install used by your launcher
- Verify the active CrossOver bottle or Linux game prefix
- Check read/write permissions on mod and game directories
- Deploy a small test profile and confirm target files change
- Return to a clean profile before testing another path
| Symptom | Likely Cause | First Fix |
|---|---|---|
| Manager opens, mods never apply | Game path points to wrong install | Re-select the actual game directory |
| Mods apply on Windows but not CrossOver | Manager and game in different bottles | Match prefix paths |
| AppImage will not launch | File not marked executable | Set executable permission |
| Profile changes have no effect | Game still running with cached assets | Fully restart Deadlock |
Never install, remove, or reorder mods while Deadlock is running. Exit to the desktop and wait for the game process to close, or updates may not apply correctly.
Setup FAQ
Q: Does Grimoire Mod Manager config setup require Deadlock installed first?
Yes. Install Deadlock through your normal game library and confirm it launches cleanly before configuring Grimoire. The manager needs an existing, working installation to locate and manage game files.
Q: What directory should I select when Grimoire asks for the game location?
Select the actual Deadlock installation folder, not a shortcut, Steam library root, or unrelated parent directory. If Grimoire cannot find the game, revisit the game path settings and point to the real install.
Q: How do I undo a bad configuration?
Restore the latest known-good snapshot or import a previously exported .modprofile.json file. Disable active mods or switch to an empty profile, apply the restore, then relaunch Deadlock to confirm the clean state.
Q: Why did my mods stop working after a Deadlock update?
Game updates can invalidate mod deployments. Restore original files via Grimoire's restore or snapshot workflow, launch unmodded to confirm the game works, then re-enable mods one at a time to find what needs updating.