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
[Issue created by Yarn Spinner Bot, migrated from Discord]
Summary: When using the <<stop>> command, the node containing the command will not count as visited when the command is triggered. This leads to confusing behaviours with the assumption that <<stop>> will behave the same as if the node has ended, there are work arounds but this might be an issue. Original thread: 🧵 Issue with <> Command and visited_count in Yarn Spinner
The text was updated successfully, but these errors were encountered:
[Issue created by Yarn Spinner Bot, migrated from Discord]
Summary: When using the
<<stop>>
command, the node containing the command will not count as visited when the command is triggered. This leads to confusing behaviours with the assumption that<<stop>>
will behave the same as if the node has ended, there are work arounds but this might be an issue.Original thread: 🧵 Issue with <> Command and visited_count in Yarn Spinner
The text was updated successfully, but these errors were encountered: