Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: Tunnels can override their return point #199

Closed
joningold opened this issue Oct 10, 2016 · 1 comment
Closed

Feature request: Tunnels can override their return point #199

joningold opened this issue Oct 10, 2016 · 1 comment

Comments

@joningold
Copy link
Member

joningold commented Oct 10, 2016

New syntax:

->-> go_here_instead

The knot-name following the ->-> is an "override" to the return. This causes the game to return from the tunnel, but then immediately divert away to go_here_instead, instead of continuing the flow as normal.

Use case: The following option might appear in several locations of the game:

* [Go to sleep] -> sleeping ->

But sleeping might have the following code:

=== sleeping == 
 { shuffle:
     - You sleep, and then wake. ->->
     - You sleep, but wake to find yourself somewhere new.... 
        ->-> woken_up_in_ 528_AD 
 }

...which allows a sleeping player to be surprise-teleported.

@joethephish
Copy link
Member

Included in 311aef7.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants