Couldn't you just use an attribute (game.life) is true - animation blah blah.

You were right Tshirtbooth. In the camera's constrain attribute for Motion.LinearVelocity.X, it needs to be

Or use the angle to change the radius. For example constrain game.radius to angle

Ad a constraint attribute. Constrain the self.angle to vectortoangle(self.velocityX,selfvelocityY). I am on my iPhone so I could have some errors in the syntax.

check out gshelper.com ... there is a all your levels in one scene tutorial by tshirt booth ... might help using tables etc. ... alternatively you could create a integer rule in the prototype of the s

changeAttribute: self.Motion.Linear Velocity.X To: 100

First create 2 real game attribute for your character's x & y. (ex. characterX , characterY)

I'm trying to do it now and I'm putting a collision rule onto the bomb for when my player character touches it. Then I added a constrain attribute - self position x,y but i cant seem figure out how t

But still my problem is how to create multiple energy bar above the actor? do I need to create new constrain x and y for each of the spawn actors? I was thinking about the table to write the values th

add an attribute Index type … name: myLives … set to the number/amount of lives (5 ???)

You constrain the second guy's position X to this formula:

Create a self attribute - boolean - call it "im touched"

Change attribute Camera Origin to Y

Change attribute Camera Origin to Y

Change attribute Camera Origin to Y

@P-O-M .... WOW! That demo is great. You nailed all five criteria that were packed into the original question. And you did it with easy to understand attribute names and with very easy to grasp equat

Basically on my newest game idea I have to have attributes that rely on each other for math. I wish to know if it is possible to reference two separate integers from a table and subtract one from the

perhaps a gameAttribute boolean collided and leave it false

@ImGus … the numerical attribute types set the form of the number when stored … therefore the type you chose allocates a bit/byte allotment for that attribute

Attributes: