The image below shows what it does in-game. I have a boolean attribute, "left", that is set to "true" when the character pushes the left arrow. As a result, the ani

(Quote)

The problem with GS Project Attributes (which lets you analyze attribute use and reorder attributes and tables) is that if you try to reorder them and press the button to generate a new file, it simpl

Not sure which is more performance taxing, to constrain an actor behind the main actor emitting particles. Or to have the actor be stationary and set the offset of the particles to Actor1x - Actor2x,

     Change Attribute game.foundCount to game.foundCount+1

The attached file has two scenes. The first one uses the Move behavior (and your left and right keys on the keyboard), the second one uses the Constrain behavior (and mouse movement).

Or constrain.

Create a new actor positioned under the actor you want the particles to spawn from; constrain the X and Y values of the new actor to the actor on top of it, and then spawn the particles from the botto

(Quote)

@Socks Yes, if you're using game.time or self.time, you're right. But for a more universal solution you need to use your own attribute.

Edit: more precisely, my solution was wrong, it's still wrong when you include an attribute.

I think you should have an attribute (or equation) where you have a zero ?

If you are increasing an attribute value, use the minimum function to limit the value:

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

Can somebody please help me understand this formula. I've constrained the position and rotation of my "head" actor to my "player" actor and it works.

You could also have each enemy that is spawned increase the kills counter when that enemy is spawned by putting a Change Attribute behavior in the enemy that says:

Game attribute: 'Kills'.

thanks

Make a game attribute.

Constrain basically means change on every frame, so on every frame your actor's LV got set to 620, overriding the gravity.