Yes, you can certainly change an attribute inside of a loop (try it!).

Is it possible to change Attributes in a Loop, similar to changing TableCellValue in Loop?

* I am going to have all Hero stats based in a second Table, which will reflect the constantly changing Stats (such as gold earned, damage dealt, etc). This will be Table based, instead of Attribute b

OK great, thanks yall! I hadn't even started thinking about Save/Load yet. I definitely want the game to save the entire game state easily so that definitely answers the attribute vs table question!

@pokapola Reliable is not really the right word. Attributes can be a big hassle when compared with tables. To save ten attributes, you need ten Save Attribute behaviors and ten Load Attribute behavi

I've been having an issue with the "Restore IAP" behaviour. When the IAP is restored do I need to make a rule to verify the callback and update the (Remove Ads) attribute? I have had

I just reorganised some of the coding in the 'constrain rotation of cannon' attribute:

I made it so when a ball overlaps or collides with actor 2 it will change attribute to score plus one. But when only one actor goes through actor 2 it adds like 6,7,8 or 11 points to the score instead

Save Table behavior. For any game/scene/actor attributes, you need to use Load Attribute and Save Attribute behaviors.

Saving a games state requires you to know what variables/data you want to save beforehand, and then you can save them via save tables or save attribute.

You're welcome. I forgot to mention that game.boxTimeStamp should be a real type attribute.

Constrain game.level to (sqrt(100*game.exp))/100 provides a nice scaling to start with, change the numbers around to provide different scaling amount.

That's right. I wasn't sure if that's what you wanted. In the box actor, you'd need a lone behavior to change attribute game.boxTimeStamp to game.Time and a rule that says When Touch is Pressed, cha

The Load Attribute behavior usually would be on an initial title/menu screen and not inside of a rule.

When attribute game.xp > 1000, change attribute game.level to game.level+1 and change attribute game.xp to 0. Or, Constrain attribute game.level to floor(game.xp/1000)+1.

Change attribute game.highscore to game.score

Just realised I don't actually know what you meant by that. How easy should this be to replicate? Fast constrain? What this

(Quote)

@Socks Ah that was stupid of me, I can just use the custom timer (or speed) with a greater value:D There is a question indeed, how do I constrain your alpha method within the 3d spinning particles. I

That menu of mine that is linked to above uses the 'fast constrain' developed by Socks, it might help if you looked at that thread: