There's this obsession on the forums currently about over-optimising. You really don't need to optimise anywhere near as much as people seem to think in the majority of games. If your game isn't extre

I have specifically avoided mod() and div attributes. My intention was to try a different method to the standard one, and use text functions instead. My priority wasn't to make things more processor e

I am almost positive it it a bug in GameSalad because I have one scene that works, copy it and nothing works anymore (no animations, no collisions, no movement at all). GameSalad developers please loo

@RabidParrot Ok, that makes sense. I am adding the IAP table data to a game coin attribute, so I will add the change attribute rule in my loading scene. Thanks.

(Quote)

Does the app crash, or just takes a long time to load? In previous versions, if a level had actors with tiled isntead of stretch attribute, it would crash. I'm gonna test later tonight to see if this

Add a self attribute of type index to the font actor and call it "div".

(Quote)

(Quote)

The change attribute behavior is for if you are taking the coins you saved in your table and are transferring it to a coin attribute.

Yeah before learning this whenever i made an actor follow another actor i had to constrain x and y game attributes then constrain self.x and self.y of my follow dude to these game attributes..and it a

Sooo, as for loading the tables... If I've saved them accurately, do I need to use the change attribute rule in my loading scene? I'm confused, if they automatically load up (if saved properly) what's

In the same way we could say Change Attribute X to Y (where Y is a changing variable), the behaviour will only take the state of Y at the time the behaviour is triggered and copy it to X, it won't con

change attribute game.SpawnTimer to 1

Also, don't load your values from the table with the "Load Attribute" behavior. It's easier to just,

Downloading the game won't help me determine what's wrong because the problem is likely with attribute values or rules that you've set up.

If you only want something to happen once, change the value of an attribute (e.g. a boolean) and add that attribute as a rule condition. So for example:

Lastly, here is how I am loading IAP made inside the first loading scene. I am loading the tableCellValue amount(integer) of coins to game.attribute "TB - IAP".

Every since I started using tables to save, that's all I do. You have to change the table cell value then save after. When you start the app load the table cell values into the attributes. Or alternat

I set them up using a table, so should I use behavior "save table" or save the actual attribute with behavior "save attribute".