I would simply have an actor attribute called ClickCount. It does not have to be game attribute. Then just add to it.

Attribute game.killEnemy=0.0

Attribute game.killEnemy=0.0

Make an Attribute called Clicks (or whatever)

I am making a game in college and a part of my game you have to click an enemy 10 times to destroy it. I have tried some of your tips but it still destroys after the first click. I have an attribute f

change attribute: 'game.coinCount' to: prec(game.coinCount, 2)+0.01

UPDATE: Still happening when attribute is changed before destroy.

The only thing I can imagine is that you're getting a glitch because you're trying to change an attribute AFTER destroying the actor. Move the destroy actor below and see if that fixes it. I've cert

change attribute game.coincount to game.coincount+1

change attribute: 'game.coinCount' to: 'game.coinCount'+0.01

Will Async multiplayer basically be like an attribute that is stored in the cloud? Something like that would be awesome.

Create a real attribute and call it Time along with a boolean called dead

Rule: attribute game.lifeB <= 0

Rule: attribute game.lifeB <= 0

Found this little gem on youtube on how to make your very own Load/Save high score attribute for those who need a little help.

I wanted to use the distance'from attribute to let it only destroy itself if it had reach a certain distance and indeed technically graphically somewaht overlap the target ghost actor and only have th

Adding a Device Type attribute should be a snap when can we have that?

=> change attribute game.start TO true

then just use a change attribute for self.image to game.timeremaining..".png" and it will change automatically....

For me personally I like to avoid unnecessary behaviours, attribute, rules and so on - so in this case I'd dump the attributes and the constrain behaviours and simply have the bomb spawn the collision