have a rule that says When game.bMyIAPBooleanAttribute = true then save whatever amount of coins they bought to your table. Use a change attribute action to update your coins attribute and a change t

Thanks that does make sense except that I don't see a "load TB" behavior. Are you referring to the "load attribute" behavior? Because if I use that I can choose a k

Thanks for that tip. I do use save table for my non consumable which is what I learned in game salad guru's videos. But I just use a save attribute for my coins table and regular load attributes for t

add an (an less you all ready have one for the lives) integer game attributes go to a random actor in the scene put a constrain attribute constrain game lives to game points then go to the lives and i

There is no need to place the two constrain behaviours within the 'every 0 seconds' timer.

when I adhoc test on my iphone. I have save attributes for both types of IAP. However when I close out the app and reopen it is when I have issues. I have load atributes for both types of save atribu

* Fixed issues with Desktop Scaling and Creator. Setting Desktop Scaling to 125 or 150% will no longer cause the Attribute Browser or Expression Editor to be hidden from view. Preview will also now sc

change attribute

Are you using a constrain attribute on the actors velocity? If you are just using velocity, it will be affected by angled ramps and such. A constraint on the velocity will force the actor to maintain

Make game attributes for the X and Y positions of the tank (and rotation if you want the gun to move with it).

Not sure if this will help in your specific instance but are you aware that you can use a Change Attribute and then flip an actor Vertically or Horizontally by accessing their Graphics Attributes in t

Hello @artsoils you can find a description of each in The Cookbook; also there's info about each type of attribute in the official GSC manual http://gamesalad.com/manuals

OK, you'll need Rand for the position, but then your wild number is just what it is, without any random? Then just ignore the line Change Attribute W to random(1,9)

I actually not understanding the first bit though the rest I do. Why am I changing the attribute W to random(1-9)?

-- your way of putting your 5 numbers into 5 integer attributes, I've called them PosA, PosB, etc.

You say each number is an attribute - are you needing to perform any kind of maths on them, or are you using strings to accommodate the wilds?

Rule: When Attribute Job ≠ 1Destroy

@wanegroup‌ I had the exact same problem and realised that you can't save a boolean attribute... It will never save/load it resulting in that your app will never figure out that the user bought an IAP

number in your rows. Each iteration, change an attribute(the one in your loop condition) to +1 and plug it into a table cell Value to check the next row. You'll also want to add +1 to an attribute th

creat an interger attribute (switch) in game 1, 2, 3, 4 as job 1, 2, 3, 4