So with my limited knowledge, but trying to grasp this: I've setup a Rule and attribute..but then do I setup an interger? I was trying an Attribute like: game.BallCount > 5 then Destroy..but th

I will take a look at change attribute or constrain thanks!

Is there an easy work around so that I can still use the reset scene behavior to reset everything but keep the music going? Or do I have to use a bunch of change attribute behaviors to "manua

When an airplane spawns originally, constrain an invisible touch control actor above it. When the airplane's position is touched, the original airplane actor is destroyed and the invisible control act

Something else to consider is the tiling capabilities of the graphics attribute of each actor.

You would just have to constrain the rotation of the barrel to the angle of the line between the cannon base (pivot point of barrel) and the touch. "vectorToAngle()" can get you tha

sometimes the save and load attribute work. sometimes they don't. is this a viewer problem?

Constraining through game level attributes is the way it is usually done and easiest to setup/manage from scene to scene.

change attribute self.color.alpha to 1

I've been working on this for the past couple of day (too long, I know - I'm new). The only thing I've come up with is to constrain the position of one actor to another, with an offset. I'd actually l

You can also change the position with the "change attribute" or "constrain attribute" behaviors...they would contain "self.Position.X" or &quo

Isn't there a built-in attribute for max speed? What's wrong with that?

Make a rule then make a change attribute when whatever

i really don't think that different attribute types would have any real performance difference. I could be wrong, but as long as you're using the right type for the data you're storing, thats as much

Do any of you super-technical GS users have an idea how much memory/storage the different types of game attributes demand? As far as I know, "boolean" is the least-taxing, then &

constrain attribute: self.rotation to (vectorToAngle( self.Motion.Linear Velocity.X , self.Motion.Linear Velocity.Y ))-90

As for having the pression of the fire button stop the crosshair's movement. Create a game integer attribute called `stopcrosshair` or something.

Constrain the rotating actor's self.rotation to a game.angle attribute. Then, any time you need to see the actors angle, just reference the game.angle attribute that data is stored in.

Have an integer game attribute set to 0. Call it random (or anything you like!)

I remember there being a problem like this before... I forget why, but sometimes the collisions focuses around an actor's origin point. To make it tighter, hmmm...