However, although now i cannot destroy it again... it's as if the HP attribute isn't working... or i am missing something retarded...

Lets say i have 1 ball actor and i add a self attribute called randomBall which is an integer. Then i have a global attributes called balltarget (which integer as well) and it's being randomize by oth

and Weapon is equipped, (I'm guessing this is an attribute here)

Change Attribute: Self.HP to Self.HP-1

Ok you dont need a game and a self attribute. Just make a self attribute in the enemey

So currently, i have HP as an integer attribute in the game tab, .... it's set to 1. The actor it'self has an HP integer set to 1...

How do i give an actor and HP attribute, and then use something like a sword to remove HP?

1) Images that depend on "change attribute> image" to cycle through images in the project file using rules appear to turn to white the moment the "unpause behavior&am

if I have the change velocity on 1 actor (a game controller actor for example), and the change attribute on a different actor.

Just done some more testing. It's deffo not right. Even though a display text will show the attribute to be whatever your rules are telling it to be, it actually only uses whatever it's physically set

@Sparky it depends which comes first in the actor the change attribute or the change velocity.

Create a game level attribute called "movespeed"

Maybe try changing the order in which it executes. Change the score first, then play sound, then interpolate actor off the screen, then save attribute.

Quick question: I already have within each actor a boolean attribute that automatically changes the actor to "false",...then when it's touched, it animates and then turns it to &

Put a rule in actor three that say something like change attribute game.invisible to game.invisible+1

when actor is pressed, change attribute to random spawn (1,6)

The way I would do it would be to set up 4 attributes, and after a random number is selected, mark the associated attribute as used and then when the next random number is picked, do a check to see if

It will if you reduce the speed. Constraining an actor to self position can be done with a change attribute (not in rule) at the beginning of a scene so it stores it's current position to a self attri

and action happening. Or you could have a constrained actor with an overlay animation for the arm.

".." is a powerful little trick. It lets you place attributes into the middle of file names.