If you are talking about images that pop off the screen, I've seen it done but not aware of game salad games doing it. Because there is red and blue seperation as part of the image size I'm not sure

I had when attribute = 1

When I created the game attribute it was set to "0." This threw everything off. Thanks again TSB and CodeMonkey!

Well, anyway, basically I have a couple of states controlled by changing a attribute.

So here's the idea. The enemies spawn at the left part of the screen, they run to the right part (only X attribute needs to change, they're not going up), and when they reach a point near the right en

open the otherwise section of the "Rule: Determine which touch number is controlling" rule and remove the two change attribute behaviors.

So! you can make a Behaviors to read the scene.attribute, then add the Behaviors to Prototype, so the actor can read that scene attribute.

- Division per zero (ex: self.attribute / 0)

restitution to 0 (its in the attributes panel on the left in an attribute (under the physics tab)

The actor have these attributes:

Constrain self position x and y of the target equal to device mouse position x and y.

again" sign, and now the game.start=3 attribute.

I made the game.start and integer attribute. Is this correct? As soon as I move my move rules into the new game.start=1 rule, my actor no longer moves. Hmmm.

- I have an attribute called "MoveTo" that moves my actor, and it's set to "1."

2) So in my main actor I have a move rule. So am I creating a new rule (attribute: game.start=1) and then putting my current move rule into this newly created game.start rule? If so, it doesn't work.

capture the x and y position of the click using a change attribute behavior, store those values on two actor variables. move to the stored position.

constrain attribute: self.rotation = vectorToAngle(self.linearVelocityX, self.linearVelocityY)

that way collisions only happen if alpha is greater than 0, i.e. visible.

There is an attribute called visible I think that can be turned to false.

Put a rule in "actor_A" ------ when actor_A is touched change attribute "actor_B_exist" to "0".