You definitely don't put your Load Attribute behaviours in your splash screen or even at the side of the menu, i.e to load as the menu card is opening… otherwise you'll have the users loading somewher

change attribute;

I want to change attribute to a random numbers between 1 to 1000

create an attribute for each timer and change it if u hit the time then save the attribute.

Just have an attribute, when player buys product change levels unlocked to true

Change attribute game.level1score to 0

Try the following or similar, see if this does it for you. Make a new integer called Mainscore (game attribute)

i tried to give each scene a number like attribute: no more score = 0

@Socks has every test you have done, been with real game scenarios? Where actors have a lot of rules and and constrains and artwork?

I put three of those actors in the scene (I did this because I only want my time to be in the minutes, i.e, 2:00, 1:53), unlocked them and said constrain attribute > self.digit to game.time%60

Either way, put a temporary actor with a Display Text in it to show one of your problem attributes, play your game til it changes, reset it by pressing the new game button, then immediately go back to

you turn the device off and on, then surely your attributes ARE being saved as you want? :-?

Spawning would work. You can also set up x/y positions in a table and have each actor change attribute self.position.x/y to the table values. That way if you want to change them en masse you just ch

@DaGreatness The problem is that you have used the game.What Level Is It attribute in your tableCellValue expression in the Stars Rating on Level actor when you should have used self.What Level is thi

One of the big challenges of an 8-bit pixel perfect environment is I need to constantly constrain moving objects using the floor() function, so that the art is always crisp. Only testing on an actual

When i go into the star display actor, this is the one that has 0 stars on it as of right now, and when i constrain it self.image to tablecellValue(myTable, (Self.what level) or (Game.what level), and

I've been working with gamesalad before where the rotation attribute returns degrees without going back to 0 after 359. For instance, two clockwise revolutions would return 720. Two counter-clockwise

@Fal01 OK, in that case, surely we've come full circle back to my original suggestion of your problem, that the game attributes aren't being saved, or if they are, aren't being loaded with Load Attrib

OK, providing you've a clean differentiation with programming between your new game and your continue game buttons, I can't really see why you should have a problem as long as your attributes are not

Hi @Fal01 I'm guessing you're using game attributes, these are "remembered" as they are updated/changed, even when going back to the menu and pressing the Continue button, all while