Please sign in to comment.
[Script Commands] Display whether commands are disabled due to script…
… or setting - The bot now has a modScripting.IsScriptEnabled() function to handle checking if a script is enabled, rather than having repeated code to access the relevant SSC.GetSettingsEntry every time. Now uses the SSC directly instead of the module's CodeObject's GetSettingsEntry. - .scripts, .scriptdetail, .initperf, .enable, and .disable: These commands' output has been made slightly more consistent. Script names are quoted, and when relevant, script names appear with the text "(disabled)". The .scripts command still uses parentheses to indicate disabled scripts. - .scriptdetail, .initperf, .enable, and .disable: These commands may now search for scripts by the start of the input given. For example, "uni" will find a script named "UnicodeMacros". They say no script was found if there are multiple choices. - .help: This command (and the Command Manager) will now list the script in the requirement text. It will have the text "(disabled)" if the script is. This command will now have the text "(disabled)" after the name if the command itself is disabled. Both the script and command may be disabled. - .helpattr and .helprank: These commands now do not list commands that are disabled or commands owned by a script that is disabled.
- Loading branch information...
Showing with 192 additions and 129 deletions.
Oops, something went wrong.