hmmm.... is it at least rotating when you use the constrain attribute method?

Constrain Attribute: self.Rotation To: vectorToAngle( game.Origin.X - self.Position.X , game.Origin.Y - self.Position.Y )

are you constraining the rotation attribute?

I have an object that has a limited amount of "hit points". Everytime it collides with objects i need it to subtract 1 point. The problem is, sometimes it subtracts 3 points or 7 poi

Create an attribute self.Threshold with a default value of 2.

Don't use a a constrain attribute on an attribute if it isn't going to change.

ok that attribute is going to be real or integer

Oh right, just constrain a self. attribute to that equation then use if attribute self.attribute < 2

nope what im asking is how do i put " magnitude(linVelX,linVelY) < 2" in a rule if besides the attribute appears just an attribute browser not an expresion editor

The textbook way is easier and more efficient. You don't need to create an extra attribute just for a percent sign.

The textbook way is easier and more efficient. You don't need to create an extra attribute just for a percent sign.

game.Attribute.."%"

If you're trying to add rules from the attribute window, it won't work. They are two separate things.

I can use any of the condition you guys give me cause i cant edit the expression bisides the attributes rule...

to explain better in the rules beside the attribute opens and attribute browser not and expression editor if you guys have any other way to do it please let me know

hey there I cant use any of those as a rule cause the software doesn't let me edit the attribute condition, so i can put one condition but not and expression.. how you guys do it?

Movable puts them in th physics engine. A lot more overhead. If they are simply moving in a strait line turn off movable and use interpolate. Or constrain position x to some function of time.

I have found that Collisions don't work well (or even at all) with interpolate. So the question is "do you need physics for this game?"

when the comp shoot that attribute comp_turn goes to 1 so its my turn now

sorry guys... ok when i shoot i set an attribute cmpu_turn to 0 and then when object.motion.linearvelocity.x=0 and object.motion.linearvelocity.y=0 the comp its suppose to shoot that guaranties that