You can only have 1 actor control the camera at a time. If you want 2 separate actors to have camera control ability...you need to have a game attribute to tell which actor to control the camera.

It's amazing what 1 single wrong attribute can do

I'm going to focus on games with less moving parts and definitely less constrain behaviors.

1. Use some game attribute to control all actors. [such as: Clear = 0]

change attribute: self.positionx to self.positionx+3;

What triggers the finish attribute?

i have a rule -when attribute "finish" is true

Looks like you are making it too difficult...just put the expression in the input box and save yourself the constrain attribute.

1. Created attribute inside the Actor name "RandomNumber".

Note: you can only have one thing controlling the camera at any given time...but you can have actors trade camera controlling roles by using some attribute switching.

I have a rule that says - when self.position.x < game.Enemy1X then change attribute game.wall to gamewall+1 Let's say this wall is Actor 1

Have an invisible round actor and constrain two game attributes to its X and Y. Then have a second actor with the image that is constrained to the two game attributes but with a Y offset.

The trouble with copying Rules is that the Attribute NAMES are just for our reference. This is why you can have more than one Attribute in an Actor with the same exact name. Each attribute name is tie

make 2 attributes in the Actor: originalY and originalX

towards the bug. Did you just use a change size attribute to get them to "stretch"?

When the touching stops, it's suppose to change the touch point to -100 for X & Y. The touch points often ignoring the Change Attribute part. I tried using a constrain instead, when the self j

You should be able to create an actor attribute (call it "TimeToGoUp" or something) and set it to one. Then in a rule, if "TimeToGoUp" is "1", th

They're supposed to go to -100 for X & Y, but I don't think that's happening. I was wondering if I should use constrain attribute, instead of change attribute. Yet, wouldn't that hurt performa

game.attribute Boolean called "Options"

* - the movement and rotation of the defense rings' 30 segments (3 constrain behaviors each and a handful of other constrain behaviors for the player and you are looking at over 100 constrain behavio