Are you sure? I can't get my actors to recognise a right mouse click as a 2nd touch, nor does a right mouse click cause the touch count attribute to be 2.

In the same rules that destroy the actor, use "save attribute" and select from the list the attribute you want saved, and give it a unique tag name, and when the scene resets or chan

The "save attribute" behavior. You add that rule to the actor that triggers the event when you want to save the attribute.

If I have a game play and applying the attribute, the actor attributes are saved

Ok merging my rules and your int i can solve the problem, but i would like to know if i could make it with physical attribute.

game.attribute = game.attribute -1

Hey this didnt quite work for me what am i doing wrong? So i make an attribute with the value of 3,than have the rule of when N over laps or collides with E,Destroy.Than change attribute to game attr

`Attribute - Game, Scene, or Actor attributes contain values accessible by actors. An attribute holds data of a certain type. There are 6 data types that you can select from. Boolean - true/false v

create a game attribute integer values 3

make a interger attribute and call it itemscollected or whatever u want

and instead of all the rules just have change attribute self.image to "image"..random(1,5)..".png"

and instead of all the rules just have change attribute self.image to "image"..random(1,5)..".png"

change attribute 'game.randomimage to random(1,5)' (change the 5 depending on how many random images there are

change attribute 'game.randomimage to random(1,5)' (change the 5 depending on how many random images there are

You could try making some Game Attributes Like ActorNumber and collide number.

Is there a way to have the user enter information into an Actor Attribute?

But i also know you could constrain something to the actor.

you could have a attribute which every time you complete a level you save to and depending on the number depends on what level they are.

@NextGen what attribute do I have for interpolate?

i wonder (not being in any way programmer savvy) weather it wouldn't just be worth screwing the polygon collision and just going straight for per pixel collisions.... i saw some1 say something about G