If you put a Boolean attribute in the first box in a rule, the second (comparative) box will automatically switch to a true/false selection box, so you can not compare 2 booleans to each other.

For example, if you wanted to check if your boolean was true, create a game.Boolean attribute, constrain it to the target you want to check against and create a rule on touch that says if game.Boolean

i can not say "If Table1,Row1,Column1 is TRUE, then......". I wish I could, but the way the rules are set up, I have to enter a solid attribute FIRST, and then compare it to another

Make a scene that has arrows. The arrows move up and down the achievements. Have an attribute that has which # is selected. Arrows change the number. Have actors that display the image, description, n

ok. it is like create boolean attributes in a achievement scene and when game score is 100+ then change attribute etc etc?

Change the attribute you had changed with the in-app purchase.

Looks like I have to add a button to my main screen, and add a rule on this button so that when touch is pressed, it will activate the PRO behavior "In App Purchase Restore Item Action&qu

What if you create a attribute (boolean) that are set to true.

Change attribute linear velocity x to 0

3) Make 2 new attributes

Change attribute linear velocity x to 0

Inside, make a "Change Attribute" behavior and change the score to score + 1. That means if the score is 4 it will say change Score to 4 + 1 which is 5. Finally, add the destroy beha

One way of doing this is to switch the "wrap x" attribute in the scene>Attributes tab in Mac Creator.

Attribute: game.Clock.hour = 17

Have you try to create game attributes to constrain position on the block and to constrain the pipe to those game attributes?..

-- Attribute: game.Clock.hour < 6

One way of doing this is to switch the "wrap x" attribute in the scene>Attributes tab in Mac Creator.

3. Add two "Constrain Attribute" behaviors to the actor,

Not by default but if you SAVE your Table or Attribute, whatever you use, when new level is unlocked the user can shut down completely and the progress is saved.

Cheers for the swift reply guys, it's a shame you cannot do this action, but like @tatiang mentioned there are ways around this, however they often involve constrain attributes etc, which are performa