I am not having any luck with the Y offset issue. If you make a platform and constrain it's y.velocity to the negative jumper's y.velocity and you put this into a rule that checks if the jumper is jum

What the guys meant was that you need to set up an integer attribute(player.Dist).

You could constrain the y position so it seems unaffected by gravity.

ok so i created the attribute integer playersy then when i add the constrain attribute to the actor self.position.y to game.playersy the actor doesn't move now, i'm doing something wrong for sure

For my game over element...I have the gameOver graphic actor present off screen at all times with alpha defaulting to 0. Then when my gameOver attribute=1, I locate the actor to screen center and thr

Do i need to create a temporary attribute and that gets assigned on the load and then have that asigned to the real attribute P1l1 P2l1 etc..

I had to add a change attribute in the actor code saying

Think of the scene execution as happening very smoothly on the Mac (which has more processing power), like an analog representation of music. Then when you run it on a device, it stutters a little.

create 2 new game attribute

each actor could have an integer Attribute called something like myNumber.

floor (and ceiling) is an expression...not an attribute...which is used in algorithms. It is similar to rounding but different in the sense that it forces the integer one way...where rounding goes 2

Just put a minus sign in front of the Time Attribute in the equation.

horizontal or a strictly vertical way. Then constrain the other coordinate value (i.e. if starting move is horizontal, constrain Y - if starting move is vertical, constrain X) to one of the equation

Can you explain the floor attribute for me? and i dont get

It was working fine until I decided to create two separate difficulty levels for my game and of course I wanted two separate high scores. I created a new attribute for the harder skill level high sco

My question then is simple: Is there any other way to make objects not movable by gravity but still have collisions tested???

Also, you can define attributes within the same actor with the same attribute name but I don't know why you would want to since it would be hard for you to keep track of.

Actually, instead of using X/Y position zones of the track, maybe add some large, invisible actors at the drift regions that when overlapping/colliding with the car, they set game level attribute(s) w

the moveable option has nothing to do with collisions.

Is there any relationship between attribute name length and game size or performance? In other words, are long attribute names internally translated into symbols that are efficiently managed, or are t