Skip to main content
Industry & SpecializedGame Production32 lines

Ren'Py Visual Novel Development

Implement branching routes, stable save state and release checks for a visual novel using Ren'Py labels, menus and distribution builds.

Quick Summary9 lines
Begin with a route graph that lists choices, prerequisites, state changes and endings. Give each stable scene a descriptive label and each important state a clear owner. Mark places where routes reconverge, and note which earlier decisions must survive that merge. Start with one complete route and one optional branch before expanding the project.

## Key Points

- [Ren'Py in-game menus](https://www.renpy.org/doc/html/menus.html)
- [Ren'Py persistent data](https://www.renpy.org/doc/html/persistent.html)
- [Ren'Py distribution build documentation](https://www.renpy.org/doc/html/build.html)
skilldb get game-production-skills/renpy-visual-novel-developmentFull skill: 32 lines
Paste into your CLAUDE.md or agent config

Ren'Py Visual Novel Development

Begin with a route graph that lists choices, prerequisites, state changes and endings. Give each stable scene a descriptive label and each important state a clear owner. Mark places where routes reconverge, and note which earlier decisions must survive that merge. Start with one complete route and one optional branch before expanding the project.

Implement branches and state

Use label for route entry points and menu for visible choices. Use conditions only where the player can understand why a choice is absent or disabled. Keep dialogue and choice text separate from state changes where practical. Apply each consequential choice once, then jump to a label that reflects the next scene.

Declare playthrough variables with default. Use persistent data for information intentionally shared across runs, such as a gallery unlock. Verify that restarting a route resets its state while retaining only explicitly persistent information. Avoid naming transient state and persistent state alike. If an old release exists, test a save from that release before moving or renaming labels. Keep supported old route data readable and initialize new fields explicitly.

Organize assets and build one vertical slice

Assign stable paths to backgrounds, sprites, audio and fonts. Record source rights, localization scope and fallback expectations. Exercise a representative background, expression change and music transition in the pilot. Run the Launcher’s lint check and investigate missing assets, undefined statements and unresolved image references. Walk through the same slice using keyboard navigation and the largest supported text setting.

For a concrete two-route test, place a locked archive at the first branch. Carry a key through the archive and through the common ending. Verify the route without the key cannot enter. Save before the choice, load and take both branches. Roll back once and confirm state reflects the chosen branch. Start a new game and verify a key collected in an earlier playthrough remains absent.

Verify a distribution build

Run the documented distribution workflow for the pinned engine version. Build on a clean copy with the intended build configuration. Open the resulting package in a representative environment rather than relying on Launcher execution alone. Check startup, menus, one full route, save and load, fonts and audio, and the intended installation and storage paths. Record build identity and test results. Deliver the editable project and verified packages, and keep publication separate from package creation.

Sources

Install this skill directly: skilldb add game-production-skills

Get CLI access →