Yeah, but it tends to overshoot the direction it is supposed to aim towards and starts going back and forth, but my fix for the transparent area problem is hinged on it stopping. In addition if I rota

Try this for staggered movement. Make two new attributes in the moving actor, they can be named anything, but I will call them LocX and LocY. When the actor is created, set LocX equal to the actor's h

Yes. You just need to use Constrain Attribute on the actor's X/Y position and set the value to the Mouse X/Y position.

I would try making a boolean attribute that changes when you shoot. And with the rule checking if the move button is pushed down, also add the condition if the shooting attribute is false.

If you want to eliminate any diagonal movement you can use the Move behavior and set the attribute to 'stacked' instead of 'additive'. Then you don't have to use all those extra rules that seem to be

(I did play around with changing the collision attribute in the PLAYER instead, but could not get this to work.)

Right now you would need to use Change Attribute behaviors for each attribute that needs to be reset

The wording may be incorrect,but not sure how to word it. Though of course the self.color.alpha needs to be selected as an attribute, but the rest can be typed in manually.

lets see... ok, when the life attribute reaches "0" I have the game change the scene to the Title Screen. I am able to change the Life attribute back to full, and the PLAYER will spa

So... it looks like I can reset all my integers with Change Attributes like; score, shield and life however, any Spawned or placed Actors can not be changed or reset after it has been run once. (as fa

Rule: When any conditions are valid: An attribute changes game.player.life equals 0 then Destroy this Actor

Is there a simply way of reseting ALL attributes at once instead of changing each and every attribute separately?

I'm also not aware of the staggered movement you speak of. Do you mean like in the way on a checkers board where you jump from square to square? If so, then I would using Change Attribute on the posit

3. Created a Change Attribute: self.randomInt to random(0,100)

I created an actor attribute that holds an integer. (RandomInt)

An attribute changes: game.Time equals random(0,5)

road actor. It might also because I put those constrain attributes in my car actor instead of my road actor. Another thing might be that I had way too many actors at once, like those boxes, but it co

1) To have one actor be able to follow another actor, the target actor will need to constrain its position attributes to game(global) attributes so other actors can go to that position.

Its set to one, which should be the same as true for a boolean attribute, right?

Did you set the attribute to "true" or "1"? I think I had a similar problem, but it was because I set the bool using ChangeAttribute to "1" inste