Practical features

This page is part of the GenPy Ren'Py learning path. It focuses on practical Ren'Py 8.x production and links each concept back to the GenPy workflow.

Learning goals

• Recognize common production features beyond simple dialogue.
• Pick the right feature instead of reinventing it.
• Keep feature code connected to project structure.

Core syntax

• NVL
• side image
• input
• achievement
• gallery

Runnable example

define nn = Character("旁白", kind=nvl)
define n_e = Character("艾琳", kind=nvl)

label start:
    nn "夜色渐深。"
    n_e "你还醒着吗？"
    nn "屋里一片寂静。"
    nvl clear              # 清屏，开始新一页

Study outline

• Start with the smallest example for practical features.
• Test the key terms in a clean Ren'Py project: NVL, side image, input, achievement.
• Move the pattern back into your real project only after the example runs.
• Use GenPy docs and validation to keep the feature connected to story, assets, and export readiness.

Common pitfalls

• Test the smallest working script before layering on visual or UI complexity.
• Run Ren'Py Lint before release builds, even when the script appears to run locally.
• Keep examples in standard .rpy files so they remain editable outside GenPy.

Official references

• Ren'Py official reference: https://www.renpy.org/doc/html/nvl_mode.html
• Ren'Py official reference: https://www.renpy.org/doc/html/side_image.html
• Ren'Py official reference: https://www.renpy.org/doc/html/bubble.html
• Ren'Py official reference: https://www.renpy.org/doc/html/rooms.html
• Ren'Py official reference: https://www.renpy.org/doc/html/drag_drop.html
• Ren'Py official reference: https://www.renpy.org/doc/html/sprites.html

How this fits in GenPy

• Use GenPy plugins and templates when a feature should become reusable project structure.
• Use Validation before publishing feature-heavy projects.

Recommended GenPy docs:

• Plugins
• Templates
• Script Validation