tunnels #30

New Issue

NQN · 2019-01-11T19:48:02Z

NQNStudios commented

2019-01-11 19:48:02 +00:00

(Migrated from github.com)

https://github.com/inkle/ink/blob/master/Documentation/WritingWithInk.md#1-tunnels

There must be an easier way to implement this using hscript variables like how I ported TheIntercept's variable referencing functionality

https://github.com/inkle/ink/blob/master/Documentation/WritingWithInk.md#1-tunnels There must be an easier way to implement this using hscript variables like how I ported TheIntercept's variable referencing functionality

NQNStudios commented

2019-01-25 17:00:37 +00:00

(Migrated from github.com)

Possible solution: Tokenize divert targets and store a queue of them. Then tunneled sections can use -> DONE which would become equivalent to requesting 'divert to the next target on the queue.'

NQNStudios commented

2019-06-04 04:08:25 +00:00

(Migrated from github.com)

Maybe these and threads (#38) could be wrapped into one feature implemented as an insertion hook (#55). If a divert target is meant to be inserted like {target}, the Story could spawn an embedded story that starts at that target and continues until it returns Finished. I'd want to test multiply nested stories at that point...

Maybe these and threads (#38) could be wrapped into one feature implemented as an insertion hook (#55). If a divert target is meant to be inserted like `{target}`, the Story could spawn an embedded story that starts at that target and continues until it returns `Finished`. I'd want to test multiply nested stories at that point...

NQNStudios commented

2019-06-04 18:06:06 +00:00

(Migrated from github.com)

The syntax I just described is ambiguous with what already happens when you insert a divert target: view count insertion.

NQN referenced this issue

2025-10-31 18:48:22 +00:00

Roadmap #63

Sign in to join this conversation.