Constrain Attribute: self.myReallyLongDistanceFormula To: sqrt((pow(( game.Mouse.Position.X - self.Position.X ),2)+pow(( game.Mouse.Position.Y - self.Position.Y ),2)))

If it is colliding with the same actor just in different spots (i.e. object 1 is in 3 spots) you can make an integer attribute in the ball and call it collide number. Then make a rule in the ball that

Definately a place for either at times. I did work out some cool work arounds to make interpolate be affected by collisions and stop on its paths at any given point.

In these cases I'd rather use a move to behavior as it's more fluid but they can be tricky to use in this way. Interpolate is a brute force move and renders things like collisions useless. I prefer mo

then a rule when attribute self.position.y < 174

Does anyone know a way around this? Maybe by simulating collisions with velocity changes instead of the built in collision?

I'm making an iPhone game and I want to know if any mouse attributes will translate to touches when I use it on iPhone. I use mouse position attribute to detect the position of the touch

stop. You've just said it's stops working when collisions happen

And the reason am using real for score instead of an integer is because my game is an endless runner game therefore I'm using the real attribute as a score as a way of displaying the distance travel.

Basically in my game I have a real attribute as a score and I also have an actor that if it the main actor collides with that actor, he dies and the game ends.

You definitely need to remove the game.collision = rule from the bombs and the exploding bomb actors. You don't need to set a game.Attribute to flag if it's collided

solution on the forum which was to create a game attribute boolean "collision" and set it to true on collision with hero. The when collision is true, run animation, destroy bomb an

constrain self.motion.lin.vel.x to 0

how do i make my attribute not able to go passed a certain number? i tried this but its not working.

Well.. I think I found a way but now once the monkeys changed their speed and path type, they dont revert back.. even trough I used "for" on the timer attribute and "run to

-change attribute: self.speed : random(100,200)

And to stop any one of them, use a change attribute on the boolean to set it to true. Hope that helps.

Hi, as you insinuated, it might have something to do with the timer changing the attribute... perhaps try change attribute to 0 in the spawned actor (so immediately its spawned, the attribute is reset

and hits the game performance to have to constrain 5 actors in each layer just to create the illusion of a change layer behavior. I Know you have many request, thats the only one i think is holding m

i think it will. but not wrap. try constrain to X. i was working on my project where i had a actor colliding with another and stopping there. thats what i wanted. but when i constrained it yo Y...the