Also, one of the ways that I "search" for attribute usage is I hit the '-' on the game.attribute that I want and it gives a list of all the actors that reference that attribute.

attribute for the underlying position and then constrain the actor position with an offset of half the current width to that number.

Also, one of the ways that I "search" for attribute usage is I hit the '-' on the game.attribute that I want and it gives a list of all the actors that reference that attribute.

Interpolate Attribute: self.Size. Width To 300

What did work though was having another actor spawn the 30 pucks on scene start. (using a rule, a timer and an attribute to count down from 30 to zero).

actors manually? (I thought about having a game.attribute of game.blockdestroyed, so if blue is destroyed it changes to 1, then on the flying actor if game.blockdestroyed = 1, then change self.red/gr

I honestly believe that I'm doing this right, but I can't get it to do it. I've got change attributes on the pause screen custom fonts. (I just tried it with constrain attributes and it did not work).

Also, one of the ways that I "search" for attribute usage is I hit the '-' on the game.attribute that I want and it gives a list of all the actors that reference that attribute.

Attribute game.tap is true

Back to the holding finger down aspect: without seeing what Physics you're using I'm not 100% certain that a boolean attribute acting as a switch would work, but it might.

You simply have to reset the spawn amount to 0. Right now it won't spawn any more because the attribute is at 7 where you said stop spawning.

that again (slightly amended and using a boolean attribute called Move):

BUTTON/ACTOR which will reset to o and save attribute..

yea just change it to 0 everytime you want to reset the score.. remember to do a save attribute feature EVERY time the score changes or gets a reset that way it will always stay updated if the user cl

is resetting the highscore as simple as a change attribute highscore=0 and then resaving again ? can someone please confirm this for me.

First I created a game.attribute integer called Jump

yes a constrain to an x and y will make and actor not move however if you get a lot of constrains going at once you will affect your games performance.

Attributes: Player 1, player 2, player 3, player 4.

Alrighty then, would it work if I create a X and a Y attribute that constrains itself to the actors position when he dies, and then constrain that actors possition to that attribute? thx tsb

Attributes: Player 1, player 2, player 3, player 4.