rpynx v0.1.0pre-release

Playing

Saves, HOME and sleep

Where saves go, what survives an update or a delete, and what happens on HOME, sleep and quit.

HW verifiedruns 23, 24, 26Source runtime/renpy/README.md, docs/IMPORTER.md, tests/hardware/results/2026-10-21-run26.md
On this page

Saves

Each game saves to its own folder:

text
sdmc:/switch/renpy-loader/saves/<id>/

Ren’Py writes every save to all of its save locations, so a copy also goes to games/<id>/game/saves/. In run 26, a save in slot 1 at script.rpy:72 loaded back to the same line after quitting and starting the game again.

What happens to saves:

You…Saves
Update a game with --replace or an FTP uploadKept: game/saves/ is moved into the new copy, and saves/<id>/ is never touched
Delete a game in the importersaves/<id>/ is kept unless you tick Also delete its saves
Rename a game’s folderThe game gets a new id, so it no longer sees its old saves folder

warning

Saves from a Ren’Py 7 game do not load after it is recompiled for Ren’Py 8.

HOME button

Press HOME mid-game and come back: the game goes on. Buttons held while you were away are ignored until released, so skip or rollback cannot get stuck. In run 26 the game was away for 54 s and went on.

Sleep

Sleep the console and wake it: the game resumes. Runs 23 and 24 logged sleeps of 29 s and 112 s, and quitting and starting another game afterwards worked.

Quitting

Quit from the game’s own menu. The runtime waits up to a second for the game’s threads, shuts Python down, and returns to the library. Starting another game afterwards works (run 24); three games in a row ran in one session (run 12).

If the game stopped with an error, you see the system error dialog first. See Errors and crash reports.

note

Docked mode and controller reconnects are implemented and tested on the host, but have no hardware result yet.

↑↓ move↵ openesc close