It is Mouse.X - posX and Mouse.Y - posY. TextBox cant have a negative size.

But i dont see a simple way to reset the Boolean in that flow.

'On Button CLICKED' will steal a 'On Mouse button released'.

https://www.dropbox.com/s/k6znwheid5n7z ... .capx?dl=0

Give both objects an instance boolean 'GetTheHellOut', starting state = false

When ENTER pressed and Hi true:

* Play a sound

* Disable the 2nd object's sine behavior

* Set boolean 'GetTheHellOut' to true for both objects

Is boolean 'GetTheHellOut' true (for that object)

* Simulate object pressing down

Is boolean 'GetTheHellOut' true (for that other object)

* Simulate object pressing down

Need some method now to destroy or stop them moving.

You can also use 1 Global variable instead of an instance boolean. Same method.

The bullet behaviour is not set to bounce of solids, hence it runs trough them.

Well. The mistake is that you see it as a 'logical mistake'. It is not. And is way more simple then that.

Lets read your event 12 as example. It states this.

On the moment that there is a collision happening between any Family member (containing the bubbles) and any instance of Bubble, trigger this condition, and make a picklist containing that Family member and that instance of Bubbles.

Keep in mind that, if you trigger a a collision check between X and Y, the mechanism that picks X will not include Y, and the mechanism that picks Y will not include X. Since you check between instances of the same object, the mechanism that picks X, starts with something holding X & Y (both collide, and they are instances of the same object). It is holding them in order of creation. So X is the one created before Y. Then it excludes Y, being the last one in that order. Or, X will always be the first created instance (when you trigger a collision check between instances of the same object)

So, in your case. Family will always be the first created instance in the list of colliding instances, that means that Bubble will always be the one that is shooting. (it is created last).

So the picklist made in that 'on collision' condition contains 1 Family member and 1 instance of Bubble and Bubble is always the shooting instance of the two.

Any following conditions, and sub conditions will start picking from that and only from that picklist.

So, then next condition picks from that (previous picked) picklist the Family member with stand = 1. Seems a bit weird, it will always be 1. But, you create the next bubble on its start position before the previous shooter bubble is gone from that start position. Hence they will also collide and trigger the 'on collision'. You prevent this with this construction of conditions. But that is not really elegant.

The next 2 conditions pick from the previous picked picklist the Bubbles with Shooter = 0 and Fly = 1. Since Bubble in the previous picklist is always the flying Bubble, this should not be needed. Dont know why they are in place. Did you need to fix another unexpected collision ? When you re-position the bubble on its endpoint maybe ? You do not use solids. So when the collision happens, they are overlapping. Take them apart and that will probably trigger the collision check again.

Now the actions in that event work ONLY and ONLY on the objects in the picklist.

So, mainly, most conditions make a picklist, the parent condition makes the parent picklist, all other following sub conditions start picking from that parent picklist. The actions work on the objects in the picklist.

But now that 'else'. Else is truly a logical condition. It will run when its parent condition(s) did not run. The parent condition will not run when it is UNTRUE. Untrue for pick conditions happen when the picklist is empty.

Hope you see the point of it all.

Should work if you bring that condition "animation frame = 1" in event 13 above the 'pick nearest'.

Currently you pick the nearest out of all points, then you check if it can be used. And it gets no second chance.

Should be: Pick all that can be used and from those (filter) pick the nearest.

An objects Json string never includes the graphics.

https://www.dropbox.com/s/t5mv8o10zh4l3 ... .capx?dl=0

Use the same trigger only once, and 'else' is essential.

Quoted :

Just for my own understanding... (because I keep seeing this subject pop up and I never understand it)

I am quite deep into my project,

must be 600 events in total now,

In game I am creating dozens of enemies and in subsequent events or sub events I am changing their instance variables, positions and pinning stuff to them etc at the point of creation. and as far as I can see everything is working well and smoothly. I have never ever needed to use wait 0 seconds for a anything, I don't even know why or when I would need to use it, it sounds like a hack, could someone enlighten me?

Perhaps you have 'Wrapping' set on Character with a box that is 2 small ?

Dont matter that much.

When spawn ... it is the spawner that provides the coordinates

System create needs coordinates.

The most important key in there is pairing the Fade behavior with the scaling, and use the global loop to add a value to the scaling.

Just so you know.

Most movement behaviours have a build in 'clamp' system.

Meaning, they have a 'max speed'. Or, speed is clamped to that maximum.

Just calculate/experiment the acceleration to your needs.

The acceleration is a natural log. Not linear as in 'speed+1'

https://www.dropbox.com/s/nnbjt6fupz580 ... .capx?dl=0