What was fixed and why
Backpatch is available again. It had been held back because downpatching alone was not enough after Bethesda’s 1.7.x update.
In 1.7.x, the format of ContentCatalog.txt changed. That file lives outside the game install (typically under Local AppData / the Proton prefix). The new format is incompatible with any version below 1.7.x (including 1.6.1170 and other 1.6.x targets): the older binary crashes on load when it reads the updated catalog.
What 1.2.1 does: on Apply (and auto/console apply), Kalium renames
ContentCatalog.txt → ContentCatalog.txt.bak.
- The
.bakkeeps the original file so nothing is deleted. - The live catalog is no longer read by the downpatched game, so the backpatch can complete and run successfully.
UI: ContentCatalog.txt field with Browse and Auto-detect (Proton prefixes, Local AppData, MO2 compatdata).
CLI/API: content_catalog= / require_content_catalog= on run_backpatch, plus disable_content_catalog() and find_content_catalog().
Without this rename, depot apply alone does not fix the crash. With it, backpatch to 1.6.x (and other pre-1.7 targets) works.