[rsdtt]

it like the same work

[Impact123]

These "variables" are currently defined like that in core.inc:

Click me

PHP Code:

/**
 * Specifies what to do after a hook completes.
 */
enum Action
{
    Plugin_Continue = 0,       /**< Continue with the original action */
    Plugin_Changed = 1,        /**< Inputs or outputs have been overridden with new values */
    Plugin_Handled = 3,        /**< Handle the action at the end (don't call it) */
    Plugin_Stop = 4,           /**< Immediately stop the hook chain and handle the original */
}; 


This and this has some related information on how these are used and/or expected to be used by sourcemod.
Short answer is that they simply "refer" to a different number.

[rsdtt]

Originally Posted by Impact123 These "variables" are currently defined like that in core.inc: Click me PHP Code: /**  * Specifies what to do after a hook completes.  */ enum Action {     Plugin_Continue = 0,       /**< Continue with the original action */     Plugin_Changed = 1,        /**< Inputs or outputs have been overridden with new values */     Plugin_Handled = 3,        /**< Handle the action at the end (don't call it) */     Plugin_Stop = 4,           /**< Immediately stop the hook chain and handle the original */ };  This and this has some related information on how these are used and/or expected to be used by sourcemod. Short answer is that they simply "refer" to a different number.

It seem like Plugin_Stop will stop all, and maybe Plugin_Handled would still work in other plugins

[rsdtt]

maybe the point is "If the server command was created by a plugin, this has no effect."

[sheo]

It depends on the function. You can write a function that continues action if you return Plugin_Stop and blocks it if you return Plugin_Continue. Actually, its a simple number return. But the most plugins and sourcemod itself usually use Plugin_Stop/Handled for blocking the action, Plugin_Changed to override given values and Plugin_Continue to proceed with original action. Read the function`s description for more info.

[rsdtt]

Originally Posted by sheo It depends on the function. You can write a function that continues action if you return Plugin_Stop and blocks it if you return Plugin_Continue. Actually, its a simple number return. But the most plugins and sourcemod itself usually use Plugin_Stop/Handled for blocking the action, Plugin_Changed to override given values and Plugin_Continue to proceed with original action. Read the function`s description for more info.

OK, Thinks