@jayderyu - that's a bug in Spriter, and you're just working around it with 'wait 0'. You shouldn't have to do that. If Spriter is not ready internally for some action to work yet, it should just queue up the action and run it when it's ready. For example the Pathfinding behavior does this. Internally it's not ready to accept any 'find path' actions in the first tick. But if you do use something like 'On start of layout - find path', it queues up the action and runs it on the second tick, so everything works like you expect. Spriter should to the same.