I also have an integer game attribute which is what I am referring with the in app purchase, but still no second field when clicking on consumable...

You must be selecting a boolean attribute, which is why your not seeing the second field to fill in - you'd want to select an integer attribute. You should then see another field pop up for you to fil

I set it as consumable, but it only lets me choose the attribute that will change, but not what it will change to. In a video posted in TSHIRTBOOTH's channel there are two fields when the check is se

change the rule around. set self.Attribute to 3 and have it in reverse

its a fairly simple rule that says "if self.attribute.x < 3 and actor recieved touch"

( Table(s) and Attribute Rules and Display Text Behaviors and On Touch Rules. )

Table(s) and Attribute Rules (Image)

1. Create a new boleean attribute and call it "loading"

ive got an integer in a table and i want to have a rule that accesses that value....i tried using a self attribute that changes value right to the table cell value before the rule but its not working.

constrain attr

Just create a button or rule that says when this is pressed or this is true/false or whatever, then do this;* Change a table value or attribute value (just create a game attribute named Score or whate

@POM -- you are right, there probably isn't a relationship between 60fps and many of the behaviors. For example, a constrain behavior will work as fast at it can.

Constrain Attribute: Self.Angle to: VectorToAngle(Self.Position.X-Game.mouse.position.x, Self.Position.Y-Game.mouse.position.Y)

can a cell in a table be an attribute? or an expression?

I understand how to constrain a paddle inside the viewable screen so it doesn't go off the side and disappear. However, I need to constrain it to a rounded rectangular shape. I could get it to hit the

Constrain X to 160*cos( game.Time *200)+512

Constrain:

Change Attribute self.position.X to floor(self.position.X/32)*32+16

the way you are thinking is really the only way since we cant change the size of the bounding box of collisions (yet). Just limit the amount of actors you need to have glowing and the performance loss

In the constrain width change magnitude() to min(someValue,magnitude()) where someValue is the max width you want