[Plugin] Pawn.CMD

[Stanford]

Great job! I hope that you will keep updating it - and it would be cool if someone posts a benchmark with ZCMD, YCMD and iZCMD and maybe other command processors.

[Crayder]

Originally Posted by Stanford

Great job! I hope that you will keep updating it - and it would be cool if someone posts a benchmark with ZCMD, YCMD and iZCMD and maybe other command processors.

There is no need for any of those benchmarks, any plugin processor like this and MCMD knock out any PAWN processor without doubt by miles.

[YourShadow]

Originally Posted by Crayder

@YourShadow Can you let us have some more features like:
- Not ignoring the return value, so we can hide commands
- Disabling commands for certain players, which would return 0 for them

PHP Code:

public OnPlayerReceivedCommand(playerid, cmd[], params[], bool:exists) 
{ 
    if (playerid ...) // condition
    { 
        SendClientMessage(playerid, 0xFFFFFFFF, "This command not available for you"); 

        return 0; // will not call "cmd: ..."
    } 

    return 1; 
} 


[Crayder]

Originally Posted by YourShadow

PHP Code:

public OnPlayerReceivedCommand(playerid, cmd[], params[], bool:exists) 
{ 
    if (playerid ...) // condition
    { 
        SendClientMessage(playerid, 0xFFFFFFFF, "This command not available for you"); 

        return 0; // will not call "cmd: ..."
    } 

    return 1; 
} 


That would require very slow code, like strcmp. Using many strcmp cases could make Pawn.CMD slower than any other processor.

[YourShadow]

PHP Code:

cmd:ban(playerid, params[])
{
    if (pAdmin[playerid] == 0) // condition
    {
        SendClientMessage(playerid, 0xFFFFFFFF, "This command not available for you");

        return; // exit from function
    }
    
    // code here
} 


[Crayder]

That would have to be placed in every command I want blocked.

Also, do you realize how slow if statements are? Another thing to slow us down.

[YourShadow]

Originally Posted by Crayder

@YourShadow Can you let us have some more features like:
- Not ignoring the return value, so we can hide commands
- Disabling commands for certain players, which would return 0 for them

Show me an example of how you would like it to see.

[Yashas]

Originally Posted by YourShadow

Show me an example of how you would like it to see.

Its here,
http://forum.sa-mp.com/showthread.ph...95#post3475795

Try to keep the syntax same so that people can easily switch. You are beating other plugin based command processors because you have lesser features.

Other processors have two callbacks. You should have one callback before executing the command and one callback after executing the command.

[vannesenn]

Maybe something like this

CMD:command(playerid, params[], cmd_id)

. cmd_id is unique command ID(like dialogid for dialogs). And then

public OnPlayerReceivedCommand(playerid, cmd_id, params[], bool:exists)
{
    switch(cmd_id)
    {
         // CODE GOES HERE
    }

}

[Crayder]

Originally Posted by vannesenn

Maybe something like this

CMD:command(playerid, params[], cmd_id)

. cmd_id is unique command ID(like dialogid for dialogs). And then

public OnPlayerReceivedCommand(playerid, cmd_id, params[], bool:exists)
{
    switch(cmd_id)
    {
         // CODE GOES HERE
    }

}

Not a bad idea, but not what I was picturing... But still not a bad idea.

Here's what I had in mind.

- Not ignoring the return value of commands:
Allow commands to return whatever integer the scripter wants. Returning '0' would result in the default actions, the unknown command stuff.
You could also add a new parameter to the callback, a 'result'. The 'result' parameter would hold the value returned by the command.

- Add a function for disabling/enabling specific commands for specific players.
SetPlayerCommandAllowed or something similiar, parameters: (playerid, cmdname[], bool:allow)
Setting 'allow' to false would return '0' if the player used this command, otherwise the command would execute.
Or, you could add yet another parameter to the callback, 'bool:allowed'. You would set this to the value set by the scripter. Then we could easily handle what happens when a player used a command they aren't allowed to use.

native SetPlayerCommandAllowed(playerid, cmdname[], bool:allow);
forward OnPlayerReceivedCommand(playerid, cmd[], params[], bool:exists, result, bool:allowed);

Doing it this way would keep the speed minimal still, and make the scripters' lives easier.