Periodic, Alert, and Global Messages
Periodic Messages
The Messages page has three tabs:
| Tab | Use for |
|---|---|
| Periodic Messages | Repeating chat messages that run while chat is active. |
| Alert Messages | Event messages for follows, subscriptions, gifted subscriptions, hosts, and similar stream events. |
| Global Messages | Shared feedback text for command errors such as missing points, missing permissions, or cooldowns. |
Use the normal message editor for visual Engine v2 messages. Use Kicklet Studio when a message needs JavaScript, advanced template editing, or script-only behavior.
Periodic messages are automatic chat messages that repeat while chat is active. Use them for Discord links, social reminders, sponsor notes, stream rules, queue instructions, or any message that should appear without a viewer typing a command.
A periodic message uses two conditions:
| Setting | Meaning |
|---|---|
| Messages Threshold | How many chat messages must happen before this periodic message can be scheduled again. |
| Period | How long Kicklet waits after the threshold is reached before sending the message. |
For example, if the threshold is 20 and the period is 10 minutes, Kicklet waits until 20 chat messages have happened for that periodic message, then schedules it to send 10 minutes later. After scheduling, the message counter resets.
- Open Messages.
- Open Periodic Messages.
- Select Create Message.
- Enter the message text.
- Set Send every.
- Set After messages.
- Enable Pin message if the message should be pinned when supported.
- Test the message if it uses variables or logic.
- Save the message.
Periodic messages can be enabled, disabled, edited, or deleted from the list. Each row shows the interval, message threshold, optional pin state, and a preview of the rendered template source. Standard accounts can create a small number of periodic messages, and premium accounts can create more.
The message text can use Kicklet code, including counters, points, variables, random text, and helper functions. Open Kicklet Studio when the message needs JavaScript or advanced template editing.
The period must be at least 1 minute and at most 24 hours. The message threshold must be at least 1. The Pin Message option is available in the UI, but pinning depends on the current Kicklet/Kick chat API support.
Alert Messages
Alert messages are chat messages sent when Kicklet receives stream events. They are useful for thanking viewers and making follows, subscriptions, gifted subscriptions, and hosts visible in chat.
Kicklet currently supports these alert message types:
| Alert | Available variables |
|---|---|
| Follow | sender |
| Unfollow | sender |
| Subscription | sender, amount |
| Gifted subscriptions | sender, amount |
| Host | sender, amount |
sender is the viewer who caused the event. For gifted subscriptions, sender is the gifter and amount is the number of gifted subscriptions. For hosts, amount is the viewer count from the host event.
Open Messages, then Alert Messages to edit alert messages. Each alert type can be enabled or disabled independently. You can edit the message in the normal visual editor or open Kicklet Studio for script messages and advanced templates. Alert messages can use Kicklet code, so you can include event data, random text, counters, points, variables, or custom formatting.
Default examples include:
| Alert | Default message |
|---|---|
| Follow | Thank you for the follow, {{sender}}! |
| Unfollow | A channel-specific unfollow message when configured. |
| Subscription | Thank you for the subscription, {{sender}}! |
| Gifted subscriptions | Thank you, {{sender}}, for the gifted {{amount}} subscriptions. |
| Host | Thanks to {{sender}} for hosting with {{amount}} viewers! |
Global Messages
Global messages are shared command feedback messages. They are not tied to one command. Kicklet uses them when a command cannot run because of a common reason, such as missing permissions or a cooldown.
Global messages are useful because you can change the wording once and it applies everywhere that message type is used.
| Global message | Sent when |
|---|---|
| Not enough points | A command or shop action requires more points than the viewer has. |
| No permission | The viewer does not have the required permission for a command. |
| Command cooldown | A command is still on cooldown. |
| Stream live state not matched | A command is only available while live or offline, and the channel is currently in the other state. |
Open Messages, then Global Messages to edit shared command feedback. Global messages can be enabled or disabled individually. They also support Kicklet code and receive context variables from the failed command.
Useful variables include:
| Message | Variables |
|---|---|
| Not enough points | sender, cost |
| No permission | sender |
| Command cooldown | sender, timeLeft |
| Stream live state not matched | sender, usability |
For cooldown messages, timeLeft contains the remaining cooldown duration. Format it in the code version used by that message.
Use global messages for system wording and error responses. Use alert messages for event announcements. Use periodic messages for scheduled reminders.
Message Editor and Studio
Visual Engine v2 messages are edited with text, variables, and emotes. The available variables depend on the message type. For example, periodic messages expose periodic-message data, alert messages expose event data, and global messages expose the failed command context.
Messages saved as Engine v2 script are edited in Kicklet Studio. The normal dialog shows a Studio prompt for those messages, because script messages can contain JavaScript logic and multiple output paths.
Older Engine v1 messages remain editable. When a legacy message is opened, the editor shows an update option so the message can be converted to Engine v2 template editing.
Use the test button before saving when a message contains variables, conditions, or helper calls.
See Kicklet Studio for script mode, Studio settings, and the preview test panel.