now. Although you may have to do something like constrain self.position.y to self.start.y+scene.camera.origin.y and leave the layer scrollable. Cause anything you spawn in an un-scrollable layer will

Sounds like you need a constrain attribute. Constrain the movement of the camera to the player. That way, wherever the player goes, the camera will follow.

If you have just one sticky actor, then the other actors can constrain their position, relative to the point of collision.

...but that's like five constraints...

Hopefully, you have attributes that tell if you are facing left or right...

You could also constrain an invisible actor to the main hero... the actor would stick out a little bit ahead of the main actor.

Hopefully, you have attributes that tell if you are facing left or right...

Heh, it looks like there's someone else waiting for the device.time game attribute (Image)

Heh, it looks like there's someone else waiting for the device.time attribute (Image)

Create an attribute - Follow camera - Boolean - False.

Would it be a Game Attribute? A boolean?

constrain linear X,Y to 0

(change attribute)

As mentioned before, eight large images is a danger. The game will likely load slowly, unless you use the change attribute - self.image trick. Also, the game might lag or crash... unless you're just b

Make an attribute for the target value, then interpolate to that value.

(change attribute)

Then I tried using timers and a variable attribute changing from 1 to 0, and rotate behaviour clockwise when it's at 1 and counterclockwise when it's at 0. This time the problem is; it rotates once in

If i use change attribute score = score+1 : everything is going fine

is the attribute a real attribute? it has to be cause interger attributes dont reconize decimal places

So do you see whats wrong with my code then? =/ the part that changes the attribute every 2 seconds is before the timer that uses it, I guess I could kill the actor and then respawn it but that is a p