Does it start again at any point? Perhaps try using constrain attributes instead of change attributes.

(Image)

Game Attribute

Are you saying that you can only press any one button if another button is also pressed? That doesn't quite make sense? You could have an attribute, game.button_is_pressed that is triggered anytime a

game Boolean attribute

So, when rather than saving attribute do a change table value and then save table.

Save and Load Attribute don't work with tables.

You can do the whole thing somewhat easier (no rules, no attributes, no tables - etc) and with less processor overhead with a simple constrain:

Very nice! And really easy to loop it as well, just adding one Change Attribute.

I have an actor that animates when hitting jump key. One way I found to change direction of image of actor is to change image when left key is down. Now i cant figure out how to animate the left facin

Thanks, I ended up creating a game.Attribute boolean that says usersTurn and when it gets to the point of the conversation i want user to make a selection usersTurn=true and that actor waits for it

But you will need some communication between the actors most likely, which can be done by a game.Attribute or through tables. Tables will give you more flaxibility, I'd recommend using those.

I don't know how your game is set up exactly but what you'd need to do is use an Attribute to store if an answer is correct or incorrect. And then use a Rule to trigger different actions. For example:

Ok - this game uses the pause scene for ads, and saves if the ad delivers or not to a game attribute.

(Quote)

did something wrong but ultimately I had to use constrains. In the end that doesn't really matter much because these constrains are only active for a few frames and that's it.

A rule to just Change Attribute back to the saved StartX,Y it if it moves... that could be good. (Image)

Something I forgot before: I would never simply constrain everything in my scene. What about a rule that only constrains them when they get out of position? So if their x or y changes from their start

The constrain approach works, and runs fine on my iPad Mini 2, so I think I'm gonna go with it, even if it's not the most performant!

120 instructions a second, every second (60 times a second constrain X / 60 times a second constrain constrain Y)