Hello. I noticed this strange behavior. I can't find any flaw in my eventing, it's propably an error in Construct... I included explanation in comment in .cap, but I summarize:
There is three events, one which creates the object, one which modifies the position and angle and one which modifies them back to the original position. On that tick an object is created, only ONE of these modifying events performs, although both should.
I'm sorry to bump this but... well, maybe I should just post this to bug tracker and stop whining in this thread
I have actually investigated this - created objects don't become fully "real" until the next event tick - with the exceptions of loops like Repeat, which make sure created objects are up-to-date. It's a bit of a weird way to handle things, so I'll try making it more sensible for the next build.
Develop games in your browser. Powerful, performant & highly capable.
This is fixed in the next build - it works the same both ways now! (It stays on top of the red object)