One more question.

Presuming your Speed attribute is a real attribute, you could use a Constrain Attribute behaviour along the lines of:

Make an integer attribute called game.playerTurn and set it to 1. It will switch between 1 and 2. Make two more integer attributes called game.player1Score and game.player2Score. Make a text attrib

assign it to an attribute of type Angle

(if rotation > 30 and < 180 change attribute...) The problem is that after one complete rotation, the angle of rotation is registering higher and higher rather than starting over at 0.

If attribute game.score > 500

Constrain X position to:

IAP request purchase - IAP Buy Item - Rule when touch pressed - rule text expression (table,1,5) is purchased - change attribute game.noad to true

If this is all you are trying to do you could use Interpolate. make a 'real' attribute - 'orginalX'

Make an (integer) attribute in the spawner, let's call it Food.

When you use a change attribute behavior, you're setting the value of that attribute to a number. So if for example self.Position.X is 200, then change attribute self.startingX to self.Position.X set

@tatiang I don't understand something about attributes, creating an attribute and changing it to self position X shouldnt be the same as using selfposition x as well? (To make rules)

Make a 'real' attribute, let's call it A.

One thing to consider is that the condition self.Position.X=self.Position+40 can never be true (if you solved the equation x=x+40 by subtracting x from both sides, you'd get 0=40). An actor can't be

i want it to stop, and I also tried creating an attribute... "If self position x = self position x + 40 (the width of the square) then change attribute, set linear velocity to 0" bu

I'm trying to get my unlocking of levels to save. i have levels 1 through 10 working. But levels 11 through 14 aren't saving. i have to have the unlocking attribute a boolean attribute for levels 11 t

So I'm working on a project involving two main actors. I'm using a Boolean attribute to change which one is controlled, but for some reason I can't get "control camera" to work on bo

the onscreen joystick did, it would be easy to constrain the players movement to those variables instead of the custom attributes we created.

You can only access this attribute within an unlocked actor on the scene. This is why the camera origin is a scene attribute.

My health bar demo allows you to constrain an actor to another actor and use self attributes as needed for customization: