- Grimoire Mod Manager on Linux: supports both AppImage and Debian package formats for managing Deadlock mods.
- Two install options: AppImage for any distribution, Debian package for Ubuntu-based systems.
- Key requirement: Deadlock must be installed and its directory correctly detected by Grimoire.
- Prefix matters: under Steam Play/Proton, Grimoire and the game should use the same game path.
- Recovery: snapshots and profiles let you roll back to a clean mod setup at any time.
Grimoire Mod Manager Linux Overview
Grimoire Mod Manager is a free, open-source mod manager for Deadlock that officially supports Linux alongside Windows and macOS Apple Silicon builds. On Linux, the manager handles the same core workflow as on other platforms: browsing GameBanana mods, 1-Click installs, load order control, conflict detection, Hero Locker, profiles, and vanilla launch. The current official version is v1.32.0, distributed through the official website and the GitHub releases page.
AppImage
- Distribution-independent
- No package installation needed
- Make executable, then run
- Best for Arch, Fedora, openSUSE
Debian Package
- System-managed install
- Integrates with apt workflow
- Best for Ubuntu, Debian, Mint
- Easier updates via package tools
Core Features
- GameBanana browsing
- Load order and conflicts
- Hero Locker and profiles
- Vanilla launch support
Pick the AppImage if you switch distributions often or want a self-contained app. Choose the Debian package if you prefer managing software through your system's normal package workflow.
Installation Comparison
| Aspect | AppImage | Debian Package |
|---|---|---|
| Compatibility | Most distributions | Debian, Ubuntu, Mint |
| Installation | chmod +x, then run | Install via system package tools |
| Updates | Replace downloaded file | Managed through package workflow |
| Permissions | Manual executable flag | Handled by installer |
| Best for | Portability and flexibility | System integration |
After downloading, verify the file against the checksums published with each release on GitHub. Comparing the local SHA256 value with the published one confirms the download is intact.
| System Requirement | Details |
|---|---|
| Operating system | Linux (also Windows, macOS Apple Silicon) |
| Game | Deadlock installed and launching normally |
| Source | MIT-licensed open source |
| Release channel | Official website and GitHub releases |
Download Grimoire only from the official website or GitHub repository. Third-party mirrors may distribute modified or outdated builds.
Linux Setup Walkthrough
Follow this sequence for a clean first-run configuration on Linux. The process mirrors the general beginner workflow but includes Linux-specific checks for paths and permissions.
Install Deadlock First
Confirm Deadlock is installed through your normal game library and launches correctly before configuring Grimoire. Close the game completely before touching mod files.
Install and Launch Grimoire
Make the AppImage executable or install the Debian package, then start Grimoire. Allow it to complete first-time setup and grant any permission prompts it requests.
Confirm the Game Location
Point Grimoire at the actual Deadlock installation directory, not a shortcut or unrelated parent folder. Under Steam Play, verify the game prefix path matches what Grimoire detected.
Review the Interface
Open the library view, identify enable/disable controls, and check for warning indicators before starting the game.
Enable One Mod and Test
Install a single mod, confirm it appears in the library, enable it, and launch Deadlock to verify. One mod at a time makes problems easy to isolate.
The most common Linux setup failure is Grimoire watching a different game installation than the one your launcher runs. Apply a small test mod and confirm the target files actually change in the expected installation.
Linux Troubleshooting
When something breaks, start from the visible symptom and make the smallest controlled change possible. Preserve a working profile or snapshot first so you can always return to a clean state.
| Symptom | Likely Cause | Fix |
|---|---|---|
| Mods enabled but invisible in-game | Competing mod overrides the same file, or profile not applied | Check conflict indicators, adjust load order, restart game |
| Game crashes after enabling a mod | Incompatible combination in loadout | Disable newest mod, restore snapshot, re-enable one by one |
| Load order changes have no effect | Game cached assets, or preferred mod not in override position | Close game fully, reorder, apply profile, restart |
| Grimoire and game in different prefixes | Manager watching wrong Steam Play prefix | Re-select correct game path, verify read/write access |
| Want a clean game again | Active replacements still deployed | Disable mods, use restore/undeploy workflow, test vanilla launch |
Changing managed files while Deadlock is running can prevent updates from applying correctly. Fully exit to the desktop before installing, removing, or reordering mods.
For persistent issues, the official documentation and the GitHub issues page are the primary resources, and the official Discord (linked at the bottom of the website) hosts an active community.
Post-Setup Checklist
Linux Setup Milestones:
- Deadlock verified to launch normally before modding
- Grimoire installed via AppImage or Debian package
- Game directory confirmed with a test deployment
- First mod enabled and verified in-game
- Working loadout saved as a profile
Create a snapshot of your working loadout before testing new mods or reorder experiments. Restoring a known-good snapshot is faster than manually undoing changes.
FAQ
Q: Does Grimoire Mod Manager officially support Linux?
Yes. The official website lists Linux among supported platforms, offering AppImage and Debian package downloads alongside Windows and macOS Apple Silicon builds. All releases are published on the official GitHub repository.
Q: Should I use the AppImage or the Debian package on Linux?
Use the AppImage if you want a distribution-independent, self-contained build — it runs on Arch, Fedora, and most other distributions once marked executable. Choose the Debian package if you are on Ubuntu, Debian, or Mint and prefer managing the app through your system's package workflow.
Q: Why do my mods not appear in Deadlock on Linux?
Common causes include another mod overriding the same file, the profile not being applied after changes, or Grimoire pointing at a different game installation than the one your launcher runs. Check conflict indicators, verify the game path, apply the profile, and restart the game.
Q: How do I return Deadlock to an unmodded state?
Disable active mods or switch to an empty profile, then use Grimoire's restore, undeploy, or snapshot workflow. Launch Deadlock without mods to confirm the clean state, and keep an exported profile if you want to reinstall the same loadout later.