well i dont think collisions work if they are both interpolating. he probably is using something else

Change attribute changes one time where as constrain constatly check what its constraining to.

make an invisible actor on the other side of actor2 that once the actor1 touches the invisible actor it make a global boolean attribute true which then you can set a rule stating if boolean attribute

its still not working? I did exactly what you told me, and interpolated the attribute self motion linear x/y to 0, didn't work.. don't know what im doing wrong?

Constrain constantly changes an attribute, meaning that for example you do actor.x = actor.x+1, the actor will continuosly move towards the right.

change attribute game.startMouseX to mouse.x

What's the difference between Constrain Attribute and Change Attribute???

interpolate attribute self motion linear x to 0

Yep only have the switch scene rules where when attribute = whatever switch scenes only in the scenes you want to switch to. And then lower the max random number to the ammount of scenes your switchin

you will also need to use keys when saving for future uses otherwise just saving will not keep the attribute once the app is closed. That may be a given to some, but I figured might as well mention it

If you are want to change it based on an event then use a change attribute for self.color.alpha and 0 is transparent and 1 full you can set it any where in between those

or you can run a save attribute when you actor changes scenes

If you don't want them to EVER come back, even if the user restarts the game, you would have to also save the global attribute jonmulcahy mentioned above.

you'll need to keep track of them in a global attribute and show or hide them depending on that.

Make an attribute called Language.

a correct anwer is givin it adds one to the attribute. Then when you reach the last question (say theres 10 questions) have a rule when answers complete = 10, display your complete image or whatever

i got it man, here tshirtbooth tutorial if you haven't seen it. now what you want to do is change the drag actors otherwise constrain attribute, and change self.Motion.Linear Velocity.X *0.95 to the p

Ok, so false alarm I guess. It was a strange bug with GS. I made a new file and used all of the exact same behaviours on both a local boolean and also a global boolean and both worked. The last file w

I tried everything, but I don't remember if I had a collision attribute on A... gonna try it out in a few minutes. It does reset it's position on overlap or collide.

do you have a collision attribute on actor A saying that it can collide with your ground actor?