[Pierre-Marie Baty]

Ah, then that might be because the bot's max speed is incorrectly retrieved.

The fact that bots bleed when you shoot at them means that RunPlayerMove() is called for them each frame. Hence we can guess that the bots call their Think() function successfully.

However if in spite of the RunPlayerMove() call the bots still float in mid-air then the movement speeds you pass in RunPlayerMove() must be zero. The movement is still executed, but the bots perform it at speed 0, giving the impression they are stuck and don't think at all.

Perhaps Steam changed the way the players' max speeds work. In Counter-Strike for example, this bug occured with the Steam upgrade. Before, with CS 1.5, the max speeds were sent to clients over the network using a network message, now in Steam/CS 1.6 they are just set in the players' edicts at pPlayerEdict->v.maxspeed.

That's all I can think of so far...