There are three types of attributes in GameSalad: game, scene, and actor (aka self) attributes. The reasoning you are seeing "score" in the attributes menu is because that is the na

the trouble I am having is coming up with the attribute game.score - I initially created the actor for score and pulled it onto upper left corner of scene. Then under rules for "score&quo

     Change attribute game.score to game.score + 100

1) add a attribute( click on the plus sign and then select boolean) and name it bullet

Rather than changing the highscore to gamescore, *constrain* it to gamescore.

Is it possible that you have more than one game attribute named "highscore"? Is it possible that you've unlocked an actor on the scene and created an instance with its own unique ru

I am making an endless runner in which the score works fine, so I made another integer attribute, highscore, and put in an actor which is always on the screen in the scene to change game.highscore to

You would only constrain the actors if you wanted them to move together. As far as spawning goes, just pick a random Y value and then add or subtract 30 to/from it. Something like this:

change attribute game.Touches.Count 1

Your questions can be answered with variables/attributes!

Thanks for the assistance. I still couldn't get it to work though. Something I should have mentioned is I have the actors rotation constrained to a global attribute. So I'm trying to come up with a me

Constrain the Arrows rotation to the vectorToAngle

Changing an integer attribute every x seconds shouldn't cause a flicker unless the values the attribute is retrieving are changing at the same time. So if you're updating a table and then drawing val

I would think it would be easier to do Change Attribute self.Xdisplay to random(45,55), but perhaps you aren't including every value in that range.

I gave that actor an attribute call it Xdisplay.

Do you have a load screen or something that "initializes" or changes any attributes on your way to scene 1?

Make three attributes.

The Link Machine is just a calculator of sorts, stick two objects in a certain spatial relationship and it will tell you the three constrain behaviours you will need to make them stick together like t

I still don't understand GameSalad well enough to have found this on my own so I will ask--is the actual control of the constrain behaviour part of your "link machine", or is Link Ma

There is nothing in GameSalad that says a rule needs to happen at a certain point, you can get your bounce animation or rotation behaviour or actor fading to black or constrain behaviour or sound of a