[Desikac]

Is there a way to "take over" a command registered by another plugin without putting my plugin above the one registering it in plugins.ini? Or if not, is there a way to block that command?

I have my own plugin which uses amx_ban and another alternative command for the same function. I want to block the amx_ban command from admincmd so that only the alternative command from my plugin works if it is not above admincmd in plugins.ini (if it is, both will work).

[jok]

if I got you right:
disassemble the plugin (can only be done if it was compiled before latest amxmodx version) and read the strings for possible commands.

[YamiKaitou]

Just remove the register_concmd line from the plugin that registers it

[Black Rose]

public client_command(id) {
    new command[9];
    read_argv(0, command, charsmax(command));
    if ( equali(command, "amx_ban") ) {
        
        // Your code instead of amx_ban.
        
        return PLUGIN_HANDLED;
    }
    return PLUGIN_CONTINUE;
}

[Desikac]

Originally Posted by Black Rose public client_command(id) { new command[9]; read_argv(0, command, charsmax(command)); if ( equali(command, "amx_ban" ) { // Your code instead of amx_ban. return PLUGIN_HANDLED; } return PLUGIN_CONTINUE; }

That will not prevent the original amx_ban from executing. The player will already be kicked when my function starts.

Originally Posted by YamiKaitou Just remove the register_concmd line from the plugin that registers it

Replacing another plugin is harder than just putting mine first in plugins.ini.

[YamiKaitou]

Originally Posted by Desikac Replacing another plugin is harder than just putting mine first in plugins.ini.

Since you have the source code for the plugin that you want to block, just edit it.

If you still do not want to edit the plugin, then put your plugin above the other and simply return PLUGIN_HANDLED to prevent the execution of the other plugin

[Desikac]

Originally Posted by YamiKaitou Since you have the source code for the plugin that you want to block, just edit it. If you still do not want to edit the plugin, then put your plugin above the other and simply return PLUGIN_HANDLED to prevent the execution of the other plugin

The problem is, people who download my plugin don't put it above, regardless of big red letters below the download link.

[YamiKaitou]

Then that is their problem, not yours.

[Black Rose]

Originally Posted by Desikac That will not prevent the original amx_ban from executing. The player will already be kicked when my function starts. Replacing another plugin is harder than just putting mine first in plugins.ini.

Yes it will. I don't just take guesses to collect posts.
Without plugin:

] amx_ban test
Usage:  amx_ban <name or #userid> <minutes> [reason]
] amx_kick test
Client with that name or userid not found

With plugin:

] amx_ban test
] amx_kick test
Client with that name or userid not found

server_print("plugin_init() admincmd")

server_print("plugin_init() custom plugin")

plugin_init() admincmd
plugin_init() custom plugin

[Desikac]

^
Lol it actually works.
Though I still don't understand how come.