Manual:
[quote:2ghr2vne]On timer
Triggers either regularly, or once off, after a timer that was started with the same tag has reached its duration. NOTE: this trigger can fire with multiple instances picked, if their timers all reach their time in the same tick. This can sometimes work unexpectedly if the actions expect there to be just one instance picked. The workaround is to add a For each condition after this trigger to ensure the actions run once per instance.
It might be because of late hour here, but in this case, then there's has to be another condition that will lock out those that are not meeting the timer condition, right?
Let's say you want to destroy object on timer. Number of them triggers simultaneously. What would you do to avoid destroying all objects (because of For each condition)? And now I know what was causing those random issues in my projects. And I wasn't expect this to be it, since it is counter intuitive.
Ashley Hope that it is going to be fixed in c3, with stacking up objects.