You must have a rule saying why and when an actor gets destroyed. Add a boolean game.attribute.ActorDestroyed that turns to true when this rule's conditions are valid and put it above the [Destroy]-li

Another way to think of this is to create an attribute in each actor called something like self.ID and manually change each actor's attribute value to a sequential value (1.. 2.. 3.. all the way up to

I found out that I was wrong. In a rule, not in the elses, put when a key right and left is up, change attribute x to 0. That's it! (Image)

I changed the attribute to linear velocity x -500 and 500 for right and left https://imgur.com/a/Rs9d904

The problem with a "real" tower defence game, is not the path, or the fact of shooting bullets, it is the problem of not having all of the turrets aim at the same game attribute. (X,

Accelerate to the left and right will involve slowing down and speeding up, which may be your problem. (I don't really know.) I just use, almost all the time, change attribute, then change self.linea

The first code I was using: if attribute "contains" "iP" was only covering my iPad-mini and iPhone (but App Store seems to test apps on normal iPads, which I don't

Attribute/device/platform/name "contains:" iP

For example is you have multiple move to's triggering without run to completion on for the same actor, and/or have a change attribute self.X you will likely get odd behaviour and unresponsive controls

for each variation, at the start of your game, have an integer attribute called "device type" and an actor that is on your first scene that determines your screen size, based on the

If you just want to spawn 1 main actor you could also use an Attribute starting at 0. When you spawn the main actor set this Attribute to 1 and in your spawning behaviors check the value of the Attrib

Constrain all enemmy's x and y coordinates to game attributes. Then add in your rule saying that if you press, and is not touching any of those attributes, spawn main actor. And of course say that whe

When attribute = ______

sorry, I think my question was not well asked. I know the magnitude and vectorToAngle. I just want to know now that all my attribute is meet how can I have my enemy keep on attacking my player. punch,

what attribute or other action can I do to have my enmy keep on punching or kicking my player? btw that attribute is distanceToPlayer and vector

I think of attribute names as reserved words so they don't need to be in quotation marks. Also make you aren't typing in the name of the attribute... that won't work. You have to select them from the

Ah, when using a text attribute in tableSearch, it doesn't have to be inside quotation marks.

There is a behavior called Log Debugging Statement. It allows you to display any expression (e.g. an attribute, a text string, etc.) within a rule. You view the Debugger Window and then watch as the v

You can use a text attribute for the search string.

So I've been making a simple game to get me started on GameSalad and I'm starting to get the hang of the Tables and attributes, but I'm running into something that I can't seem to fix by myself.