Everything solved!! Yes! EVERY load and save attribute behaviour "key" section MUST be filled directly! It is a common mistake as @gingagaming said in another post.

I deleted all Load Attribute behaviours for the Lives and that seems to have solved the problem but only for the Lives.

(Quote)

So, I'm just testing out some basic game ideas/tutorials, and every time I try to make an actor move with the up/down/left/right keys, nothing happens. They'll move when I add a Constrain Attribute, b

Change attribute

Constrain attribute: self.Rotation to vectorToAngle(self.PositionX – game.Mouse.Position.X, self.PostionY–game.Mouse.Postion.Y)

It doesn't matter if it's a consumable or not, the attribute is just the game's way of keeping track of it.

Are you using the load attribute behavior at the beginning of the game?

I have a problem saving an attribute in a Consumable:

What else should i do to make the first 'next level' attribute be 500??

(Quote)

Instead of making "Lives" as the IAPs, i made Coins for players to purchase with real money and then with those coins purchase the lives. The problem i cannot understand is why they

Have you tried wrapping the move behaviour inside a rule for eg if pause is false....move...so when you press pause change the game.attribute pause to true.

@tatiange my change attribute behaviors:

I also can't tell from your screenshot what your Change Attribute behaviors do.

Thanks, I'll give this a shot. Both ways seem great although I'm thinking using the constraining attribute may be a cleaner way to do it. Appreciate the information!

If you use walls, you'll need to make sure to uncheck "moveable" for the wall actors and set the bounciness attribute for the walking actor and the walls actors to 0. You can make t

(Quote)

Where is the callback attribute being checked?

-change attribute self.color red to 1.