I just had this simple idea.
It's ver well know, now that when we have a newly created or destroyed object, we need to wait for the next tick to access them.
For instance when we use functions a lot even when the function is called in the created block, the newly created object won't be visible.
My usual work around is to put a wait 0 seconds
But it's not really intuitive. And at some point, nothing insure that this behavior will be kept in future versions (since it's more like a hack). Maybe in the future, the implementation of wait will be changed and wait 0 seconds will trigger instantly... who knows?... and why should we care about internal implementation? (:
So maybe an action dedicated for just that situation, like a "Wait next tick" OR "trigger next tick" action would be better (although "triger next tick" looks more like a condition)
What do you think @Ashley ? (: