I have been trying a gravity function for a player using c_move and the script from the workshop 24. But i did not have any success. Can some one help me ?(I dont want any physics related options for now.)

int height;
action func_player()
{
//set(my,INVISIBLE);
int x_speed;
VECTOR vfeet;
int angle , fall;
vec_for_min(vfeet,me);

while(1)
{

x_speed = 3 ;
fall -= 2;
c_move(my,vector(x_speed * time_step * (key_cuu - key_cud),0,0.5*sin(angle) * (key_cuu - key_cud)*time_step +(0.5*sin(angle)*key_shift * time_step)),nullvector,GLIDE);
camera.x = my.x;
camera.y = my.y;
camera.z = my.z;

camera.pan = my.pan ;
my.pan += (key_cul - key_cur) * 8 * time_step;
c_trace(my.x,vector(my.x,my.y,my.z - 1000),IGNORE_PASSABLE | IGNORE_ME);
if(my.z >= (hit.z - vfeet.z))
{

c_move(me,vector(0,0, fall * time_step),nullvector,GLIDE);
}
else
{
my.z = hit.z - vfeet.z;


}
angle += 10;
wait(1);
}
}

My idea is not really good as c_move puts the player down but the my.z line puts the player up.

Please post you code so that we can have a look at it.

This is and old function that ive made a long time ago, but i think it is what you´re looking for
You just have to call it inside a loop from the entity´s action

Thanks for the code.

Here is a general remark. When you move a character you should either use c_rotate and move OR set the models coordinates and angle directly. But never do both of these methods at the same time. As soon as you set any value directly you loose collision control and hence any prior call to c_move and c_rotate renders pointless.

Using c_move without c_rotate is perfectly fine, even changing the position manually in combination with c_move is okay too.

Any direct change of a coordinate bears the risk of moving the entity into something solid. The same is true for c_rotate. How is that ok?

There are of course exceptions where the player is cone-like or where there is never something above the player because of the game mechanics so you can always move him up.

As you may know that 90% of the time I'm coding movement or similar related stuff and I simply never use c_rotate, it's just unhelpful and bad for the gameplay (except for maybe a door where it could be useful).
In fact you should not use c_move all the time but only when it is necessary, f.i. get the distance to the ground with c_trace and USE_BOX and set the z-position of the entity manually when it is close to the ground (the bounding box should hover above the ground). c_move does not help here, instead it may prevent that the player's/ entity's feet get pulled out of the ground.
As a general rule I think all actors should have an xy-symmetrical bbox and change my.pan manually.

I don't need to tell you that you arguments are all perfectly valid and a good advice for advanced programmers. But please be aware that your expertise concerning movement methods is really extraordinary.

I still think that a consistent use of c_move and c_rotate is a good advice for beginners. The direct change of the pan value is even suited for beginners though.