Try creating a real attribute called cameraX (or something like that)

It currently sets an attribute called musicVolume, just change that to ActorX, or whatever

if i constrain the self position of the actor to slider (position-68)*3.9506 "cause the slider minimum position is 69" it wont work.

Oh you magical genius! I was close when I had added a camX type attribute onto game but missed that you can add the game and mouse position to the constraint. You get a cred if I finish this game - wh

I would suggest having two global game attributes (real) called PlayerX and PlayerY.

you would need to set up a global game attribute for each one i guess...

In the actor, you need to add an attribute ( boolean) called, let's say, "pleaseAnimate" and check its checkbox.

on (I think). If I change that to a new game attribute of real 1000 the triangle will move across the width - but of course the full width each time so not a solution but getting close.

Oh, you know why? Because it's going to the mouse position. I bet the mouse position is always between 0 and the screen width or height. Try constraining an actor to the mouse and using that actor's c

You need a global game attribute (real) called musicVolume.

You can have global attribute called "Controls". (set it to integer)

I haven't tried it, but you might be able to make a global game attribute for "bounciness".

If a movable ball with a collide attribute is set to a restitution of 1, it will bounce on the specified non movable actor without losing energy. That happens no matter what the restitution is of the

I would create two invisible actors and constrain them to either side of the main actor. Use these actors for collisions and not the main actor.

They way I see it, all you would need is a 'save for next time' checkbox for each attribute.

Check if the enemies are on the correct side by using the self.Position.X and Self.Postion.Y attributes...

The best way, I think, is to have a global game attribute (boolean) called "busy", or something like that.

I was wondering about how far the text attributes could be 'pushed'.

When I have my character moving with d pad like buttons, other objects bounce off of it like I expect. Then I switch to a constrain to touch rule so that the character is moved using your finger and t

triggers I can find are based off of "attributes" and it seems "player input". At this point in the game, I don't want the player to have input anything yet, just