Lastly, here is how I am loading IAP made inside the first loading scene. I am loading the tableCellValue amount(integer) of coins to game.attribute "TB - IAP".

Every since I started using tables to save, that's all I do. You have to change the table cell value then save after. When you start the app load the table cell values into the attributes. Or alternat

I set them up using a table, so should I use behavior "save table" or save the actual attribute with behavior "save attribute".

(Quote)

... if you update a global attribute that is used within an every timer like you have there then the actor that is on the scene already will not use the updated global value.

that the "Spawn Speed" real attribute was subtracting properly every 5 seconds, which it was. However, the second timer in the ruleset, which is supposed to spawn the cannon balls e

drag and drop. How would the attribute increment without a change attribute?

An actor alpha color is its transparency so by making its alpha less its transparency will go down. You could make a rule that says; If touch is pressed change attribute self.color.alpha to 0.2. That

to make another rue in the vulture that is; If attribute self.position.X = (whatever position you want the vulture to drop eggs from) then spawn actor egg. Then you need to make the egg move downward

Start by Googling save attributes gamesalad. You can watch one of the tutorials about high scores, for example, to learn about how to save and load attributes. Or you can use tables to save and load

I uploaded pictures of my code. I changed the attribute to (game.Weapons-1)%2. with Weapons being a integer of 1. Thank you.

Place a Log Debugging Statement inside of the health rule and watch the Debugger window to see if the statement/expression appears. If not, figure out why that condition isn't triggering. If it does

-Rotation of clock hand is constrained with the DayCountdown attribute

1. Comparing the value of an attribute in an actor to the value in a table

-constrain enemies position to a table to let towers reference

yes the specific thing causing the game to seize is the acceleration attribute on the projectile itself. more specifically it's the direction I used that caused the game to crash the "self po

I don't see an active attribute under touches.touch1, only x and y.

Change attribute game.Boolean to not(game.Boolean)

change attribute self.motion.linearVelocity.x to -self.motion.linearVelocity.x

point of the number is, so a different game attribute is needed for each different number being displayed. It's still super-easy to add one to your game, but additional ones will require a few more s