The problem is not with saving attributes, the problem is that you never reset game.score to 0 after the player wins/loses. If you add a Change Attribute behavior to your Restart? actor, it will fix

UPDATE: Another bug has surfaced: text does not display if it contains a value provided by a global attribute. It seems to display properly if it's an actor-level attribute.

Constrain your copter's rotation to a calculation based on its motion.linear velocity.X.

i have a major isssue with my scrollable tips page. The menu does not constrain to its position. Whenever i click, it moves to the right and then the constrain rule comes into effect and it goes back

Yes, sorry I left out the attribute placement aspect. Looks like you are in business.

Ahhh figured it out by making a boolean attribute in the scene, then saying when the two actors collided, change the scene attribute to true. Then in actor 3 made a rule saying if attribute equals tru

(Quote)

Do not use destroy it will cause lag later in game. Simply take it out of screen using interpolate or constrain attribute.

Change attribute game.highscore to game.score and save highscore attribute

simple fix.. if its left or right do a text attribute if its a jump use a boolean (Image)

It would work for hundreds of scenes as you need to address change scene each with a change scene behavior as that behavior is a drop down menu not an attribute.

Just keep track of which scenes are completed with an index attribute and make rules that go to the next scene based on the scene count in the index attribute.

Define a boolean Game Attribute, and use it as trigger for change the scene.

Make s self attribute skip stage in the skip button.

Create two game attributes. Name them Spawn1 and Spawn2.

To make something rotate in a circle 100 pixels from something, you need two constrain attributes.* Constrain Attribute self.Position.X = 100cos(scene.Object.Rotation)+scene.Object.Position.X

I don't think those rules go together like that. You have a rule inside of a rule that doesn't really need to be like that. You should add that second rule as another condition by clicking the &qu

Try placing the collide test within the projectiles and make "life" a game-level attribute.

outside of the timer behavior and then use an attribute inside of the timer.

- After a successful confirmation I would like to save the attribute, and then change a Boolean attribute to false (menu control)