Advanced GUI customization

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

• Understand when advanced GUI code is worth the maintenance cost.
• Keep custom displayables isolated and testable.
• Prefer built-in screen language before adding custom runtime behavior.

Core syntax

• Displayable
• renpy.register_statement
• custom text tags
• callbacks
• CDD

Runnable example

init python:
    def buy(item):
        store.money -= item["price"]
        store.inventory.append(item["name"])

screen shop():
    vbox:
        for it in shop_items:
            textbutton "[it[name]] - [it[price]]金" action Function(buy, it)

Study outline

• Start with the smallest example for advanced gui customization.
• Test the key terms in a clean Ren'Py project: Displayable, renpy.register_statement, custom text tags, callbacks.
• 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/screen_python.html
• Ren'Py official reference: https://www.renpy.org/doc/html/cdd.html
• Ren'Py official reference: https://www.renpy.org/doc/html/cds.html
• Ren'Py text reference: https://www.renpy.org/doc/html/custom_text_tags.html
• Ren'Py official reference: https://www.renpy.org/doc/html/character_callbacks.html

How this fits in GenPy

• Use Screen Editor and GUI Theme docs for common cases first.
• Use Code mode for advanced runtime code and verify in Ren'Py.

Recommended GenPy docs:

• Screen Editor
• GUI Theme
• Code editor