Learning resources and communities

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

• Start with official docs when syntax matters.
• Use community tutorials for workflow examples.
• Keep asset licensing visible before release.

Core syntax

• official docs
• Lemma Soft
• itch.io
• asset licenses
• learning path

Runnable example

This chapter is mainly conceptual. Use the checklist below while testing in a small Ren'Py project.

Study outline

• Start with the smallest example for learning resources and communities.
• Test the key terms in a clean Ren'Py project: official docs, Lemma Soft, itch.io, asset licenses.
• 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/

How this fits in GenPy

• Use GenPy docs as the workflow layer and official Ren'Py docs as syntax authority.
• Use Publish docs to keep licenses and release materials organized.

Recommended GenPy docs:

• Platform Overview
• Publish
• Export and download