1) You can change all the attributes to 0 except for the dragged objects positions

First off you need to change the self color attributes. Next ,Gamesalad uses rgb color. Which means if you want to change the color, mostly all the time youll have to change all the color attributes,

attribute - game.health <40

when attribute health is 20 change self color ...

Have a attribute called fadeScene have it set to 0

Just have each object detect how far it is from main actor. Then have it update an attribute with it's value only if it is closer

How would I go about doing that. If you mean constrain attribute linear velocity y to game.gravity, it didn't work… :P

OK I tried the Constrain Self linear velocity again and it just makes the ball go crazy and fly upto the top right hand corner and stay stuck there bouncing around.

You should just be able to Constrain attribute: Self.linearvelocity.X/Y to whatever

Hi I have tried to look around the forums and tried a few things but nothing seems to quite sort out the problem I am having. I am sure its really simple but its driving me bunkers :-)

I often find, when debugging a game, that I spend quite a long time going into an actor placing a display text and replaying over and over changing the attribute displayed each time to find out if it

Ok so i have an attribute where when you beat level one it turns level 1 to true. When level one is true you can play level 2. I have a save attribute behavior along with the load attribute. I was jus

a random until its different to the 1st attribute, more like a "while" statement.

- change attribute "increase game.snow_speed"+1 (which of course i guess would technically slow down the rate, but even if i could get that to happen i'd be thrilled (Image)

Create a game attribute for the speed of the background scrolling (bgspeed) with a default value of 100. Create a timer. For every 1 second, game.bgspeed+1. In the background, add a change velocity

Use device orientation through the attribute browser for the the simple version but this doesn't work if the device is locked by the user to display in one orientation, but you can get around this by

I would drop each animation in a rule and have them dependant on a self integer attribute, then switch them for each behaviour. This way you can drop out of any individual set and run another with no

I don't think you need to run the timers. Just rules that say if = then run the random. I have just done something like this that ran exactly when I wanted the random and it worked fine and with no pe

This number will then change an attribute to true for a certain, differing amount of time.

I would drop each animation in a rule and have them dependant on a self integer attribute, then switch them for each behaviour. This way you can drop out of any individual set and run another with no