Guide Details Save Preparation and Transfer for Seedsow Lua Editor

A community-focused preparation and installation guide outlines the workflow for setting up and transferring the Seedsow Lua Editor save data between a hacked Nintendo Switch 1 and a stock Nintendo Switch 2. The process utilizes a modded Switch 1 for initial save restoration via the JKSV homebrew tool, followed by standard Nintendo save-transfer features to move the data to the second console.

Core System Requirements

• Consoles: A hacked Nintendo Switch 1 capable of running homebrew and a stock Nintendo Switch 2.
• Firmware: Targets firmware version 23.0.1 on both consoles, which represents the current checkpoint referenced in the guide.
• Accounts: A matching Nintendo Account linked to the designated save user on both devices.
• Software: The same edition of Seedsow Lullaby installed on both systems, with reference testing performed using the 1.0.0 US eShop demo.

Preparation and Installation Steps

1. Initial Save Generation: On Switch 1 in stock mode, launch the software, create a new game, make an in-game save, and close the application.
2. Homebrew Tool Setup: Transfer the JKSV save manager to the Switch 1 microSD card and boot into custom firmware (CFW) on sysNAND to run it.
3. Backup Creation: Use JKSV to create an initial backup of the existing save data as a safety precaution.
4. Save Substitution: Place the pre-built `Seedsow-Lua-Editor-Save.zip` file into the appropriate JKSV backup folder alongside the original backup, then use JKSV to restore the editor save.

Transfer Methods

• Nearby Local Transfer: Recommended for demo editions, utilizing system settings to beam the save directly from Switch 1 to Switch 2 while connected to Nintendo servers.
• Cloud Save Transfer: Requires an active Nintendo Switch Online membership and the full game edition on both consoles to upload and download the save data via Nintendo's cloud servers.

Users should verify all firmware requirements and official instructions directly with Nintendo. The guide emphasizes keeping original backups intact and notes that custom firmware usage carries inherent platform risks.