You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally link would have a argument to function as a "returning link", in the way that dialogue would snap back to the current node (and position) when the branch finished.
Instead we should handle every link as a returning link, and add a component that notes the end of the dialogue.
This will allow for easier to use and more advanced dialogue.
The node stack will require to keep track of the current components to make this feasible with recurring / looping nodes.
The text was updated successfully, but these errors were encountered:
Dialogue now creates NodeInstances when moving to a Node,
NodeInstances hold position information and handle updates.
The Dialogue holds a stack of NodeInstances, the dialogue can push, pop or switch at any time.
FixesKeyslam#1, FixesKeyslam#7
Originally link would have a argument to function as a "returning link", in the way that dialogue would snap back to the current node (and position) when the branch finished.
Instead we should handle every link as a returning link, and add a component that notes the end of the dialogue.
This will allow for easier to use and more advanced dialogue.
The node stack will require to keep track of the current components to make this feasible with recurring / looping nodes.
The text was updated successfully, but these errors were encountered: