The way I would do that is create another attribute called control for example than set it to 200 and make a rule saying when score = control spawn actor and change control to control + 200

Attributes have to have some value and most attributes' default value is zero. So if you constrain an actor's position to x=0 y=0 it will be at the bottom left of the scene.

I have a actor centered in the scene, but when I preview it goes to the far bottom left. All I have added was constrain its position to touch.

That's simple enough, you can do it using the change attribute behaviour.

I have recently ran into a problem on an App game that I am developing. I have the Change scene attribute with Enable advertisements enabled. After the Chartboost Advertisement gets displayed it fails

Right... that's because self.Angle doesn't exist (unless you create it as a custom attribute). What you want is self.Rotation.

Make a new attribute and call it 'Angle'.

How would I get exactly what I see in the picture I posted into a change attribute box?

(Quote)

Im trying to get something like this http://tinypic.com/view.php?pic=vhw0o0&s=8#.VQC0wfnF-j8 but I cant find the angle attribute in the attribute menu.

I still don't get how, for example, I would set self.Angle to self.Rotation-180 in a change attribute thingy because I cant find self.Angle at all as an attribute in the change attribute box thingy(th

Each actor has a built-in attribute called self.Rotation that determines its angle in the scene. You can change this in several ways including Change Attribute, Constrain Attribute, and Interpolate.

I may sound very silly, but i'm trying to create a game that I plan to be similar to Geometry Dash and I cant figure out how to change the attribute self.Angle on my actor. This is the first time i've

...change attribute self.jump number to self.jump number+1

Constrain self.position.Y to . . . .

Constrain self.X to 170 *sin(self.time *300)+770

If you are changing a value by 1 every 1 second then you don't really need any additional attributes as game.time is already changing by 1 every 1 second, all you are doing is looking at one attribute

change (or constrain) attribute self.position.y 767 **

reference actor A's self X and self.Y using two constrain behaviours (etc) . . . or . . . Actor A has two integer self attributes, these are constrained to self.X and self.Y and actor B is unlocked a

In addition, consider when you are saving and loading. Attributes should be loaded when the app loads which means that you place the Load Attribute at the top of an actor's rules and place that actor