I just can't understand how the heck this happens.
I also had to do some debugging to find out what the heck is going on here, but finally the test level "011.level" you have provided in your last post was key to solving the problem!
In fact, this bug always occurred if the following conditions were met:
- a CE with animated graphics (easy to test by just using "use graphic of element" with an element with animated graphics, like the EMC android or firefly etc., for example, which are always animated)
- a CE delay on the CE's change page, but "element changes to"
not checked (that is, no CE change defined)
- any CE action defined, which could even be "no action"
As a result, the in-game animation for this CE is frozen!
The cause for this mis-behavior was indeed tricky to find, as it was a bug deeply hidden in a lot of bad and confusing code. (The whole custom element stuff is a beast that's way to complex and complicated, unfortunately, but I don't dare to clean up that mess.
)
After finding and understanding the problem, the bug was easy to fix, and I am quite optimistic that it should have no negative consequences anywhere else (besides maybe drawing the CE's animation more than once per frame maybe, which should not hurt much).
Thanks again for your test level, which helped a lot to understand and debug the problem! Everything that's already defined that way (including the test level) should instantly work fine again with the bugfix!