Build and publish
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
- Run lint before release builds.
- Understand platform-specific packaging expectations.
- Keep export artifacts and source projects separated.
Core syntax
Build DistributionsLintWindowsmacOSLinuxAndroidWeb
Runnable example
text
define config.name = _("我的视觉小说")
define config.version = "1.0.0"
define build.name = "MyVisualNovel" # 文件名/目录名（用 ASCII）
define build.directory_name = "MyVN-1.0.0"
# 应用标识（务必唯一，影响存档目录、商店上架）
define build.itch_project = "yourname/my-vn"Study outline
- Start with the smallest example for build and publish.
- Test the key terms in a clean Ren'Py project: Build Distributions, Lint, Windows, macOS.
- 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/build.html
- Ren'Py official reference: https://www.renpy.org/doc/html/android.html
- Ren'Py official reference: https://www.renpy.org/doc/html/ios.html
- Ren'Py official reference: https://www.renpy.org/doc/html/web.html
How this fits in GenPy
- Use GenPy Export and Publish docs to prepare project files, then use Ren'Py's launcher for final distribution builds.
- Use Desktop workflows when local files and runtime preview matter.
Recommended GenPy docs: