(Quote)

Delete the change attribute rule game.score to game.score + 1.

I have two game modes that use the same game.score attribute,

In GameSalad, true/false and 1/0 are essentially interchangeable. You can make a boolean and, for example, say "Change attribute game.boolean to 1" and that will set it to true. In t

Somewhere in your rules, you have another change attribute behavior that is adding one to that value. You may want to turn rules off and/or delete actors from the scene until you discover the cause.

I have put in the rule, when touch is pressed- change attribute game.score to game.score+1.

There does appear to be a spooky little colour bug in gamesalad. Adjusting values in the colour picker whilst observing the actor colour values (spinner down) in prototype attribute pane gives strange

I made an attribute, I called it X, I changed that attribute to (random(0,1)*469)+148

Your enemy actor is detecting the first bullet and it decreases the life count. However, when you rapid fire, it gets caught in a loop and fails to detect the collisions because there are so many. If

Hmmm ok but my Self Life is in the actor its self...should I make that a game level attribute instead I'm thinking now? Because yes in my enemy actor I have a rule that when actor overlaps or collid

I had that problem so I use a constrain attribute for my actor. that way it won't move.

I created a Sign Up scene, where the player enter his name, email and password, the server returns a +1 attribute and he is in.Wonderful.

You could have a game integer attribute , and each character that's available has a number assigned to them. When a player selects a certain character change the attribute to that charterer.

Also, you have your X constrain and your Y constrain in sync with each other, which kind of defeats the idea of a more organic random oscillation, as you have it set up the actor will simply move in a

(Quote)

Check out the Penguin Paradise template for some slippery floor movement. Movement is done with the Accelerate behavior with limits set by Rule conditions instead of the Max Speed attribute, so fallin

I want to make an actor (a moth) follow another actor (light), which is the player's mouse. I've used the Constrain Attribute to place the light actor always in the position of the mouse. I've done th

@Socks I was interested in your last example..."Constrain self.locX to self.time and the actor will move across the screen - very slowly! - (while continuing to wobble)." I couldn't

You might try turning off the 'constrain self.position.x' behavior. It seems to me that the oscillating up/down and rotation behaviors you already have will give you the floating effect you are after

You can change the self.locX and self.locY attributes to whatever you want/need.