"I tried to track both touch 1 and touch 2's x position and display it (as well as constrain it, but thats not important, getting a value is all that is necessary). Touch 1's x position upda

Create a self integer attribute called health (3)

Make a game attribute called lives. Set it to 3 or however many lives you want to have

Yep thats how i would do it. Make it a self attribute in the object you want to spawn. Change self attribute randomPoint to random(1,4)

Basically i was wondering how to spawn an actor from any of the 4 spawn points i have set up. The 4 spawn points are 4 actors dotted around(named spawn1-4). Im guessing its having a game attribute c

have a rule when attribute self.position.y is less then or equal to zero

I needed to change my 'self.angle' attribute to a real number not an 'angle' as it seems if its an angle you are limited to 0 to 360 and can't have negative numbers.

This is a rundown of how to create and use a random number generator. The example given is for spawning, but you could change that to an attribute that allows your random actor to move. Read it over a

Well you can have one attribute and change that to random(1,2)

have the images initially be white boxes. Just change attribute self.image to imagename.png

Okay, I got part of it. If I use this Constrain Attribute Behavior (the second box (To:) says: vectortoangle(game.mouseposition.x , game.mouseposition.y).

How exactly do I do the first constrain attribute behavior? I am confused as to how I would enter two mouse coordinates and a VectorToAngle in one Constrain Attribute behavior. Is it possible that you

its a mystery to me.... is there some sort of maximum value to a integer attribute??

Use DeepBlueApps as they have created software called Attribute which lets you do all of the above! You could also maybe jot them down in a notebook to save some money!

graphics to ipad resolution,and reset all your collisions spawn positions everything,or you can buy Utopian Games project resizer head on over to their website

Constrain Attribute: vectorToAngle(game.Mouse.Position.X-self.Position.X , game.Mouse.Position.Y-self.Position.Y)

To be honest not to sure. But another work around is to constrain another actor to your ball, have it behind the ball, and have the particles out of that 2nd actor . That way they will be behind like

To be honest not to sure. But another work around is to constrain another actor to your ball, have it behind the ball, and have the particles out of that 2nd actor . That way they will be behind like

In the prototype, make two new attributes:

Give each dot a seperate x and y coordinate game attribute, for instance