end

Parameters

This construct takes no arguments.

Canonical example

narrate "And that was the last she ever saw of him."
end

"And that was the last she ever saw of him."
return

end terminates the playthrough — the player sees the credits / end screen / next-episode CTA depending on the project's configuration. Reaching end from inside a called scene still terminates: the call stack is discarded.

Notes

Folio splits the responsibility Ren'Py overloads onto return. In Ren'Py, return at the top level of start ends the game; inside a called label it pops the stack. Folio names the two cases separately — end for "the playthrough is over", return for "the called scene is finished, resume the caller". The disambiguation makes the author's intent visible in the node editor (an end node has no outgoing edges; a return node draws an edge back to its callers).

The importer translates Ren'Py's terminating return to end when it's at the top level of start (or any label that's only ever entered as the entry point), and to return when it's inside a called label. This relies on call-graph analysis the importer runs during the deterministic pass.

A project can have multiple end lines — one per ending. The "which ending did the player reach?" record is part of the save state, used by the gallery and replay surfaces.

See also

• return — return from a called scene without ending the playthrough
• scene-flow — full routing vocabulary