There might be a simpler way, but I would try two boolean attributes, firstCorrect and secondCorect, and have a rule on one correct actor "when touched change attribute firstCorrect to true&a

TSB's labyrinth video is great when you need collisions (ie bouncing off of things), but when you don't need collisions (think doodle jump or tilt to live) using the constrain method in my demo is way

when the total is reached set visible or alfa attribute of picture to true.

when the total is reached set visible or alfa attribute of picture to true.

In your parachute actor have your left and right movements as well as move down direction for example down 270 at 150 speed then when chute is activated constrain the parachute to that actor and also

-change attribute game.direction to 1

I'm not sure if you got what I meant, I meant that when the home button is pressed, yes when you start it up again it is back to where it was, but change an attribute to pause the game. So you don't g

I'm not sure if you got what I meant, I meant that when the home button is pressed, yes when you start it up again it is back to where it was, but change an attribute to pause the game. So you don't g

you could run one timer that starts when an attribute is true and not tick 'run to completion' then put another when that attribute is false. As they are not running to completion if the starting fact

Change Attribute Method,

I just use the same name as the attribute for the key, then I don't get confused.

It saves the value to the key, so each save is overwriting the next. It does not save to the attribute name but to the key.

Do I need a different key for each save attribute? Because right now I'm using the same one xD could make a difference!

Thing to remember with the save attribute feature is that you are not saving an actual attribute but a value to a key.

When s key is pressed, Save Attribute game.playerhealth, etc. I have quite a few attributes to save. I also have an actor that saves the scene number. So I have an attribute called game.WhichScene.

You probably have the attribute game.bulletalive affecting the ability to spawn (I'm guessing), so when the cancel button changes that it affects the ability for a bullet to spawn.

Change attribute game.bulletalive To: 0

Change Attribute

First I created two attributes in my actor called Spawner (invisible). The first one is a integer called random_value and the 2nd is a boolean called TimerSaysGo.

when collision with actor ... => change attribute randomSpawn to random(1,5) etc...