OnPlayerPostRunCommand

[ghost]

Let's add this, It's very useful when you want to change something after processed command, because, for example if you set a velocity in OnPlayerRunCommand, velocity from the tick will be processed anyway.

[jordanbriere]

I don't think internally doing twice the work to provide a post listener would worth the effort and extra computing time it implies to be honest. Making the majority of servers suffers that extra load for a listener that might be used by very few plugins that might have to handle that very specific case you mentioned doesn't seem like a good idea from an API standpoint. Especially considering you can already register your own post hook fairly easily:

@EntityPostHook(EntityCondition.is_player, 'run_command')
def _post_run_command(stack_data):
    player = make_object(Player, stack_data[0])
    ...

[Ayuto]

Actually, it shouldn't really have a performance impact. The hook is already installed, so we would just add a post hook callback. Inside of this callback we would simply check if there are PostPlayerRunCommand callbacks. If there aren't any, we would simply quit the handler like we did here:
https://github.com/Source-Python-Dev-Team/Source.Python/blob/master/src/core/sp_hooks.cpp#L175

So, if no plugin registers a PostPlayerRunCommand callback, there are only one or two very simple additional calls.

[ghost]

Yes!!! Also as I know if I want it through standard EntityPostHook, I should to create the ecx storage otherwise the player pointer will be utilized. I have another problem without the post hook, when you entered in pre hook, gravity velocity (sv_gravity * server.tick_interval / 2.0) has already been added for some reason to player z axis. and maybe it would be better to do these things in post hook of previous tick.