So i'm using the accelerometer to control the actor moving left and right across the screen and trying to use constrain position to limit the movement from going offscreen.

Any ideas? I've tried timers and a boolean attribute that turns on/off with 2 touch.

I created an attribute(ActorAngle). When the game starts I save the actor angle(self.Rotation) to ActorAngle attribute.

* Actors have a self.Rotation attribute. You can store this value in another attribute that you create (use attribute type angle) and then compare it to the current rotation value.

* I have an attribute called difficulty. So I have:

I've made a rule for a group of actors that says that if they collide with another actor, they will change an integer attribute to a random value from 1 through 8, which will determine which actor get

However many times you want the player to tap on your object, you just input the number in your touch count attribute, then go into your result, (mine was a coin) and type the number of the touch coun

(Quote)

Make a weapon integer attribute.

It is best to avoid using the constrain behavior on any actor attribute that is involved with physics. It seems to me that constrains should only be used for attributes which only secondarily play in

(Quote)

(Quote)

Hmm..... it seems that the constrain behavior does not (yet) play fair with the new center of mass system.

(Quote)

Constrain: self.rotation to: (111sin( *44))+(66cos( 27))+(221sin( 33))+(111cos( 34)+66)+(33cos( 211)-22)+(112sin( *33)+180)

conditions. The thing about seperate rules is if collisions happen during that cycle the odds of another rule being next in the cycle increases the likely hood of it being registered. It all comes do

not a loading issue. Timers? Maybe a every x attribute you are doing a save function? There are certain things that cause lag issues. I am not absolutely sure.

Change Attribute Health to Health -1.

Yes it is the tinkering with the constrain actor behavior in order to get it looking realistic that I'm dreading hah.

Edit: No this was the wrong one too. You'll get the idea, though. Just a redundant attribute being used.