Skip to content

1.2.0 MO2 repair

Choose a tag to compare

View all tags
@bobbycomet bobbycomet released this 12 Sep 15:36
· 20 commits to main since this release
v1.2.0
78576a1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Added

Repair MO2 (staged recovery, mod safe, save safe, tested on Skyrim SE/AE, backup is option for safety)

New capability to repair MO2 application files on an existing managed instance while optionally preserving instance (user) data. This does not create a new Steam shortcut, AppID, or Wine/Proton prefix — repair always targets the same install path and the same compatdata/<id>/pfx.

The feature is modeled as recovery of two separate state classes:

Application state (replaced) Instance state (optional backup / restore)
MO2 binaries, shipped plugins, runtime, helpers, USVFS mods/, downloads/, profiles/, stylesheets/, overwrite/, ModOrganizer.ini

Safety workflow

Backup → Confirm → Repair → Test → Restore
  • Backup and Restore are explicit, user-triggered steps — never silent.
  • Repair does not automatically restore instance data after reinstall.
  • Users are expected to launch MO2 from Steam and verify the original problem is gone before restoring.
  • Automated backup/restore is optional; fully manual backup/restore is supported.

Backup location rules

  • Backups must live outside the MO2 install folder (enforced).
  • Default suggestion: same drive, sibling folder, e.g.
    …/Games/MO2 → …/Games/MO2_backups/MO2_<timestamp>/
  • User may browse to any other path.

GUI

  • Settings → managed prefix → “Repair MO2” opens a dedicated staged dialog.
  • Stages: backup, confirmation checkbox, repair, test guidance, restore.
  • Per-folder selection (mods, downloads, profiles, stylesheets, overwrite, ini).
  • downloads/ and overwrite/ are optional (off by default in the UI).
  • “Skip backup — repair application only” for users handling data themselves.
  • Optional “remove backed-up folders after repair” so a clean MO2 can be tested before restore.
  • Manual backup checklist available in the dialog.

CLI (kalium fix-mo2)

New staged subcommand (see wiki for full usage):

  • backup — copy selected instance data out and verify
  • repair — replace application files only
  • restore — copy instance data back from a backup folder
  • checklist — print the manual backup checklist

New module

  • kalium/installers/fix_mo2.py — backup, application repair, restore, path helpers, checklist text.

Changed

  • Settings managed-prefix actions include Repair MO2 alongside USVFS, VFS memory, LOOT, and vcrun2022.
  • Repair-related messaging emphasizes same prefix / same path and that some mods may not survive a filesystem copy (re-download may be required).
  • Large-list timing is called out (HDD / overhaul packs can take an hour or longer).

Notes / caveats

  • overwrite/ may contain SKSE output, shader caches, and other generated VFS content — not only loose mod files.
  • Backup verification compares size/fingerprint; restore treats fingerprint mismatches as warnings (partial copies / picky mods) rather than always hard-failing the whole restore.
  • After application repair, Kalium still re-applies USVFS 0.5.7.2, theme, VFS max_memory, and custom-executable path normalization when those helpers succeed.

Files of interest

Path Role
kalium/installers/fix_mo2.py Core backup / repair / restore
kalium/main.py fix-mo2 CLI
kalium/ui/main_window.py Repair MO2 dialog + Settings button
'''
Assets 5
Loading