not bad I want lego like that too!

it looks like your cat is trying to eat an invisible sandwich at 0.26

All the calculations for the collision event for all instances will take place before the next condition is evaluated.

That's handy information

Thanks guys, I understand it a bit better now

nice find

Hi all

I'm trying to understand how Construct works, and I have a quick question about how Construct handles similar events that occur within the same tick.

Let's say I have two families, Red and Green, and 10 objects in each family.

I have an event set up like this:

-On collision between Red and Green

Action: Set global variable(speedxRED) to Red[physics]VelocityX

Action: Set global variable(speedyRED) to Red[physics]VelocityY

Action: Set global variable(speedxGREEN) to Green[physics]VelocityX

Action: Set global variable(speedyGREEN) to Green[physics]VelocityY

I then use other events to do further calculations with those global variables and apply some actions to the objects that collided.

My question is, if the situation occurs that two independent collisions happen within the same tick, will Construct treat each collision separately, and first store the values in the global variables for one of the collisions, then overwrite them with the values from the other collision? Or will it just be a big mess?

Also, if they are treated separately, will Construct go trough the entire chain of events involving the global variables for one of the collisions, and then do the same with the other collision? Or is there a risk that the other collision will mess up any ongoing calculations that is happening with the first collision?