I never thought of this 'lifting up' before move, too.
Great advice and insight!
Thank you, Damocles!

I think "lift up before move" is a workaround to the problem.

What about if the player is a vehicle?

The trick is to adjust the bounding box I think.

Additional thoughts:

There are functions already implemented in the acknex move instructions.
for instance, the model can walk over stairs which are lower than the height of the origin of the model.

Shouldn't this instruction already take care of an issue like stucking in a slope?

I tried adjust move_min_z and move_friction but same.

@Pappenheimer: I agree. That's basically why I still think that there's a bug in c_move. However, my entity can still walk up stairs, so luckily everything is working. (PS: howdy!)

I posted all my movement code to the wiki at: http://www.coniserver.net/wiki/index.php/Modified_Kingdom_Hearts_Movement

@F.Lim: I was worried too that Damocles's solution wouldn't work for my entity because his entity floated above the ground and mine is standing on the ground. However, you can keep the entity on the ground and just lift the bounding box slightly off the ground. This might not be a great solution for a car if you're seeking realistic movement, but it worked great for my little goblin game.

There were two reasons for the problem: your movement code plus a bug in c_move.

The bug in c_move causes entities to get entangled on 'hooks' in some cases, in your case on the vertical surfaces of the triangle-shaped blocks you've made the 'hill' from. This special case will be fixed in the next version, but there can still be other sorts of hooks in the ground where the same happens.

For this reason, the real fix is a better movement code, as suggested by Damocles. NEVER move an entity by dragging its bounding box along the ground. ALWAYS keep a distance from the ground. Use c-trace to let the entity float in step-size height above the ground. The reason is not only the above problem, but also that movement by dragging is very slow because of the permanent collisions. If you have 1000 actors moving around, you'd end up with 10 fps with this method of movement.

Check the movement code in the templates.

You bet. Better don't glide 1000 entities along a wall.