[Silencer123]

Example:
In almost every Game you have the Command +jump/-jump,
which, indeed, makes you jump. Now if I do this in my Plugin:

register_concmd("+jump","something_on",0)
register_concmd("-jump","something_off",0)

It has no Effect, because the Game is already using this.
So the Thing I ask you to change is, that both works:
1. Jumping
2. The On and Off Commands
- Not only Number '1.'!
Thanks for Replies in Advance!

[Greenberet]

+jump is a client side command
you have to do something like this in prethink

if(pev( id, pev_buttons ) & IN_JUMP)
{
//put your jump code here
}

[Silencer123]

Thanks alot!
It works just fine in this Case!

public client_PreThink(id)
{
    if(pev(id,pev_button)&IN_JUMP)
    {
        gravityon(id)
    }
    else
    {
        gravityoff(id)
    }
}

[BAILOPAN]

hi,
i do not understand your other items on the list but as greenberet said, +jump is a usercmd (like impulses), processed internally by the engine. it is not hookable as a client command.

[Silencer123]

Originally Posted by BAILOPAN it is not hookable as a client command.

That is what I needed a Solution for.
But there might be other Commands which do not have a fakemeta, client_PreThink or engine
way of Solution and if so there would be no way to solve the Problem, as long as you cannot
do a register_concmd or such via AMXX for Commands which are already defined by the Games Engine

[PM]

Originally Posted by Silencer123 That is what I needed a Solution for. But there might be other Commands which do not have a fakemeta, client_PreThink or engine way of Solution and if so there would be no way to solve the Problem, as long as you cannot do a register_concmd or such via AMXX for Commands which are already defined by the Games Engine

All console commands that are not processed by the client directly are sent to the server and go through the gamedll's ClientCommand handler, and thus you can hook them using register_clcmd. Commands which are handled on the client never get sent to the server. This means that the only way of knowing that such a command was executed on the client in AMXx (which is a server-side modification) is looking for side-effects (such as the buttons entvar for commands like +attack or client disconnect for commands like quit). It also means that you can't prevent the command from being executed; the best you can do is try to revert its effects.

So no, there is really no server-side solution for this problem.