modde
modde is a game mod manager written in Rust that runs natively on Linux, macOS, and Windows. It gives you declarative, reproducible mod management with a virtual-filesystem deployment that keeps your game directory clean, git-backed save vaults, profile experiments, and graph-based conflict detection — and it installs Wabbajack modlists and Nexus Collections natively, no Windows VM required.
Every platform is a first-class target. Install modde with your system’s package manager, a direct download, or Cargo — and if you happen to use Nix, modde is also a flake, which gives you a reproducible install and the option to declare your mod profiles as code through a home-manager module.
- Project site: https://modde.tartanoglu.com/
- Source: https://codeberg.org/caniko/rs-modde
What modde does
- Virtual filesystem deployment — a symlink farm overlays mods without touching the original game files, with atomic rollback. See Deployment & VFS.
- Wabbajack & Nexus — install
.wabbajackmodlists and Nexus Collections, browse and search Nexus, and resolve downloads from many backends. See Wabbajack modlists and Nexus Mods. - Profiles & experiments — per-game mod sets with a non-destructive, git-like experiment stack. See Profiles.
- Save vaults — git-backed save snapshots with SHA-256 fingerprinting and pre-restore compatibility warnings. See Save management.
- Conflict detection — graph-based collision analysis with severity classification. See Conflicts & load order.
- Tools & executables — MangoHud, vkBasalt, GameMode, ReShade, OptiScaler, and Proton, plus named external executables with overwrite capture. See Tools & overlays and Executables.
Where to start
- New here? Read Installation, then Quick start and the end-to-end Your first profile walkthrough.
- Want to know if your game is supported? See Supported games — modde ships 15 titles across seven engine families, plus user-defined games.
- Curious how it compares to Mod Organizer 2? See the MO2 parity & capability audit.
- Looking for a command or option? See the CLI reference, the Home-Manager module, the settings file, and the Architecture overview.
Status claims in this documentation use a deliberately conservative vocabulary —
Done, Partial, and Not shipped — anchored to the canonical
docs/capability-matrix.toml in the repository. The FAQ answers the
most common questions.