Basically, create a global integer attribute named score. Then go into your ball actor and put in a new rule.

make a global attribute called score. Then ahve a rule when ball collides with block change attribute score to score+1. Then have a display text behavior to display attribute score in a actor to show

Make a global attribute g-ame.score and in the ball a rule like this:

you still needed to constrain the y or else it would still push down.

maybe try constrain maxspeed

make a rule when touch is pressed, then drag in 2 constrain attribute behaviors. Constrain self position x to devices mouse positiion x, and constrain self position y to devices mouse position y

But how is it possible to even rotate if I constrain its X and Y values? Wouldn't I "pin" the actor to a fixed position if I constrain its X,Y ?

but I can not constrain the X position, because the platform need to move left.

Constrain its X and Y positions to whatever you want those to be and make sure fixed rotation is unchecked. Then make it collide with those actors: it should dynamically spin without actually moving

drag a constrain attribute behavior in the actor. On the actor thats in the scene(not that same actor thats to the left in the actor pane) double click it. Then on the left go under position and right

I did the constrain in platform,but not work.

constrain self position y to the position it is onscreen

for say bullets offscreen, and make a boolean attribute, when true. change attribute bullets x position, to x on screen. same with y. then the bullet can take its course to the enemy, then once overl

create two attributes one Walk one Shoot, integers value 0. In walk button put rule when touch is pressed change attribute Walk to 1. In Shoot button rule when touch is pressed change attribute Shoot

for say bullets offscreen, and make a boolean attribute, when true. change attribute bullets x position, to x on screen. same with y. then the bullet can take its course to the enemy, then once overl

otherwise change attribute>background>position>x = 0

I've tried using the constrain attribute behaviour but that doesn't work.

I've thought about that attribute thing also and gave it a go...the thing is that you dont have a "When to set the attribute" factor. All the rules apply on actors and if i could say

I believe you will want to create an attribute for each moveable actor so you can do two checks in the rule ie: when mouse up and when attribute actor1Active=1 or whatever you call it. That way the mo

I started replacing my constrains and timers with the following: