I'm seeing some weird behavior with 276.2. The following code works as expected, and in the debugger I can see Player's animation being set to "collapse" in either scenario.
However, if I combine the conditions into an OR block, like this...
...this is what happens:
- the "set animation to collapse" action executes when either of the conditions is met (expected)
- Player's animation changes to "collapse" ONLY when the hitCount>= player.hitMax condition is true. In other words, if lifeBar (a Progress Bar) has progress <= 0, the "set animation to collapse" action is still called per the debugger, but the player animation doesn't change.
I've had the OR block (2nd pic) in my code for many months now, and only recently started seeing an issue with it. I split it into the code shown in the 1st pic and now it works. Is there something about OR blocks or Progress Bar objects that I'm not considering?