The continuation
The upstream architecture was useful. Stopping there was not.
Nexforge began from NexusMods.App after that Linux effort was archived. The goal is not to pretend the inherited code did not matter; its Avalonia surface, MnemonicDB data model, game locator work, and installer foundations are valuable. The engineering job is to carry them into a product that handles the parts the original stopped short of.
Creation Engine support is a real system
Skyrim SE and Fallout 4 are not just names in a game selector. Their plugin files, load order, FOMOD choices, INI files, script-extender expectations, generated content, and external edits all affect whether a modlist remains usable. Nexforge now has substantial coverage across those boundaries: detection, load-order persistence, an in-house FOMOD path, INI tracking, xEdit conflict diagnostics, missing-master checks, and version-aware SKSE64/F4SE diagnostics.
The carried-forward support is broader than the Creation Engine work. Cyberpunk 2077 and Stardew Valley remain supported from the previous repository, while Mount & Blade II: Bannerlord was brought across close to completion and is now supported in Nexforge too. Its launcher and module state, installer and manifest fallbacks, and launch arguments have also received hardening work.
Installation for those games is still an active work area. That distinction matters. A system can have deep diagnostics and safe state handling without claiming that every install path is finished.
Linux is part of the product
Linux support is not a compatibility paragraph at the end of the README. Steam can be native or Flatpak, the game may run through Proton, paths are case-sensitive, and Windows tools such as xEdit or BodySlide may need protontricks. Nexforge keeps those differences in its discovery and launch paths instead of assuming a Windows filesystem and hoping the user never notices.
Safety is in the file operations
Mod management writes to directories that contain saves, runtime-managed content, generated files, and somebody’s carefully assembled loadout. The project has spent real effort on protected-content safeguards, deterministic diffs, backups, rollback and recovery, path handling, and explicit reset boundaries. The useful feature is not a bigger Apply button. It is knowing what Apply will touch and having a way back when reality disagrees.
Diagnostics beat a green icon
Health Check is the product’s explanation layer: external INI drift, plugin conflicts, missing masters, script-extender mismatches, tool prerequisites, and update state should become actionable evidence. That approach is also why the project retains support for existing game providers while building deeper Bethesda-specific behaviour.
Polish is part of long-session correctness
The current v0.5.2 line is not only feature plumbing. It adds density modes, source-aware badges, high-contrast readability presets, reduced-motion controls, progressive rendering hooks, and a low-spec path for large list surfaces. A mod manager is a long-session tool. Legibility and feedback are operational features.