Ren'Py Release Gate

It reads your .rpy files and reports the lines that pass Ren'Py's compile step but fail later: a bare square bracket that Ren'Py reads as a variable, a text tag opened and never closed, define used where default belongs, a persistent value with no default, tab indentation, and shipped developer settings. Fourteen rules, each with the fix.

Solo and small-team Ren'Py developers shipping visual novels to Steam, itch.io and Android. It is aimed at the moment before you press build: the point where your own save file hides bugs that a first-time player will hit on line one of chapter three.

A chatbot only sees the snippet you paste. It cannot tell you that persistent.seen_ending_a is read in script.rpy and defaulted in none of your other files, or that config.save_directory is missing from the project. Those two findings need every file at once, and they are the two that lose player saves.

Free: open a .rpy file, run the check, get every finding in that file with line numbers and fixes. That is a finished job for a single file, forever, with no key. The licence adds the other axis: one sweep across every .rpy file in the workspace and an exported release report you keep.

Putting one title on Steam costs $100 in Steam Direct fees before you see a crash report. After launch, each fix is a rebuild, a store update and the players who already refunded. The licence is $29 once, one key per person or CI seat, with a seven-day full refund.