next »

[Doctor Universe]

Fixed the problem.

[weasello]

I'm not sure just by looking at your code, but:

If you limit momentum it could cause the problem. Your "If gravity>10 gravity = 10" line could do that.

Also you might be applying gravity as a velocity, not as a constant force. That could be in the gravity=0.5 line.

Or it could just be that gravity=0.5 is too little.

Or it could be that the jumping velocity never stops from getting applied (so he is still "jumping up" but the gravity is a bit stronger, giving the float down).

I'd take your big variables (gravity, acceleration, speed) and output them to the screen for debugging, then you can watch them scroll by in real time and see where the problem is.

[Doctor Universe]

I think the problem lies with the line

{move_towards_point(obj_player.x,y,fspeed)}

...because it's when this is activated that the gravity messes up. Having tested the minion (placing a block next to it to see if it jumps correctly, gravity and all) the minion performs accurately. It's when I introduce the move_towards_point that it begins to fall apart. Currently, I don't know any other way to get one object to follow another, aside from mp_potential_step and this has just resulted in a floating block chasing me like a ghost. Similarly, mp_linear_step results in an exceptionally jittery minion, but with similar results to the above.