hmm... I understand the concept but it doesn't seem to work. Just to clarify, When I create the attribute. Do I create a "text" attribute and call it x and put in a value of real o

Im sorry. Im new to this program. For the making a self attribute. I create a new attribute with "real" type. When i try to set the value to x it just sets it to 0. Im sorry, am

thank you so much. for the constraints can I put Constrain attribute self.position.X to X, because I have multiple actors of this type spawning at different times

1. Is there away to only allow up and down movements only and constrain left and right movements. When my player hits into a block the block moves left or right a little bit. I want these blocks to

Attribute: game.soundnumber(Interger)

A boolean only allows for two values (true or false). If you only have two sounds a boolean will work fine. If you have more than two you need to use a game integer attribute and set it to 1

I think this is the reason why I ended up using Constrain Attribute Actions instead of Change Attribute ones. I was getting so frustrated why things weren't updating in the order I placed them in the

i think the internal attribute is referring to the iphones system: time,options....

Then Constrain the Attribute of the Health Bar Rotation Angle to the Main Character's Rotation Angle.

Change Attribute: game.ImageNamePrefix = "image_"

Make the following real or integer Game Attributes:

yes, i used constrain attribute.

Did you try constraining the self.Rotation Attribute to the value instead of changing? I think it's an issue with 0.8.4 that I never saw previously. I'm going around and having to Constrain things i

half of the semicircle. Rotate it with the attribute and it will look as if it's pivoting from there.

i tried to link the needle rotation to attribute (that range 0 to 360)

if you mean what i think you mean, you could do it with an attributes and a few rules. Is that bounce height going to be the same every time? If so, just create an invisible actor as a hotzone, and tw

While the Dragging flag is set, I constrain the Camera X and Y origin like this:

Choose only 1 auto rotate option in every scene attribute then when publishing only choose 1 of the orientations. Your game does not have to rotate mine are approved and they don't rotate Ghost Word

constarain attribute "self.position.x" to "40*cos(self.time*600%360)+240"

attribute － "grabbed"