this is a little deeper than what you want but just ignore the change attribute.

80 levels broke into 4 worlds of 20 (all easily customizable) all on one screen in a beautiful smooth interface. Easily reduce the total level number, or even the amount of levels within each world. A

not sure what that attribute for mouse.position.y = 240 is up there anyway? Haven't looked at the tutorial though

You can't have collisions with constraints to x and y positions. Constrain the front wheel's position x to the (cos(angle of the bike)*(magnitude(bike height, bike width))/2+bikeposition.x. Do the b

if you want the speed to go up make an integer attribute called speed and make the speed that attribute then copy the actor for how many ever images you have put an image in every actor line them all

Did you type in an attribute? You cannot type in "game.MyAttribute" You must select it from the drop down menu. Could that be it?

1) RULE: When actor is touched AND mouse is inside Change Attribute game.scenescore to 0, Change scene to level 1(or whatever level the actor is in).

What I did was I had and an integer attribute called "Start Timer"

It's the main bit! In the actor you telling the attribute to change +1 you can't just type in game.score you need to create a booelean attribute.

to asymptotell i am using a change attribute

It definitely works! Did you create a timer? A attribute called game.time. A display text showing game.score.

Are you using change attribute or constrain attribute?

0,1 sec change attribute grand total score = grand total score - highscore (from scene)

Have 3 attributes High Score 1, High Score 2, High Score 3. Then have a rule where if Total Score is > high score 1, then change attribute high score 1 to Total score, change attribute high sco

you will need movable to get proper collisions most likely.

This is what I'm working on http://gamesalad.com/forums/topic.php?id=17422#post-132451 but I chose not to constrain the wheels and such due to the unnatural collisions and when the bike goes upside do

create an boolean attribute called alive, and integer attribute called score

I dont think yo will be able to do this. I have tried several times to get a car to work the same way. The problem is the constrains override collisions if they ever conflict with each other. so getti

You can't have collisions with constraints to x and y positions. Constrain the front wheel's position x to the (cos(angle of the bike)*(magnitude(bike height, bike width))/2+bikeposition.x. Do the b

I'd use a boolean attribute for the scene being over, meaning whatever you have to complete the level, kill all the enemies, eliminate all the blocks, etc, and set it to false. When the level is compl