Same thing Zebbi (in my eyes), i see always the Two Same Things.
1/ A lot of poeple doe things like this, for example. In the first event they check if something moves right an some other condition. If true they set it to move left. In de next event they check if it moves left (forgetting that in the previous event they made it move left)
So, they make two events in a row, and the first event makes the second always true.
2/ At the same time (especialy in OR blocks) they pick some objects. In de next (same level or sub level event) they filter those picked items in a way that the condition is true, but there are no objects left in the picklist to feed the actions.
It is usaly not a case of construct having a flawed event system. It is usaly not carefully coded. In a lot of cases you are better of with two seperatly events then with an or block. The or is mostly lazy coding, because you dont have to duplicate the actions. Althaught, less event should be encouraged, i know.
So, in my opinion, allowing ANDs in an OR block will get even more poeple confused, when they seem to be confused allready. But i am guilty too, i still fall in those traps. I dont need more traps.