A change attribute behaviour only triggers once, placing it inside a 'for' timer will have no effect on it.

Change attribute.X to random (1,5)

Another way that could work (you could run into issues), is have game.highscore and save it to game.level. Then load attribute game.level

So..I created a game attribute called 'sprite-speed' and gave it '95' as the value. If mouse overlaps or collides with 'x' then change attribute 'sprite-speed' to '50' for 15 seconds, after 15 seconds

(Quote)

Actor 1: Its main objective is to change its Y attribute + 32 pixels, every 0.2 seconds, and to continue forever.

movement actor shouldnt be allowed to change its attribute to exist inbetween them' . . what is a movement actor ? You've not previously explained what a movement actor is, not even mentioned it, and

is there anyway though to not allow my character to go in between the rocks? The whole area of each rock is 4 collision walls, and the movement actor shouldnt be allowed to change its attribute to exi

change attribute self position -to- self position +32

No, it shouldn't effect how collisions work.

Its very fast though, considering i'm changing attribute every 0.2 seconds while left is true.

Best way imo is to do a constrain in one of your score actors…if score > high score constrain high score to score, then you won't need to change high score to score to save and it will update i

"timer every 0.2 seconds - change attribute self.position.y to self.position.y+32".

Attribute: Game.Score > game.High Score

I save attribute gold to key gold.

save attribute : game.gold //// key : gold

@sawkastee‌ Theres a lot of rules and constraint happening. But I constrain the main actors position X to '5*(game.player X - self.position X), same for Y. Then on my invisible moving actor, everytime

Information within layers permeates upwards - so imagine you have 12 layers (either 12 actual named layers or simply 12 actors in the scene) - starting with 1 at the bottom going upwards to 12 at the

Are you able to create an integer attribute called game.lifeBar with a starting value of... say 3?

@gyroscope is suggesting that you use an attribute to keep track of the actor count. It wont matter whether that attribute's value is 5 or 10,000. It's still just a single attribute which uses next