Kicklet Studio
Kicklet Studio is the advanced editor for commands and messages. Use it when a response needs JavaScript, advanced template editing, command settings, or repeated testing while you work.
Open Studio from the Kicklet Studio button on the Commands or Messages page.
When to use Studio
Use the normal dialog for simple visual responses. Use Kicklet Studio when you need to:
| Use case | Example |
|---|---|
| Edit several items | Switch between commands, command settings, default commands, and messages without closing the editor. |
| Write JavaScript | Use Engine v2 Script for branching, state updates, helper calls, or multiple chat messages. |
| Tune settings | Edit command identity, active state, permissions, usage, cooldowns, point cost, aliases, and installed-command config. |
| Test output | Run a command or message in the preview chat before saving. |
| Update legacy content | Open older Engine v1 content and move it toward Engine v2 editing when needed. |
Command tree
The left side of Studio shows the available editable items.
| Tree area | Contains |
|---|---|
| Commands | Custom commands and command groups. |
| Default Commands | Built-in Kicklet commands that can be enabled, disabled, and configured. |
| Installed commands | Marketplace commands installed in your account. |
| Periodic Messages | Repeating chat messages. |
| Alert Messages | Stream event messages such as follows, subscriptions, gifted subscriptions, and hosts. |
| Global Messages | Shared command feedback messages such as missing permission or cooldown messages. |
Command groups can be opened from the tree to edit their name, active state, and cooldown settings.
Editor modes
Studio uses different editor modes depending on what you open.
| Mode | Use for |
|---|---|
| Visual | No-code Engine v2 template responses built from text, variables, and emotes. |
| Script | Engine v2 JavaScript for custom logic, state changes, helper calls, and multiple chat messages. |
| Settings | Command, group, default-command, installed-command, and message settings. |
| Legacy v1 | Older template content that still uses the previous engine. |
Visual mode is best for normal chat text. Script mode is best when the response needs logic that cannot be expressed as simple text with variables.
Settings
For commands, Studio can edit:
| Setting | Meaning |
|---|---|
| Command | Main trigger without the leading !. |
| Active | Whether the command can run. |
| Reply / as response | Whether the output should reply to the triggering chat message when supported. |
| Usage | Whether the command can run always, only while live, or only while offline. |
| Permissions | Which viewer roles can use the command. |
| Cooldowns | Global and per-user cooldowns. |
| Point cost | Points charged when the command runs. |
| Aliases | Additional triggers for the same command. |
| Configuration | Extra fields exposed by installed marketplace commands or default commands. |
Script commands do not use the normal reply toggle in the same way as visual responses. In script mode, use chat helper functions such as async.messages.send(...), messages.send(...), or messages.reply(...) to control output.
Testing
Use the test panel before saving when a command or message contains variables, arguments, conditions, helper calls, or JavaScript.
Command tests let you enter optional arguments after the command trigger. Message tests render the selected message with the matching message context. The preview chat shows generated chat messages and rendered output.