Merge main into the 0.9.1 release: the launcher's Mods screen, the anti-aliasing choices beside FSR and DLSS, and the scene's last row and column filled before an upscaler reads it.

The 0.9.1 notes keep the release branch's text and take main's sections: New, the edge line under Fixed, and Changed.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
chrg6
2026-11-12 09:00:37 -05:00
24 changed files with 1388 additions and 151 deletions

View File

@@ -88,7 +88,9 @@ identity (`NX2navi.Launcher`), so the taskbar groups and pins it under NX2navi r
Screens (`launcher/ui/app.py`): first run (dump, install folder, Desktop Shortcut, Check for Updates at Start,
Update Channel, Begin Installation); the steps of an install, update or rebuild with their progress, the build log's
last lines and Cancel, and after a failure Try Again and Copy Report; home (Play, Updates, Game Folder, Saves,
Rebuild the Game, Customize Launcher, Settings); customize (Color Scheme, with Custom Background Color, Panel Color and
Mods, Rebuild the Game, Customize Launcher, Settings); mods (Open Mods Folder, Add a Mod, Add a Mod Folder, one On/Off
row for each mod, More Mods when they fill more than a page, Load Order, Back); load order (each mod with its place,
left and right to move it); customize (Color Scheme, with Custom Background Color, Panel Color and
Button Color, Background, with a picture set Background Dimming and Remove Background, Animations, Sounds, Add to Steam on
Windows, Back); the colour picker (Hue, Saturation, Brightness, Hex Code, Reset, Done); saves (Export Save, Add Log and Settings, Export To, Import a Save, Import a Save Folder,
Open Saves Folder, Back); settings (update check, Install Updates Automatically, Hide Launcher While Playing, Keep
@@ -344,6 +346,38 @@ copies the current save to `saves/backup <date time>` and makes the import the s
(`runtime/fs_host.c` `import_pending`), and the menu says where the old save went. An import in the launcher replaces
one still waiting from the menu.
## Mods
Mods (home, under Saves; `launcher/mods.py`) is where the player puts the mods they download. The game reads the game
folder's `mods` folder (`runtime/mods.c`; `mods_dir` in nx2navi.ini names another): one folder per mod, holding a
`romfs` folder with the game files it replaces, an `exefs` folder with code patches (`.ips`, `.pchtxt`) or a `cheats`
folder, either at its top or in the Atmosphere layout (`atmosphere/contents/0400486024DEC000/romfs` and the others
`tools/mod_files.py` lists).
A mod goes in as it came. Play first puts the folder in order (`mods.prepare`): an archive (`.zip`, and `.7z` or
`.rar` through Windows' own `tar`, which reads them on Windows 10 and 11) is unpacked into a folder of its name unless
that folder is there already, and the archive stays; a mod folder whose files sit one or more folders down (an archive
that held the mod's own folder) gets them moved up; a `romfs`, `romfslite`, `exefs` or `cheats` folder put straight into
the mods folder becomes a mod of its own, *Unnamed mod*. An archive that would write outside its folder is refused.
Nothing is deleted. Add a Mod and Add a Mod Folder do the same for an archive or folder the player picks, which is
unpacked or copied into the mods folder under a free name; Open Mods Folder opens it.
Each mod has an On/Off row; its description says what it changes (how many game files, code patches, cheats), which
other mod changes the same files and which of the two wins, and why the game leaves it off when it does: a code module
(`subsdk*`), a download with options to pick from (several folders that each hold a mod), a mod for another game or
another version, or nothing the game reads. Load Order sets which mod wins a file two of them change: the higher one.
The switches and the order are the game's own settings, `mods_disabled` and `mods_order` in nx2navi.ini, written as the
game writes them; they apply at the game's next start, so they wait while it runs.
**Mods that change the game's code.** The game is lifted from the console's code ahead of time, so code cheats and
ExeFS patches cannot be applied while it runs: the build turns them into patch sets of the lifted code
(`tools/cheats.py`, `tools/exefs_patches.py`) that the game switches on with their mod, and the Cheats tab of the
game's menu switches each cheat. The lift step's key names those files, so a build lifts and compiles again when they
change (only the changed parts compile, and the shaders stay prepared), and `build-cache/mod-code.json` records the
files it took up. When an enabled mod brings code no build has seen, Play builds the game again first (a few minutes;
the home's Mods row says "Build Waiting") and starts it after. A Play from Steam then opens the window for that build.
Code mods are built from the game folder's own `mods` folder only.
## Importing a save folder
Import a Save Folder (Saves) makes another save the game's own. A save put into the game folder's `saves` folder (its