[Exino]

Does anyone know of a way to block commands in SourceMod? I, for instance, specifically want to block "+attack" for a set amount of time after the client jumps. I want this to work on bots as well.

[bl4nk]

Hook the command and "return Plugin_Handled;". Some things can not be blocked though as they happen client side as well.

[L. Duke]

+attack is handled client side. It gets sent to the server and can be seen in the ProcessUsrcmds function. I think that you can access them in sourcemod using the GetClientButtons command. Check the SourceMod API.

[raydan]

in amxmodx, it can use register_forward(FM_CmdStart,"xxx"); then something like "buttons &= ~IN_ATTACK"

is there any same function in sourcemod?

[Nican]

PHP Code:

if( GetClientButtons(client) & IN_ATTACK ) 
{
   //...
} 


List of constants:
http://docs.sourcemod.net/api/index....ad=file&id=47&

[raydan]

Originally Posted by Nican PHP Code: if( GetClientButtons(client) & IN_ATTACK )  {    //... }

if "return Plugin_Handled" in here. all command will be blocked
should be a way to remove "IN_ATTACK"

[SAMURAI16]

something like this:

public blah(client)
{
    new buttons = GetClientButtons(client);
    
    if(buttons & IN_ATTACK)
        buttons &= ~IN_ATTACK;
    
    SetClientButtons(client,buttons);
}

public SetClientButtons(client,button)
{
    if(IsClientConnected(client) && IsClientInGame(client))
        SetEntProp(client, Prop_Data, "m_nButtons", button);
}

Depends when is called, and about a 'return Plugin_Handled' I remember too, on HL1 it was necessary to call after removing ATTACK from a client

[Nican]

There is no such command as "SetClientButtons"...

My suggestion would be getting CBaseCombatWeapon::m_flNextPrimaryAttack of the player is holding and setting it to a value to something like GetGameTime() + 500.0

[SAMURAI16]

Originally Posted by Nican There is no such command as "SetClientButtons"...

look again

About CBaseCombatWeapon::m_flNextPrimaryAttack i'm almost agree with that

[raydan]

m_flNextPrimaryAttack only work on IN_ATTACK, how about prevent player jump or couch?