FolioTier 3

goto

Navigate the player to a named Location (pushes the location stack).

Parameters

ParameterKindRequiredDefaultNotes
nameidentifieryes—Identifier of a declared location (from `canonicalProject.subsystems.locations`). Locations come from the importer's post-pass over Ren'Py screen blocks; the Locations + Time rail in the Studio lists declared ids. Silently no-ops at runtime if the id isn't declared (no jumps, no errors).

Canonical example

Folio
goto bedroom
goto kitchen if time.period == "morning"
Ren'Py
screen hallway:
    imagebutton:
        idle "bedroom-door"
        hover "bedroom-door-hover"
        xalign 0.26
        yalign 0.38
        action Jump('bedroom')

goto navigates the player to a named Location. It pushes the current location onto the runtime location stack so return-to-map can pop back.

Notes

  • The target must be a declared location. Locations are declared by the importer over Ren'Py screen blocks, not by author scripts. If the target id doesn't exist in canonicalProject.subsystems.locations, the verb silently no-ops at runtime — no jump fires, no error surfaces. Use the Locations + Time rail to see declared ids, or call get_location_definitions from Aldus.
  • The location stack push is unconditional. If you goto bedroom while already in bedroom, the runtime still pushes — so return-to-map will pop you to the prior location, not stay put.
  • goto: <scene> (with a colon) is the legacy scene-flow verb, not this one. goto bedroom (no colon) is the location verb. The colon form lowers to scene routing; the no-colon form lowers to the Locations subsystem.
  • gotoOnEnter — if the declared location carries a gotoOnEnter slot, the runtime immediately jumps to the named scene after entering the location. Useful for hub locations that auto-run their map screen.

See also