To make it a little more slick, try replacing the enemy's speed with an attribute (let's call it NME_Speed), when you need it to move backwards simply interpolate NME_Speed from its current speed to t

I am (currently) using the free version of gamesalad. i was looking for something i can do when i came across in app puyrchase item. i thought u need the pro version for in app purchases. am i mistake

On a related note, is there a way to make an actor recognize when another actor has been spawned on top of it? So like if the bomb's explosion was spawned on top of an actor, that actor would be destr

When black actor is spawned, change attribute buttons inactive to true. In the buttons, when attribute buttons inactive = false, then do whatever behavior. In the large actor, just before you destro

for the Rock actor. Also the second to last Constrain behaviour needs to be constrain self.position.Y (rather than self.position.X)

(Quote)

About Lx, Ly, Lr, Mag and angle attributes - do i have to make them as a character's attribute or game's? I can't make it working. (Image)

Make 3 real game attributes:

http://forums.gamesalad.com/discussion/75220/fast-constrain-linkmachine-v2

Hello everyone.

* Change Attribute: attack to true (attack is a global attribute. It's type is integer.)

When touch is pressedChange attribute game.isRuby3Pressed to not(game.isRuby3Pressed)

....Attribute -->game.Touches.Active.Touch1 is true

Create a self.attribute in the actor a boolean name it activated.

(Quote)

Well I thought of putting it into an attribute, but im spawning off 15-20 of the same actor, and I want them to each have different values in that formula.

Say you want to change the gloves, create a game attribute called gloves and set it to 0 as default, then when the player clicks your shop button change game atribute to 1, 2, 3 ect

One way to spawn actors with different images is to change a text game attribute value right before the spawn actor behavior and then in the spawned (prototype) actor, change self.Image to that attrib

The way you communicate between actors is by changing the value of a game attribute. So create one for each item -- or better yet, use tables to store the values and then have rules that change the i

Create an attribute called TouchX and another called TouchY (make them both integer attributes).