User Triggered Actions aka Custom Commands
¶ Trigger Types
¶ Player Action
¶ Server Action
¶ Server Broadcast Action
¶ Server Selection and Command Availability
¶ Trigger Inputs
user.idis the ID of the user that triggered execution.
user.nicknameis the nickname of the user that triggered execution.
input.<name>the value of the trigger input can be used in conditions and as a variable in templates.
A log of actions taken, conditions evaluated, and command responses is shown to the user after running a trigger. The purpose of the log is to provide feedback on what happened and why. Depending on the information used in the trigger and commands executed this log could contain sensitive information. If you disable the visibility of the log (see below), that permission will limit what appears in the log.
¶ Condition Log
If the trigger's condition uses information that an end user should not see then "Log Condition Result" should be disabled.
Most trigger actions will have some kind of response. The response is visible by default and can be disabled by clicking the eye found at the top of each action. This also controls if the condition evaluation log should be shown for the action.
If the action condition, options, or command response contains information that an end user should not see then the response should be hidden.
Toggling the action's response visibility has no impact on the ability to use the response in conditions or templates.
Action responses are capped at 20KB (20,480 bytes) and are always treated as strings.