you could also add variables to the constrain so it varied as you wished from a very exact position, or you could add delay to the paddle's movement (again with a variable possibly).

The thing is about making an integer attribute called 'level', and when you reach a goal, you change that attribute to 'level +1' and save it.

change attribute self.motion.angularvelocity to 180

attribute for device.game.musicvolume to game.musicvolume

information needs each grid space to send to an attribute that is visible to other grid actors (or in the case of edge or empty space for there to be a null value). The moving actor has to make it's

I wouldn't use collision but grid state as an attribute integer for each tile at a scene or game level. Then use a check of self position to organise the check of neighbour's attribute state. There wi

Create two Integer Attributes: a and d (put the default value of d to 0)

No it wont automatically reset. Youll have to change all the attribute back manually and such that you need to there starting values

6. Attribute viewer. Help us see what is going on and debug.

Game attribute - LevelBeingPlayed (integer)

Set it up as NextGen said but have two High Score game attributes (highscore1 and highscore2).

you are loading/saving 100's of the same type of attribute, where typing it in would be MUCH faster (they already have it for the Key, why not the first part?)

Have a boolean attribute, called ResetScene, set it to Change Attribute > false in a rule somewhere on the scene

Have a boolean attribute, called ResetScene, set it to false...

I wouldn't use collision but grid state as an attribute integer for each tile at a scene or game level. Then use a check of self position to organise the check of neighbour's attribute state. There wi

6) Pixel Collisions

1). If a piece of road goes from left to up (I don't want the player to be able to rotate any pieces) then it could check the grid spot to it's immediate left and the grid spot directly above for a c

integer attributes scene.Time1 and scene.Time2

I've tried creating a game attribute "playerX" and constraining it to player.position.X. Then, in the moving platform's behaviors, upon colliding with player, it constrains/changes (

I have a rule that states when enemyX (a real attribute) DOES NOT equal (and here in the expression editor I want to say 300-400)