I can't make it work. How can I put the "self.randomX" or "self.randomY"??? everytime I write it down at the change attribute it changes to "game.randomX&

Rankings didn't improve that much with the price drop, in most places they were down. I would attribute most of this to the fact that as time progresses of course it will decline. Again, you can't tel

In the actor, create two integer attributes: randomX and randomY

There are no collisions or anything on them (Image)

I will test TOXIC ROACH tomorrow (heading to bed now). I will remove collisions and see what happens.

Well the test seems to confirm the memory leak is in collisions.

I made a quick test with my mouse avoidance demo on my wall (which uses 210 Constrain Attribute behaviors).

The test will be where I will leave all rules but remove all collisions and see how the memory plays out.

Here is a demo showing how to constrain the dragging region of an actor to a circular area:

Wherever you are increasing the score, just add a Save Attribute behavior after that.

Hmm... this isn't working. o__o" I have the Move behavior on the background, and I dragged a Rule in with an Attribute that says what you wrote, reddotinc, and set the Game Over Rule so that

out how to save is to use an actor with a save attribute and when clicked on it, it saves. How do you save automatically?

One thing in my game I do have a lot of collisions. You said you have none, that might be something to look at in tests as well.

Now, is there some sort of work around to get it running at the exact speeds across all models of iPhones? Too bad there is no option for "if on iPhone 4 - then apply this attribute"

I had an attribute for the explosion and I just turned off the explosion attribute on the reset button hehe.

.....constrain height to width

Hmm are you saying setup an attribute for the Reset button and actors with the animation that if pressed, change animation to 0?

Even with something like a: ifAllMotionStopped attribute is set to false it still replays stuff like this and doesn't truly reset.

What I would do is have an angle attribute called self.shootAngle and a boolean called self.shoot

You add these by having your scene visible and clicking on the centre tab 'attributes' on the sidebar which shows all your actors. This is a global variable you're adding.