From 7fa9eb8ecdeafe520fadf865ad8463a9ac1b47cb Mon Sep 17 00:00:00 2001 From: gumi Date: Mon, 15 May 2017 12:20:57 -0400 Subject: update documentation for add_group_command --- doc/script_commands.txt | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) (limited to 'doc') diff --git a/doc/script_commands.txt b/doc/script_commands.txt index 0ba350ad1..3b01d8977 100644 --- a/doc/script_commands.txt +++ b/doc/script_commands.txt @@ -7773,6 +7773,21 @@ OnAtcommand: --------------------------------------- +*add_group_command("", , , ) + +Allows to explicitly change the command permissions for a specific group. + +This command bypasses group inheritance, which means groups inheriting from +the specified will NOT inherit the specified permission. You should +use add_group_command() for every group you want to give permission to. + +Example: + bindatcmd("foobar", "NPC::OnUseCommand", 99, 99, 0); // define the command + add_group_command("foobar", 2, true, false); // allow group 2 to use @foobar + add_group_command("foobar", 5, true, true); // allow group 5 to use @foobar and #foobar + +--------------------------------------- + *unbindatcmd("command") This command will unbind a NPC event label from an atcommand. @@ -7790,7 +7805,8 @@ scripts-atcommands this way. *can_use_command(""{, }) Checks if the attached or specified player can use the specified -atcommand and returns true or false accordingly. +atcommand and returns true or false accordingly. Works for both +built-in atcommands and custom atcommands. --------------------------------------- -- cgit v1.2.3-60-g2f50