If you use a timer, put the timer inside an attribute rule, if you are using a loop, simply put the attribute rule as the condition for the loop and set the condition to "While". Yo

round(attribute) will show no decimals. roundTo(attribute,decimals) will show the number you tell it to show, rounding up/down as needed. prec(attribute,decimals) will show the number of decimals you

I have an real attribute that tracks the time taken for the actor to reach point B from point A.

I have an attribute that counts the number of players remaining in the game ('notCommitted') and I tried adding an attribute to the actor ('MoveCounter') so that if notCommitted and MoveCounter weren'

"Change attribute game.on/off to (game.on/off+1)%2"

I'd assume it means that if the actor isn't being told to move, it will sleep and be removed from the physics calculations. Whenever the actor isn't being moved by the player or other actors it behave

the opposite direction. But when i set collision attribute it just bounces of and collides again and again in the same spot until the actor for border itself gives it a way off screen by flipping ove

Attribute self.FacingRight = true

When it comes to a constrain vs a loop, it's more of a usage difference than a performance one. Loops have many uses that constrains do not.

To make an actor point in the direction it is traveling, use a constrain behavior:

Your otherwise section is essentially saying: if 'switch On/Off' is false then change the image to the off image, but there is nothing in your rules that makes the attribute 'switch On/Off' false - an

--Constrain self.pos.x to self.pos.x +1

--Constrain self.pos.x to self.pos.x +1

(Quote)

(Quote)

Another method, using custom collisions. Might have already been suggested, I didn't check each one.

Constrain style to random

Sorry, another thing. When using the loops do you NEED a while constrain?

Funny enough I was asking Armelline about a similar thing just yesterday, comparing Loops to Constrain (both which fire once every code cycle / 60fps).

I just watched that video to see where you're at...it looks like it should work for you. You are doing the save and load attributes to store the high score, yes?