boolean - no, this is not a bug. Let me explain the interpretation of the logic that you did by Construct 2. In the same tick, the object was clicked. The first event states the condition "object clicked"(true) and "StateOne"(true), set animation to "StateTwo". So animation is now at "StateTwo" but the processing of the logic in the tick is not over yet. The next event, "Object Clicked"(true because it is still in the same tick and the condition is true in this tick) and "StateTwo"(true because the above event set it so), hence, it also runs. So on and so forth. I hope you understand what you just did.