change attribute game.health to game.health -1

@Zwire You can do this with 2 actors first create a game integer attribute Health set it to 3 ( 3 hearts)

should follow it. I can do vector to angle to constrain the rotation of the black circle to the red circle , but i don't know how to move the black circle towards the direction of the red circle.Can

Here's how you'd trace out an arc in an isometric (1:1.72) view, give your player 3 new 'real' attributes. A, Tx and Ty.

Yes all attributes I described are global. You need to carry that attribute value to the next scene.

Change an attribute (e.g. game.questionNumber) to random(1,tableRowCount(tableName)).

Then attribute integer.

the block wouldnt require gravity and it wont move so set its moveable attribute to false.

change attribute

(Quote)

Maybe you might have more luck now that we have custom collisions?

I would use custom collisions. you can trace a custom collision area for both the ring and net. Using this method you could trace the two sides of the net and leave the top and bottom open. Same with

Controls will reset when you change scene. So I would make a global attribute "Keep moving" boolean

its ok i fixed with constrain

There is no need for the timer in the jump rule just put change attribute instead of a constrain in a timer , and put the accelerate behavior at the top and set its direction to 270 ( down) so it wil

@sonicm3 Just to explain sorry , You have to keep in mind , self attributes restart when the scene changes but game attributes don't, thats why you see it resets every time you go into a new scene ca

When right is pressed change attribute game.facing to true.

Your right but from my experience with side scrolling games in particular, constraining motion velocity is better than change attribute cause of the jump issue , it doesn't allow you to jump forward

if right and left are up , motion linear velocity = 0 otherwise 2 rules ( if right is down constrain motion linear velocity to +180 ) ( if left is down constrain motion linear velocity x to -180 )

You don't really need to constrain linear velocity to a value, once you give an actor a linear velocity it will move by itself from then on at the speed you specified . . . so most times you can use a