QUICK Question about Save Attribute & Tables on GS Preview vs. Published Device.

If so, You'll be making use of the spawn and random attributes and behaviors.

* Change attribute game.randomRow (integer) to random(1,tableRowCount(tableName))

@Adrenaline‌ oh ok i do have save attribute and it does work when i change scene so it must work then. ok thanks.

Make 2 new game attributes, one for each rotation direction.

@macman123‌ I was in the middle of typing out a long explanation on how to save attributes, but then I realized it might be an even simpler solution.

@macman123‌ did you just put the change attribute on that retry button, or did you put it in a rule --- if touch?

What I'm saying is, you'll need to create the "Change attribute score to '0' " after the score has been displayed to the player, so, for example, put the "Change score back

@Adrenaline‌ i put the change attribute at the retry button at the gameover screen so its like when i want it to be showing the score but not restarting with the same score

You need the score changing attribute to display after you've saved the score somewhere.

It sounds like you're resetting the score before you really want to. So delay setting it to 0 until after the Game Over screen. Move that change attribute behavior onto something else that REALLY rese

Wherever you have the code that restarts the rest of the game, add in a change attribute behavior that sets the score to 0

I too mostly start from iPad. Reason being that's I find it nicer to build from a bigger scene. For my last build I used overscan and had the actors with adjusted with a change attribute. It's not ide

I have changed my jump settings to match what JodyMitomas has outlined & my actors attribute motion linear velocity X to 200 the actor now moves accross the screen & collides properly

Like I told you previously, instead of using a CHANGE SCENE attribute, use a PAUSE GAME attribute to open up the "Score/Retry Menu" at the end of a level or death.

Second, I finally found a video on YT which addresses my issue, and uses the save/load attribute technique to resolve it. Below is the video:

@JodyMitoma‌ thank you so much for your help. Quick question: As far as the second method is concerned, do you mean load attribute to the main scene, or the game over scene, since the score is ultimat

Just be sure to have a SAVE TABLE attribute.

For that you're going to need to track what color it is. You could make a self attribute and change it's number based on the color change. Say, red = 1, blue = 2 et.... And then make that integer part

Like I said above, instead of all of this craziness, why not make the "Score" scene come up by using a "Pause Game" Attribute, then when user clicks on "Re