Also I dont think the actor that contained the attribute was the prototype. It was an instance of the rototype in a scene. so I just deleted it and started fresh. hope this helps anyone having wierd s

Using Change Attribute gives you a little more control over when the RAM gets allocated.

----Change Attribute: self.currentText To: (self.currentText + 1)%2

----Change Attribute: self.currentText To: self.currentText + 1

What I ended up doing, and this seems to work, is when you click, I set an attribute to 1, and rotate to the position. When the angular velocity is 0, and fire is 1, I spawn the bullet, and set fire b

----Change Attribute: self.currentText To: self.currentText + 1

Global attributes needed: game.text_to_display

I created and attribute game.myName yet when I try to assign a concatenated string to it <char1>..<char2>..<char3> it only displays the first character. thus

Use rotate to angle to orient the actor (and set the target angle attribute). Then have a rule that tracks the actor's rotation compared to the target angle. Once those are equal...execute a boolean

then i created a new rule but changed it to attribute and then i chose game.left is true and game.right is false

then i created a new rule but changed it to attribute and then i chose game.left is true and game.right is false

Now during the game if you change B' tag attribute to "bomb" --> A will not be destroyed

This only works for tap zones (like a button) and not for collisions. For collisions...The other solutions work best.

create an invisible actor with alpha set as 0 at size 64 wide, then constrain it's x and y position to your original actor. Then set the colision rules with the invisible actor and not the main one.

if both actor isn't spawn at scene, you can check other attribute under current scene> layer>actor name.

If there is a collision, reset a game.attribute to 0 (you will use this attribute as a counter). In the "otherwise" condition constrain game.attribute=game.attribute+1. When it gets

You can't refer to another actor. You need to use a game attribute (aka global).

You may need to first constrain the X and Y position to a game attribute. Then tie a separate camera controller actor to the game attributes.

I was planning to have an attribute called CurrentLevel, and an actor that loads all the attributes for that level and sets everything up.

Use the Change Attribute behavior.