couple of ideas .. you could write a rule to determine direction of motion of your black actor and create an attribute to set if moving left then attribute =1, then put in your blue actor if overlap

Okay figured it out i think... got 3 directions working left up and down ... right is wonky... Well i thought i tried this earlier but think i used self.poistion.x by accident ... vectorToAngle( se

in the actor that has the collision rule make an attribute - Boolean and call it "collided" -set to false

the hits by 1 ). I however, want the hits attribute to increment only when both of them collide in the air. Also, if I purposefully fire actor B towards a previously "grounded" act

game. The frame rate drops and things that have collisions do not work the way they should any more... however at least i know my game does not crash after running for several days back to back..

it if it doesn't work. then you want to make a constrain actor.rotation to (put vectortoangle formula). now all you have to do is make your actor rotate to the touch position. and perform a rule say

Could you set up as many attributes as you have keys in your calculator (10 if you are doing 0-9). Also create an attribute as keyPressCounter=0.

can just make global attributes for the 2 then constrain the attributes to there self rotation. So when actor1rotation= 180 and actor 2 rotation= 180 with all conditions valid, you should be able to

not sure if im understanding what your tring to do. You can put a invisible actor just along the top of the platform and not on the sides. then when the player collides with that actor change a attibu

Make game attribute, game.Centered = Boollean.

Try change attribute to Random(100,500)

i guess from that point have an attribute modified to 7, and when it is, record that with a 'change attribute' to and use the rand option and i think you can put the 2 numbers 350-400 inside the brack

without resetting every Attribute?

if attribute game.mynumber > 350

Should be easy. I want to constrain or change, whichever is proper, a number to an attribute from a range of numbers.

without resetting every Attribute?

You can take out the touch inside rules and have it when touch is pressed. Also make it when touch is pressed change attribute to 1 and when touch is released change attribute to 0. you dont have to

I have a crosshair on screen used for aiming. I need it to move left and right, and ONLY left and right (not up and down). I have a left arrow, and a right arrow to do so. When each is pressed, I have

So, what I want to do is spawn tiny little white stars onto the screen as long an attribute called "Create Stars" is equal to true. Therefore the rule I set is:

what you would have to do is make 2 real attributes, call them actor1x and actor1y. Then make a interger attribute and call it switch. In the first actor you want to start out onscreen constrain attr