[Mero]

Hi guys
editing .sp files is a fix of a problem
but editing it is problem
so here's the problem
I want to make some people VIP
and only VIP (and certainly admin) have access to a command example "sm_resize"
but the problem is I dont want them to use those commands on other people
I want them to have access to a command like "sm_resize {VIP PLAYER NAME}"
So some people told me you can't do this by overrides only, you must edit the plugin
and noticed that I cant edit a smx file, I can edit .sp files only (and then compile it and somethin like that...)
So here's the main question
How can I edit the .sp file
thanks

[DarkDeviL]

Originally Posted by Mero So some people told me you can't do this by overrides only, you must edit the plugin

That information can be both true and false.

If the creator has done his/her work properly, you should be able to override such things easily..

No matter which kind of branch you're in, you can always find people doing things in a lousy way and/or otherwise trying to cut corners where they can. If your plugin has been created by someone like that, then it is possible that the plugin code needs to be altered.

If the plugin you are using is "[ANY] Resize Players - 1.5.1 - 2014/11/20", then you can override "sm_resize" (and all the other "Overrides" listed there), to get the wanted functionality either for specific flags, or for giving specific groups access to that command.

Without a link to (or a copy of) the specific plugin you're have, I'm afraid it won't be possible to help you more than that.

Originally Posted by Mero So here's the main question How can I edit the .sp file

Open the .sp file with your favorite text editor (nano, vi, vim, mcedit, Notepad, Notepad++, ..., you name it), change what you need to change, save the file and exit your editor.

[cravenge]

Don't forget to compile the .sp after doing so, move the compiled .smx file to plugins folder, and overwrite the previous one. Otherwise, no changes will be made.

[Fyren]

Originally Posted by arne1288 If the creator has done his/her work properly, you should be able to override such things easily.

This isn't true. Overrides don't know or care about command parameters.

[DarkDeviL]

Originally Posted by Fyren Originally Posted by arne1288 If the creator has done his/her work properly, you should be able to override such things easily. This isn't true. Overrides don't know or care about command parameters.

Yup, I have to admit I completely missed this part:

Originally Posted by Mero but the problem is I dont want them to use those commands on other people

Closest OP will get to this is probably a combination of overrides (to give access to sm_resize) and immunity levels to prevent lower (and/or equal) immunity level admins using it on others. It would still not be 100% identical to OP's request though. Higher immunity admins would always be able to use it on lower level admins.

[ddhoward]

Originally Posted by Fyren This isn't true. Overrides don't know or care about command parameters.

But overrides can be used to limit whether parameters are accepted.

Something like this:

PHP Code:

public void OnPluginStart() {
    RegAdminCmd("sm_SomeCommand", cmd_callback, 0, "Some command");
}

public Action cmd_callback(int client, int args) {
    int target = client;
    if (CheckCommandAccess(client, "sm_SomeCommand_TargetOthers", ADMFLAG_GENERIC, true) {
        //declar a char array, get the argument, run it through FindTarget and store the result in 'target'
    }
    //the rest of the command's code
}