It depends on the code logic you use to fire the Save Attribute trigger..

One question, i use save attribute behavior in my game. When I use Timer, every 0 second Save Attribute. But when I load it, it doesn't work. I try when touch is pressed, save attribute then it works.

you actually would not use it with the change image behavior. There is a random function. but it only works for defining a value. so you would actually use it with the change attribute behavior. You

The actor checks the value of the attribute your are currently modifying, checks to make sure that you have ample currency, and then changes the attribute accordingly and subtracts the correct amount

I have a function to save a value from a player attribute to a game attribute .. to mark each level. this works perfect on the demo but everytime i download the full app it is not working ( I have an

Change your original attribute Jump to an Integer, 0 = Not jumping, 1 = SingleJump, 2 = Double Jump.

but then who i can change the enemy attribute to from true to false when my player pass it or jump it over.

Change attribute game.timer to 30 (or whatever you want it set to)

Game Timer integer attribute set at 30

Use a Change Attribute Behavior and just change the actors Flip Horizontal setting.

You'd create a self attribute - integer type.

Create an integer attribute:

Create interger attribute: MoveDirection

2) Create a local attribute in the character to tell the game if he can jump or not. It should be a boolean. Call it canJump. I use a rule that detects if the player is currently touching the ground.

I have figured out how to constrain my distanceToTarget attribute to get a continuously decreasing number as the player actor approaches the target. However, since the distance between the player acto

animating it using interpolation and change attribute y-position of the ground but its feels way off. Please an idea how i can go about this so it feels like the character fell all the way to the gro

On that actor (level box) , i have an attribute self.mylevel, that is changed to each box so it can know which level it corresponds to (1,2,3,4....)

Another way to do this is to have three separate actors that each choose a random color value and then change a game attribute or table cell value to that chosen value. When the main character collid

Create an index attribute called start_y

On second thought, I think it is better if we don't destroy the "power button" at all. Just stop it from working and counting down (-1, -2, -3 etc.) when it's press once attribute =