Why is it that you can't just use collide to control your collisions?

If I set the vase to be initially movable then it falls to the floor as expected when I start the scene, but setting the movable attribute in a rule doesn't seem to work.

Create a game.integer.attribute called touch.

Create a new game integer attribute called "token"

Try taking out the "otherwise change attribute to 1" part. And also make sure the attribute is set to 0, not 1.

I want to find a way to count collisions of a certain actor with its self. Its kinda hard to explain.

When the player overlaps or collides with the first letter actor, change first letter attribute to true.

Should be able to use the "Keyboard Input" behavior. If you want the user to chose their own password you can get it and save it in an attribute. Then load it back up again so when t

it seems to happen every time after I alter one attribute, and immediately alter another attribute in the same actor. The second actor rarely saves, I usually alter one, save and exit and alter the o

Is anyone else having problems with using the saved attribute command with keyboard input. I'm basically having a person enter their initials if they beat the high score. I save the high score attribu

Make sure the master actor (the one giving it's X position to 'attribute:game.PositionX') is beneath all the other four in the the layers panel.

Secondly, I see what you mean now. You'll have to erase that boolean attribute and use an "Integer" one instead, and call it the same name. Sorry for the confusion. Also, Gamesalad w

Does GameSalad automatically know that a boolean attribute called "LevelUp" means level up? Or is this something I need to define elsewhere? Like "LevelUp" means wh

Rule 1: constrain attribute: game.PositionX to self.position.x

You could make a boolean attribute in the "Game" column, and call it "LevelUp."

So, I want this "level up!" artwork to flash on the screen every time the level goes up, appearing for about a second. I know I could create a rule for EVERY level, but that seems li

So I'm getting really frustrated working on a project because after about 3-5 minutes after opening and working on my project GS decides to start changing my attribute values to 0 or a previous value

iPhone 5 size and made overscan for actors like: Attribute game.device screen size = 480, change attribute: self.size to 480 to optimize to iPhone 4 and 3GS. My question is here, how you said I do no

I created a rule which says : when self.position x= 0, change attribute, self.position x to self.position x + 320. This did nothing. The game is landscape and the floor is moving to the left at a spee

change attribute selt.position.x to XXXX