It's really just about organization and clean code. If your attribute might ever be a value you need in another scene or an attribute that will be used and changed consistently throughout the game the

Scene attributes can only be accessed in the scene in which they were created in. A scene attribute would not be useful as a score. You'd have to create a score attribute in each scene, which is ridic

You're also constraining the actor's x and y positions to game attributes which I find strange (usually you constrain the game attributes to the actor's self x and y positions) but then I don't know h

I would like to start saving high scores and I have found many tutorials for how to do it. When I drag out save attribute on my Windows machine, there is no option for "key" instead

did not stick to the equation so I had to use a constrain attribute on them for the odd star that came out and was off it's axis. It would be better as a change attribute but I had that issue.

It started playing on the first scene, but stops when I go to next scene, I am not using reset scene. I am using a game attribute for current level and change scene behavior.

I have a game project using in app purchases. I have an attribute called coins, and when you use the in app purchase the coin attribute should be increased by 2000, 5000 or 9000 depending on what you

Never mind, i figured it out somehow. All i had to do is add a rule to my scene saying that when attribute reset scene is true, after 0.1 seconds, change it to false.

I have done a game boolean attribute called reset scene. When reset button is pressed, unpause game, changed attributes (score,lives etc) to their values and set attribute reset scene to true.

I have a game boolean attribute called reset scene. When i press the reset button, the attribute is set to true, and in the level 5 scene i have a rule when attribute reset scene is true, reset the sc

change attribute from score to score+1

I put the constraint attribute position, then gave the mainPlayer his VelocityX 250 back, and it didn't fuss one bit! Wohoo! Funny how I had to do it in a specific order for it to be okay with it! Eve

Holy smokes, I turned off every single thing on the mainPlayer, and it still crashes instantly as soon as I try to constrain my mainPlayer with an empty actor! GRRRRR

turning them ALL off, and see if it allows me to constrain.

I have a MainPlayer actor. I have a shadow constrained to his position. I also have an invisible "collide" box constrained to his position. These work fine and dandy.

Lastly, be sure to give the 'tree' a TOUCH Condition. Under the DO area, place a CHANGE ATTRIBUTE there... Before we go any further, add an "integer" into the "Game&quot

m/discussion/68320/when-actor-is-missed-change-an-attribute

(Quote)

This seems to have created the random interval of 5-10 by setting the attribute game.PlayCounter's value to 0 at the start of the scene.

When actor's touch is inside change attribute to +1, else; change attribute to 0 (also; rule/ if touch is outside change attribute to 0)