Nintendo Switch 2 · Save backup tools

ns2-savekit backup, verification and save tools for the documented patched RPC environment.

ns2-savekit

ns2-savekit original project identity

Back up, verify, restore and modify title saves through ns2jb. Includes separate Artemis Lua save-launch tools.

Requirements: Patched ns2jb RPC engine, live session and run folder/current-root.json, Node.js, firmware 23.0.1 and retail SmileBASIC 4.

Setup: Apply the documented engine patches before starting a fresh RPC session. Open tools/kit.cjs with the run folder. Begin with read-only listing and backup, then verify by hash. Keep originals before restore/replace/delete operations. No npm install or compilation is required by the author; this project does not include the exploit, keys or games.

Pinned complete script/source ZIP with tools, patches, configuration and upstream documentation. Requires the separate RPC download.

ns2-savekit scripts ZIP · version 3b4446fb8ef044c46052a53a5836c3071891e7f3 · SHA-2568b2a2f8a2404fdcc59d21a7c99c897362e0596d0e7e6c6c125cd15482744b8dfUpstream package source

ns2-savekit setup guide

  1. Extract both downloads separately

    Keep Savekit and the RPC fork in separate folders. Retain every engine, tools, patches and config directory; do not run kit.cjs alone.

  2. Prepare the required engine patches

    The upstream patch command expects a Git working tree. For an extracted RPC ZIP, run git init inside that RPC folder first. From Savekit, follow sh patches/apply.sh /absolute/path/to/ns2jb-rpc. If any patch fails, stop and resolve the revision mismatch before starting a session.

  3. Start a fresh RPC session

    Use the RPC setup above, with node run.cjs --rpc <computer-LAN-IP>, and keep it running. A run folder from before patching retains the old engine and must not be reused.

  4. Open the kit

    From the extracted Savekit folder run node tools/kit.cjs /absolute/path/to/ns2jb-rpc/runs/switch2-RUNID. Begin with listing, then backup, then verification. Keep original backups outside the tool folder.

  5. Restore deliberately

    Follow the bundled docs/RESTORE.md and write allowlist requirements. Restore/replace/delete alter saves. The Artemis launcher is separate from general save backup and has its own documented limits.

Packages are pinned script/source snapshots, not upstream binary releases. GitLab snapshots are reconstructed from unchanged, Git-hash-verified files when upstream ZIP downloads are unavailable. Required runtimes are listed above; no console execution was performed here.