[IstuntmanI]

Quote:

Originally Posted by Crayder All of you are just wrong. There are functions and macros made for exactly what you want. The callcmd macro and the PC_EmulateCommand function are both for calling commands like this. Don't call the function manually, that's not how the plugin was made to be treated.

Actually, I told him that PC_EmulateCommand is recommended.

By the way, "callcmd::" macro is the same thing as "pc_cmd_" (excepting the fact that it won't be automatically replaced with the help of include, if the command function will be renamed [anyway, the function name won't be renamed, as there's no need to anymore]):

pawn Код:

#define callcmd::%0(%1) pc_cmd_%0(%1)

I preffer to use "pc_cmd_" because of one thing: "callcmd::" can't be used in things like CallRemote/LocalFunction as (a regular public name, a string), as it is just a replacement for the compiler.

And anyway, manually calling the function has two more benefits (of which I can think now): first, we can increase the execution speed, as it isn't calling those 2 callbacks, and second, we can also execute that command's function even if there's a flag/OnPlayerCommandReceive rule which prohibits it.