$SecuredExecutor

Syntax

$SecuredExecutor <bitflag>|

Description

To secure and manage who can actually load and execute scripts, some clients use a proprietary protocol extension: $SecuredExecutor.

First, the client sends a "SecuredExecutor" flag in the $Supports command (if the hub supports the extended protocol), so that hub developers could support that feature in their hub's GUI. For example, they could add a list of granted executors with their rights.

Then, the hub must send the extended command $SecuredExecutor <rights> to, and only to, the granted executors. The <right> value is a bitflag of what actions are allowed to the user's scripts:

• Bit 0 (1) - Can send messages on Central Chat.
• Bit 1 (2) - Can send private messages.
• Bit 2 (4) - Can send raw commands to the hub.

A value of 0 is permitted and could be used for BOTs that don't need to interact.

For example, sending:

$SecuredExecutor 7|

to the user [@Bot]Cerbere, gives [@Bot]Cerbere's scripts all rights.

Sending the following:

$SecuredExecutor 3|

to the user [@Bot]GeneralBot, gives it rights to send MC/Private messages only.