Commands
Commands are chat triggers such as !discord, !lurk, or !clip. A command can send a static response or run template code for dynamic behavior.
The Commands page has three areas:
| Area | Use for |
|---|---|
| Commands | Commands you create or install for your channel. |
| Default Commands | Built-in Kicklet commands such as points, watchtime, uptime, song requests, and command management. |
| Gallery | Marketplace commands that can be imported into your account. |
Create a Command
- Open the dashboard.
- Go to Commands.
- Open Commands.
- Select Create Command.
- Enter the command name without the leading
!. - Enter the response.
- Add aliases if the same response should be reachable through multiple names.
- Choose permissions, usage mode, cooldowns, and point cost if needed.
- Save the command.
The command is active immediately after saving.
New simple commands use Engine v2 template responses. A simple response can be plain text or include variables such as {{sender.username}}. Use the test button before saving when the response contains variables or logic.
Command Settings
Custom commands can be configured with these common settings:
| Setting | Meaning |
|---|---|
| Active | Enables or disables the command. |
| Reply / as response | Sends the output as a reply to the triggering chat message when supported. |
| Aliases | Additional triggers for the same command, without needing separate commands. |
| Permissions | Who can use the command. Available roles include Everyone, Subscriber, VIP, OG, Moderator, and Broadcaster. |
| Usage | Whether the command can run always, only while live, or only while offline. |
| Global cooldown | Minimum time between any two uses of the command. |
| User cooldown | Minimum time before the same viewer can use the command again. |
| Point cost | Points charged when the command runs. |
Use aliases for alternate spellings or short forms. Use command groups when several commands should be enabled, disabled, or organized together.
Kicklet Studio
Kicklet Studio is the advanced editor for commands and messages. Open it from the Kicklet Studio button on the Commands page.
When creating a command in Studio, choose one of two editor types:
| Type | Use for |
|---|---|
| Visual | No-code responses built from text, variables, and emotes. |
| JavaScript | Full Engine v2 script code for commands that need logic, state, API helpers, or multiple chat messages. |
See Kicklet Studio for the command tree, settings editor, script mode, and test panel.
Command Groups
Command groups let you enable or disable several commands together. For example, you can place game-specific commands in a group and turn that group off when you switch categories.
Create groups from the command page or from Kicklet Studio. A group has a name, an optional description, an active state, and cooldown settings. After a group exists, you can create commands inside it or move existing commands into it.
When a command group is disabled, commands inside that group no longer respond in chat. Kicklet treats them as unavailable until the group is enabled again. The individual commands keep their own active state, permissions, cooldowns, costs, and responses, so you can turn the whole group back on without reconfiguring each command.
Use command groups for:
| Use case | Example |
|---|---|
| Game-specific commands | Enable !rank, !build, or !server only while playing that game. |
| Event commands | Turn giveaway, tournament, or sponsor commands on only during an event. |
| Seasonal commands | Keep commands configured but disabled until they are needed again. |
| Testing | Keep unfinished commands in a disabled group while preparing them. |
Group names can be up to 32 characters long, and descriptions can be up to 300 characters. The number of command groups depends on your account limits.
Override a Default Command
Default commands are built into Kicklet, such as points, watchtime, uptime, song request, command management, and other common chat tools. You can enable, disable, and edit them from the Default Commands tab.
For most changes, edit the default command instead of replacing it. The default command editor lets you change the command's availability, permissions, aliases, cooldowns, point cost, response style, and command-specific configuration. Many default commands expose configurable messages or labels through the Config step. Those values are inserted into the command's built-in response template, so you can adjust the text while keeping the original behavior.
Override a default command only when the behavior should be completely different. To override it, create a custom command with the same trigger as the default command. Custom commands are checked before default commands, so the custom command handles that trigger instead.
Examples:
| Goal | Recommended approach |
|---|---|
| Change the wording of a default response | Edit the default command config. |
| Restrict a default command to moderators | Edit the default command permissions. |
| Add aliases to a default command | Edit the default command aliases. |
| Change cooldowns, live/offline usage, or point cost | Edit the default command availability settings. |
Make !points do something completely custom | Create a custom command with the trigger points. |
If you override a default command, remember that you are replacing the built-in behavior for that trigger. Features such as argument handling, built-in API calls, and default response templates no longer apply unless you recreate them in your custom command.