I've read in some threads that "constrain attribute" is more likely to affect performance; I haven't come up on booleans doing that.

Don't have it change on a button press. Have the button press change an attribute and have that attribute change the scene and turn it off.

Sometimes one rule is too many. Sometimes 20 rules are just fine. It all depends on things like Constrain Attribute behaviors, Timers, Loops, etc. There's no set number that indicates a problem.

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

Attribute "game.Players.Player 1.Start" = "true"

@jamie_c A game level attribute?

You're talking about the position attribute of the text display, right? Yeah, not in version 10.

(Quote)

Moving the slider right or left would move the orbit actor right and left but not in a straight line..... It moves left and right constrained along the circle. I think the diagram explains it

You'll need two game attributes, game.score and game.highscore. And you'll probably want to load and save at least the high score attribute. You can pause the scene or change the scene to show a gam

If you have an attribute for the power ups, lets call it PowerUp, you would set up a rule like this:

Create an Integer Game Attribute named Coins, starting at 0.

Change attribute game.gameoverBoolean to true

You should constrain attribute self.y to the y position

because I couldn't imagine saving and loading an attribute every .1 seconds. That would definitely lag.

nm, I got it.. just had to change the constrain behavior in the player's backstage to a rule where if the player's velocity > 0, the attribute is constrained to -self.motion.linear velocity.Y o

@http_gamesalad unchecked at start. Have it checked when game over is true. Or use whatever attribute your using to say that your game is over.

I'm making an endless runner type game where the player only moves up and down, but objects in the scene come from right to left (similar to flappy bird). I'm trying to constrain the speed of said obj

I fixed this by adding a timer to control both my score and change attribute high score at intervals of .1sec

I think you'd have to keep a constrained magnitude self attribute (DistanceToTarget) going that shows the characters position to his intended stopping position and when that magnitude gets below a cer