or if you have a point and health attribute you can do change attribute

You can test a save / load attribute by clicking the reset button in creator. This simulates an app restart on a device.

but, then i need it to change attribute again to random(1,4)... but i don't want it to be the same number. Sorry if this has already been answered!

if i press shift to constrain the shape it starts scaling proportionally but then it stop and the image didnt finish proportionally.

Load attribute: key: music, attribute: game.music

the "loader" actor loads the attribute on the first scene

Pretty sure you need to include a save/load attribute actor in there...at least a save where your on/off switch is and a load on first scene to "remember" attribute and act according

Yes, using change attribute game.score to max(0,game.score-50) should work fine.

For the matching coding I used 2 game attributes(integers) CardID and CardIDA so each letter pair changes these attributes e.g: A changes them to CardID 1 and CardIDA 1. Then B changes them to CardID

I thought that you only needed to load attributes if the player exits the game? Is this incorrect? shouldn't the attributes remain the same between scene changes?

I currently have a button that works for the sound effects, because I have set all sound effects within my game to use an attribute called "sound effects volume" to determine their v

There must be errors in your code somewhere. Make sure you also have the load attribute in any other spot the game might start from. This is why it's best to use a table. If your game freezes using ta

I have two attributes, both are INDEX (so they can't go into negative numbers)

the simpilest solution and slimest method code wise is to switch to an index attribute as it won't produce negative numbers. Just change your highscore to an index in the table and see.

because my original high score was also an index attribute and it just wasn't working. It would update the score sometimes, not always, and would sometimes pull a completely random number for the hig

I have multiple actors that affect my game score attribute by +10, +50 and -50.

So the issue would be in the Score attribute even though it is showing that it is recording the score.

Rule: When game.game score [my attribute] > tableCellValue( game.table_achievements ,8,2) [this is where my high score number was]

* No constrain attributes!

I'm not sure you understood what I meant. I was asking you to isolate each attribute and determine if it was working properly. So you'd look at each timer attribute and each score attribute separate