Every ator in the background has his own integer attribute.

For Grabbing, You need to Constrain Attirbute to Touch.

do I reset this? Do I need to make an (Lives) attribute for the scene instead of the game?

Yeh, there is no need to have anymore than one attribute. There is a game on my page that you can download. You'd just need to have a rule that is (for example):

For the first one, a way is to drag your actor outside of the screen area and in its Rules put a timer, after so many seconds change attributes x + y to where you want on screen

I like the method above but you could use a single attribute. Here's how I would do it. 

As spawning and destroying actors, and keeping track of associated attributes could get confusing when you start problem solving any bugs etc. At least if its all in one big scene it will be easier to

If the player taps on the door, show an animation opening a door and tranisiting (fade in-out) into the elevator. Check it with an attribute if the player is in the elevator.

create game.BallY and constrain it to self.position.Y of the ball

Create a real game attribute called game.BallX

I only realised it after release when I downloaded the released version from the app store. Its caused by the game importing an attribute which is usually used to save your gun level, but due to the

Try this. Make a interger attribute, call it invisible or whatever have it set to 0 . Then go into the actor you want to touch to make the other actor invisible. Make a rule when touch is pressed chan

Try like this. Make a interger attribute, call it invisible or whatever you want. Then go into the actor you want to touch to make the other actor invisible. Make a rule when touch is pressed change a

I would think the text attribute would be the most greedy for resources

What type of attribute use the most resources?

I define an attribute for the actor which I move with a touch, let it call okToMove and it's a bool. I set it to true as default.

now i need a second invisible collider for accurate collision but if i constrain that to the rocket or the invisible actor with the movement, the problem in the video turns up..

one invisible actor doing the collisions and my weirdly-very-unsquare visible actor follows this invisible collider (which has all the movement code..oh sorry, shouldn't mention code on gamesalad;).

You'll need a boolean game attribute to do this. Call it something like "ShowActor"

Indeed. Its not that diffucult, it would just require alot of attributes and i dont think you would completly understand from how i would type it all out. Watch the demos then try for yourself, and wh