Overseer

A Fallout 4 mod manager, written in Rust.

Under active development

The Mod Organizer 2 model, done right

Overseer follows the Mod Organizer 2 model of explicit, non-destructive mod and load-order management, and builds in the pieces MO2 leaves to third-party plugins: root-folder deployment (script extenders, ReShade, ENB), in-app plugin grouping, native tool integration, and setup diagnostics. One UI-agnostic Rust core drives every front end.

What’s inside

Crash-safe deployment

Non-destructive hardlink deploy, journaled as a transaction. Overwritten files are backed up and restored on purge; an interrupted run rolls back cleanly.

Real load order

Writes the actual Plugins.txt through libloadorder on deploy, and restores it on purge, so the game and tools see exactly what you set.

Root-folder deploy

F4SE, ENB and ReShade files that live beside the executable are handled first-class, not just what lands in Data/.

Plugin grouping

Organise your load order into named groups inside the app, with no external plugin needed to keep a large setup readable.

Setup diagnostics

overseer doctor runs read-only health checks on your install and surfaces the same results in the terminal UI.

TUI-first, scriptable CLI

A ratatui terminal UI for daily driving, plus a one-shot CLI for automation, both over the same core.

Quick start

Launch the terminal UI:

cargo run -p overseer-tui

Or drive a full Fallout 4 workflow from the CLI:

# create an instance pointing at your game
overseer instance init --path <instance-dir> --game-dir "<FO4 install>"

# install a mod, then inspect the mod list and plugin order
overseer install <mod.7z> --instance <instance-dir>
overseer mod list    --instance <instance-dir>
overseer plugin list --instance <instance-dir>

# deploy into Data/ (writes the real Plugins.txt), then undo
overseer deploy --instance <instance-dir>
overseer purge  --instance <instance-dir>