Yeah, you have a "when touch is pressed" rule in there to go to another scene that is attached to an attribute change. The problem is you can't touch an attribute with your finger. Y

Attribute: {game.Team...} ≥ 2

When attribute = or > than 2:

I want a go button when a attribute = or is greater than 2.

say you have an attribute game.level1hiscore (this keeps the highest number of stars on that level) and you have game.level1newscore ( this is the score at the end of the level every time it's played)

But only one little thing, I have in the "game over" scene a "Save Attribute" and in the "welcome page" a "Load attribute"

And in place of OnCreate, OnDestroy…GameSalad uses rules and behaviors that are tied to events. When touch is pressed, or when actor collides, or when attribute equals, and even device tilting, etc...

I wanted to constrain an image to my main character. I created a global attribute for X and Y, had the global attributes constrained to the main actor's X & Y. Then I constrained the 2nd image

Then you would need an actor count attribute that keeps track of how many actors are onscreen. Every time one is tapped and destroyed, change the attribute actorcount to actorcount -1. And when it rea

when attribute =0

have an attribute called lives, when you want to take a life away change attribute lives to lives-1

Hey Guys, liamo here I have a problem, I am trying to change the attribute of some pits when an attribute called looped is true, this works when i press the play button in the editor, but when i press

i should also add that i would have it when game.lives is equal to or less then 0 and not just =0, so you dont miss the trigger if it fires to fast when your subtracting from the attribute

1. POLYGONAL coliisions (per pixel collisions aren't possible in Box2d)

When attribute game.lives = 0 change scene to you lose..Or something like that

when the live attribute=0

Ok and would I need to make an attribute for PlayerY? If so, how would I do that?

I am guessing the answer lies in . . . . . . . . . . . . (wait for it) . . . . . . . (drum roll) . . . . . attributes.

Up the angular drag or constrain the rotation speed to self.motion.linear velocity.x

5. I like the idea of a performance/step analyzer - basically something to show exactly what is happening (and all attribute values) at each click. Putting in debugging steps is a little too time con