Managing Save Data and Script Execution via ns2jb Sessions

Overview

An open-source repository titled `ns2-savekit` provides toolsets to read, back up, restore, and modify save data across various titles over a live `ns2jb` session. The documentation specifies that the utility is not an exploit itself; it requires a patched local `ns2jb` checkout, a running exploit session, and specific firmware environments like firmware 23.0.1 alongside retail SmileBASIC 4.

Core Save Operations and Safeguards

According to the repository documentation, save management works by opening an archive, moving files, committing changes, and verifying results via hashes. Safety measures include:

• Read-only by default: Writing requires a prior backup and a byte-by-byte comparison against live data.
• Allowlist restrictions: Only titles specified in configuration lists (such as Elden Ring) can be modified.
• Verification checks: Large save files are processed in 256 KiB reads to ensure integrity.

Launchers and External Integrations

The toolkit facilitates installing external launchers from pinned releases, such as a Lua launcher for the Switch 1 edition of Balatro running on newer hardware in compatibility mode. It also supports Artemis-based environments (tested on specific demo titles like the Seedsow demo and Nora 2 demo) which configure script execution paths through save containers or suspend files.

Verification and Limitations

Users must verify all procedures against the official repository documentation (`docs/` directory). The developer notes certain components remain in a staging or smoke-tested phase rather than fully installed on all hardware configurations. Third-party components such as upstream repositories and dependencies are acknowledged under the project's notice file.