(Quote)

Use the save attribute and save the number of lives just before the reset scene behavior. When the new scene starts use the lives saved and assign to whatever attribute that keeps track of your lives.

(Quote)

OK, but Im not prompted to log in at all so i can't sandbox test it. The only rule that fires is my change attribute. Nothing gets updated in the tables since Im not able to log in.

You could also add a boolean attribute to your game called loggedIn and set up a rule like this:

My game starts with pause.attribute (integer) = 0

I'm not 100% what the question means ? There's no special code really, It's just a technique, just the usual stuff, the constrain behaviour and the replicate behaviour get used a lot, but it honestly

I have an integer game attribute called health which is set to 100. When the bullet collides or overlaps with the enemy it reduces the health attribute by 25. I then have a rule set in Enemy 1's proto

Are you using self attributes to count the hits or a game level attribute? Each enemy should be counting the hits it takes to a self attribute.

Make 2 self attributes "real type"

do not check them. Also make sure you use a constrain on all velocity. Motion linear velocity x,y and angular to zero. Also do you have fixed rotation checked in the actor? Post the code so we can sp

Make a self.attribute (an integer attribute will do here), let's call it 'counter'.

im quite confused with the new IAP table. Am I going to useTable Cell value ? How am i going to use it for non consumable to apply in an attribute like 500 coins?

Then create a rule in the action button that says when touched or a key is pressed, Attribute Action_Button_Pressed is true, otherwise it's false.

When you press on the left-hand actor, it changes a game attribute (game.Pressing) to TRUE. When you stop pressing on the actor, it changes that game attribute back to FALSE.

Gate Position = 0 Rule: When action button pressed is true, Rotate to angle 60 relative to scene, run to completion, stops on destination Change attribute Gate Position to 1 Gate Position = 1 Ru

Another couple of things occurred to me, firstly the way this vector-isometric set up works means you have an enormous amount of control over collisions, you can - with certain caveats - have a kind o

not really because you could just have a change attribute that says "change positionX to positionX + offset or offset/2" and they would move same distance. or not move them at all. I

I have attached an example for you. GameSalad indexes the scenes in the order you place them from 1, 2, 3, ect to the maximum number of scenes in your project. You can't access this attribute if you c

Although I did make some game.attributes for the controls, but to be honest it was very thrown together, made up as I went along, in hindsight it could be much much more efficient, for example for the