Funny, you and I did the same thing, but put the constraints/calculations on different objects.

I have just had a similar problem and fixed it by having an attribute called "allowjump"

First I create 2 real attributes:

The pad will be constrain to the Rotator position with the cos and sin formula and also it will have an Rotate To Angle to maintain its orientation.

For the interpolation thing, I really don't know that behaviour much. What's the difference between it and the constrain one?

Have a boolean attribute for every scene and call it like scene1Selected, scene2Selected, etc. Have them all false except for your first scene. Then somewhere in the random function have it check if

my jump. My jump function is based on an attribute that tells him when to jump when my button is pressed and when he is on the ground. I have tried making a rule where it corrects itself when my char

Constrain Attribute: self.Position.X To: 160*cos(self.Time*200%360)+240

Constrain the invisible actor's self position X and self position Y to the X and Y of your visible actor.

jstrahan - I am going to try that method out, my question is how do I constrain the "actor image" to the "invisible actor" when using constrain attribute since they

Using the move attribute makes my actor look a bit stiff. After my acceleration I just want the sliding after it to be less ongoing. When I accelerate too much a tend to slide about half my map distan

Make an invisible actor the size u want for collision put all rules in here then constrain real actor to the invisible actor with any offset to get in right position

Create two global game attributes, cameraX and cameraY

I wrote a game with custom collision detection tracking the player actor in relation to all the environment actors so that I would have more control over collisions. This seemed to work ok, except for

unticking physics > movable makes the platform unmovable via the physics behaviors (accelerate, rotate, etc) and the linear movement behaviors as well (Move, Move To) so you will have to do you

With a costrain attribute = self.position.y to given coordinate, the problem is solved, but the constrain attribute isn't really an FPS helper, and I have 4-5 platform onto screen at a time.

I have got quite a bit resolved though ... The 2 enemies no longer come straight at you when the scene starts. This was due to two attributes, one controlling the right, one controlling the left side

create an attribute, name it "change scene".

just use the 'Move' attribute. no sliding at all,

Get a integer attribute and set it to 10 and call it limit then go to your player and put in if player overlaps/collides or any other action