I don't understand how this works:
the manual states:
Returns:
>0 - Rotation successful.
0 - Entity was blocked by obstacles and could not be rotated.

and;
Gliding along walls is always activated. Otherwise the entity could easily become stuck on rotation.

So, c_rotate can never return zero when blocked, or am I wrong?

Imagine your object is inside a small triangle-shaped room, touching the corners. Then it can't rotate no matter how much it glides.

Yes, I understand that, but when I try to rotate a door with c_rotate and the player is blocking the door it will not stop rotating, the return value will never become zero.
When I use 'USE_AABB', it has no collision detection. The door will always rotate.
When I use 'USE_AXIS', the door rotates and move itself to a new position when it is blocked.
So, why is it not possible to stop rotation when blocked?

I tryed this with;
result=c_rotate (me, vector(-2*time_step,0,0),null);
if(result==0) {break;}
but this didn't work, because result gets never zero.

I suppose when you rotate a door with c_rotate and a player is in the way, the door will still rotate but glide out of its hinges. Thus you won't get a zero. c_rotate is not meant to be used for a door and to stop at an obstacle.

I haven't programmed c_rotate, so I'm not sure about my above assumptions, but I'll look into it. Maybe we can implement a flag for c_rotate in a future version so that it stops at an obstacle, rather than gliding.

Would be a nice solution, then you can use c_rotate for other objects too.
Thanks.