There's no need for a separate attribute... yes, you can use an integer such as 10 to add to the value.

is game.ManaToAdd an attribute or is it like min(100,game.ManaBar+10) ?

     change attribute game.CurrentManaAmount to min(100,game.currentManaAmount+game.ManaToAdd)

@PixelGaming - Hi guys - simply use the following function in the expression editor in a change attribute etc, behaviour:-

(Quote)

You can do this for any boolean attribute. 1 = true. 0 = false.

The easiest way is to use the Keyboard Input behavior and check the value of the attribute that you use in it.

I was running a lot of actors with quite a few Constrain behaviours in each one, and found that I could keep the frame rate happily at 60fps when using self.attributes, whereas with game.attributes t

Also, obviously you can use calculations to work out which square of the board you're on, but alternatively, if you used the same custom colliders on the board pieces too, and each board had it's own

     Change Attribute self.CurrentWheelColor to mod(self.CurrentWheelColor,5)+1

okay I did that, and it's fantastic method, but how can I let the color of the ball matches the colors of the wheel !! sorry , but I'm new to GS, and by the way there is something wrong with the codin

Change Attribute self.CurrentWheelColor to mod(self.CurrentWheelColor,5)+1

This is what I used and it's not working.

That's how I see an 'Every 0 seconds' Timer too, basically a poor man's Constrain behaviour, in fact it's not even as good as a Constrain behaviour in that it only fires once every two frames (30fps),

In the Wheel actor, you're changing self.Image to self.CurrentWheelColor+1 and since that attribute has a random value from 1 to 5, self.Image is going to be 2, 3, 4, 5, or 6. The reason you're getti

Yes. You can fix the position of an actor using constrain attributes. You will need two self real attributes to track the position of the actor constantly and the reference those positions when you wa

First make a tag for all your squares, call them squares then add a self Boolean attribute to the square actors call it can snap.

(Quote)

make an integer game attribute 'death' and a new actor containing the splash animation; then create a rule in your character that when colliding with the 'water' actor, change game.death to 1; make a

Try ticking better collisions (might work) and make sure the actor is locked on both scenes