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
It's possible for the hero to trigger other touch/collision events while it's being moved by a list of event commands. In fact, the hero can trigger multiple events, but they won't start until the list has been completed. If more than one events have been triggered, they'll run in ascending order of IDs. This means it doesn't matter in which order these events are triggered by the hero. It looks like in this context, the touch/collision triggers are checked right after the hero's move route has been finished.
It's possible for the hero to trigger other touch/collision events while it's being moved by a list of event commands. In fact, the hero can trigger multiple events, but they won't start until the list has been completed. If more than one events have been triggered, they'll run in ascending order of IDs. This means it doesn't matter in which order these events are triggered by the hero. It looks like in this context, the touch/collision triggers are checked right after the hero's move route has been finished.
That might have been a bit confusing, so here's an example.
https://dl.dropboxusercontent.com/u/30277047/PendingCommands.zip
The text was updated successfully, but these errors were encountered: