constrain: self.Motion.Linear Velocity.X = 0.01*pow(1.012,(sceneheight-self.position.Y))

I think your doing it through a self attribute , instead do it as a game attribute so for example

----Constrain Angular Velocity to Angular Velocity+1

I'm want to constrain a ball to a circle and when mouse button is down the circle spins faster and faster. The ball spins with the circle and when mouse button is released the ball fly off the circle.

(Quote)

Gameattribute PlayerX is constrained to the player actor's position X.

Each actor "wall" as an attribute "selected" which change between 0 and 1 each time it collide with my player. Only one can have the value 1.

(Quote)

change attribute self.xx to mod((self.xx+1),2)

(Quote)

change attribute self.xx to mod((self.xx+1),2)

(Quote)

depending on your screen size height , create an integer attribute self.xx

(Quote)

(Quote)

Create an integer self attribute call it what ever you want .. "self.xx"

However, your constrains are very limited.

This is still relevant today, tables don't have a row zero, so it causes issues when it has references to attribute that start at 0. Not anything wrong with the tables, this is the intended and correc

Also, if tables are still causing crashes, I'm assuming the above method by @The_Gamesalad_Guru is set with a self.row integer attribute starting at 1? Or does the attribute type/start matter?

Attached is a very quick constrain example (file attached below) for the rotation element of your question - click to rotate - I'll leave the flip element to someone else as all my questions will prob