(Rule: "If peg's custom attribute 'user-selected' is 'true', change Physics > Moveable to 'true'")

I added a Game Attribute call "Animation" (it's an integer) and then added a rule to the "Play"

Another possibility is to have the tongue positioned offscreen. When the mouse is clicked, the tongue appears using Change Attribute and changing the self.Position.X and self.Position.Y values. You ca

You can have the pegs be set to be moveable unless they collide or overlap with the ball (the physics attribute ARE changeable via rules). I don't know what the balls are doing, so I'm not sure if a t

I have accomplished the sensory aspect (easy enough), but for some reason I cannot get the ball to outright stop. My first idea was to simply apply a "0" to all velocity attributes o

the click is. Easy enough. Now I've seen people constrain these types of size changes so that the "growth" doesn't come out of the center and go in both directions. (i.e. power bar

Attributes- GoodGuyNumber, BadGuyNumber.)

Create an attribute (boolean) called dragging.

First I created attribute (boolean) "dragging."

http://gamesalad.com/wiki/how_tos:gsc_mouse_movement?s[]=constrain&s[]=actor&s[]=touch

actor attribute self.random # (leave it set to 0. This is so it does not trigger prematurely)

when size = 100x100 change attribute self.random # to random(1,100)

1. Is there any speed advantage to taking the sounds out of the actor and dedicating that function to a 'sound actor' that waits for a game attribute change.

The first drop-down menu in a Rule says "Actor receives event" by default. You can change that first drop-down to listen for an attribute instead.

I've been reading your reply and your reply in my other thread. I've noticed something. When creating a rule what is the difference between "change attribute" and "when?&

You need to create a global game boolean attribute called something like pleaseStartCalculatingTheScore. (you can shorten it of course)

---- Delete the Change Attribute Behavior

It seems that I can not capture a scene attribute (camera x in this case ) until the actor is on stage. — Is this correct? @PA

Create a rule w/ a boolean attribute that switches to true when you touch the touchblock, and otherwise false. Set the cannon to only fire when 'touchblock' is false. But you must make sure the actor

in your actor list it will only be 1 actor. they will have different values for the same attribute when placed in the scene.