ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #renpy
A practical breakdown of Ren'Py's store vs persistent data, when to use checkpoint() and block_rollback(), and how to verify rollback behavior in your own project.
Ren'Py's layeredimage statement composites character sprites from separate art layers at runtime, cutting asset count and enabling dynamic variations. Covers block syntax, auto-discovery, conditional attributes, and verification.
Build a custom save screen in Ren'Py that displays thumbnails, lets players load or delete slots, and keeps the UI inside your game using built-in functions.
When Ren'Py language selectors fail to switch dialogue text, proper translate block configuration and UTF-8 catalog encoding are the fix. This guide covers the procedure and verification steps.
When adding story flags mid‑development, choose <code>default</code> over <code>define</code> to maintain save compatibility. Here’s how to verify your variable strategy works correctly.
Separate UI from game logic with Ren'Py’s screen language. This guide walks through defining screens, calling them from script, passing data, handling callbacks, and highlights trade‑offs and a quick checklist.
Learn how to build reusable, declarative UI components in Ren'Py using Screen Language, focusing on minimal design patterns, security boundaries, and failure mode mitigation.
Learn how to use Ren'Py's Animation and Transformation Language (ATL) to replace static sprite movements with organic, eased animations and how to profile them for performance.
Learn how Ren'Py's rollback system uses full-state snapshots to enable deterministic rewinding of narrative progress and how to handle custom Python state.