Ren'Py Introduction - Visual Novel Engine Basics for Game Developers
====================================================================
Ren'Py is the dominant <strong>visual novel (VN) engine</strong> for indie narrative games on <strong>Steam</strong> and <strong>itch.io</strong>. You write story flow in a Python-like script language, ship translated strings from <code>tl/</code> folders, and build <strong>desktop distributions</strong> that fest reviewers install—not just play in the editor.
This chapter orients <strong>developers and producers</strong> who already have a VN project and need <strong>localization discipline</strong> before <strong>October 2026</strong> fest traffic—not a full Ren'Py syntax course.
Why this matters now
Store pages list <strong>Simplified Chinese</strong>, <strong>Japanese</strong>, and <strong>Korean</strong> while the <strong>fest build</strong> still boots in English. Weblate shows <strong>100% translated</strong> PO files; players see English menus because <strong>Ren'Py never wired the selector</strong> or <strong>stale <code>.rpyc</code> cache</strong> hid new <code>tl/</code> strings. Teams that fix this in the editor but skip <strong>standalone exe smoke</strong> repeat the failure on Steam depots.
Who this chapter is for
- Narrative designers importing <strong>Weblate</strong> or <strong>Poedit</strong> exports
- Engineers maintaining <strong>Preferences</strong> screens and <code>Language()</code> actions
- Producers requiring <strong><code>language_receipt_v1.json</code></strong> before promotion
<strong>Time:</strong> ~<strong>10 minutes</strong> to read; <strong>one evening</strong> for the first preflight chapter.
Core concepts (shipping-focused)
| Concept | What it means for fest builds |
|---------|------------------------------|
| <code>tl/<language>/</code> | Translated script + strings on disk |
| <code>translate</code> blocks | In-game text bound to language folders |
| <code>Language("chinese")</code> | Action name must match Ren'Py language id |
| <code>game/cache/</code> | Delete before builds when PO changes |
| Distributions | <strong>Installed exe</strong> is the proof surface—not Launcher preview |
What Ren'Py is (and is not)
Ren'Py <strong>is</strong>:
- A <strong>story engine</strong> with labels, menus, saves, and rollback
- Strong <strong>localization</strong> via folder-per-language workflows
- A path to <strong>Steam</strong> via Ren'Py <strong>Build Distributions</strong>
Ren'Py <strong>is not</strong>:
- Unity <strong>Localization String Tables</strong> (different receipt: <code>string_table_receipt</code>)
- A substitute for <strong>store-page</strong> translation QA (<a href="/resources/18-free-store-page-qa-localization-checklist-resources-indie-launches-2026">store checklist resources</a>)
First steps before localization preflight
- Open <strong>Ren'Py Launcher</strong> → confirm <strong>Translate</strong> lists target languages.
- Note exact language ids (<code>chinese</code> vs <code>zh_CN</code>)—you will map Weblate codes in the next chapter.
- Create <code>release-evidence/localization/</code> in your repo for manifests and receipts.
Where to go next
- <strong><a href="/guides/renpy?chapter=renpy-weblate-po-language-map-and-preferences-screen-preflight-2026-preflight">Weblate PO, language map, and Preferences screen preflight (2026)</a></strong> — L1–L5 gates, <code>language_map_v1.json</code>, clean build, <code>language_receipt_v1.json</code>.
- <strong><a href="/blog/your-first-renpy-language-selector-after-weblate-po-import-one-evening-2026-beginner-pipeline">Evening beginner pipeline (blog)</a></strong> — full block-by-block tutorial.
- <strong><a href="/courses/ai-powered-rpg-game/lessons/202-weblate-export-string-table-smoke-before-fest-player-build-2026-rpg-live-ops">Lesson 202 — Unity string tables (course)</a></strong> — sibling engine, different receipt schema.