Create an integer game attribute called score. Then in an actor on screen add a timer set to every 1 second:

I have tried Changing Attribute to 0 when it slows but this produces qwerky rebounds.

Has to be a real attribute(the one you make)

when actor overlaps or collides with meteor, change linear velocity to 0 and make an attribute called sticky. constrain stick to the meteors x and y velocity. and then to continue the rule, constrain

sorted finally,i created 2 real attributes target x and target y,on the target actor created 2 constrain attributes,1 change velocity, 1 timer with change attributes inside,then created a move to and

E.G. when <Actor> receives event <otheractor> is spawned (Change attribute size to 50)

constrain is not viewed as movement by the physics engine.

I've checked out how to shoot to a specific point tutorial (with game.attributes of game.mouseX and game.mouseY then on the individual actor placing a MouseX and MouseY self.attribute on them).

-Contrain actor attribute to magnitude(self linear velocity X, Self linear velocity Y)

through your credits though... I would create an attribute called Credits (boolean type)... set the attribute to false (or true) after they have seen the credits once and then save the attribute....w

What type of attribute? Integer?

Using an attribute called ItemsToCollect (for exemple)

Create an attribute (I'll call it "chance") (set chance to 1 not 0)

--Constrain self.position.x to 480

So I'd like to make my player not be able to move past a certain point on the X axis...(I'd use collisions against a wall, but I need the actor to be able to move slightly past the side walls (so like

is true you can set them all to have change attribute to move into place. when you do it this way you can also control fade in and out by interpolating alpha so you can create some cool effects that

Rather that using the 'Move' command use the 'Change Attribute' command to change the Y position of the image.

You Make Rules, If It touches this one, change an attribute Path to 1.

But if not, or if the app was Closed, you need to save all attributes you want to remain the same when the user return to your app. It will not be so easy, you can´t forget any attribute and need to s

Maybe have an attribute that increments, then when it reaches 1000 change scene. Or change level attributes like speed, and background etc.