You don't need a global game attribute because it is all confined within the moving actor.

Would I have to add a global game attribute? Or should I be able to go straight in and apply these rules?

I don't THINK you need a rule. You should be able to just drag over the constrain attribute & set it to whatever you want. That should work. The less rules you have the better. (For optimizati

So I basically, under the actor prototype, created a rule, and said, if an attribute changes, self position y is greater than 1, AND self position y is less than 0, then constrain attribute, self pos

I would think you would just constrain the Y axis to whatever you wanted it to stay at. That way it could not go up & down.

I'm assuming you would use the constrain attribute, but I just wanted to clarify

You can only have one actor controlling the camera at a time. All that means is that if your actor starts hitting the border of your camera controlling area, the camera will be moved along with it. T

5. Now here is the creative part. Edit the actor INSTANCE. Instead of constraining 'OffsetX' and 'OffsetY' to 0, constrain them to the Camera.Origin X and Y, respectively. You will find this under 'Cu

And, on a related note, are actor collisions and events constrained to the outline of a rectangle, polygon, or actual pixels? As a recent convert from Windows to Mac, I'm realizing I have to actually

An actor can only affect itself or a Game Attribute. This may seem odd at first, but once you understand the concept you realize the power/potential behind it. What are you trying to accomplish &a

event" rule and "Change Attribute" of another actor. However, in the Attribute Browser window that pop-ups, it only shows "Game," "Device,&q

Constrain the actors X and Y positions to the edge of the screen by using rules to check if the actor is beyond this and then moving the actor back on.

It would be a nice addition if Gamesalad came up with an attribute of some sort to loop the image over and over

Do I need to create an attribute to link Accelerometer.Z to player rotation?

You would just need to make a game attribute that, when true, each individual actor checks via a Rule then uses the Destroy behavior.

If I reverse the multiplier in the attribute change (from -0.1 to 0.1 and I flop the directional vector I do not get the reverse effect.

did you put a value larger than 0 on the gravity attribute? a good start is 300.

And another thing, when I put in attribute, when self position x is greater than 480, destroy actor, the birds won't spawn on part of the left side of the screen, but only come down on the right.

an attribute changes: self.position.X is less than 0

Yes I've added the "bounce" attribute as well to both the birds and the actor