Custom commands
Create commands and scheduled messages
Configure Custom commands.
Create a chat reply and command
The Message library keeps reusable text separate from command structure.
- Open Custom commands.
- Open Settings.
- Stay on the Commands tab.
- Add a command.
- Enter its command words without the exclamation mark.
- Select who can use it.
- Open Message library.
- Add a reply with at least one message.
- Return to Commands.
- Select the saved reply under What happens.
- Select Save changes.
- For a command without a message, BlokeBot opens the relevant tab or section.
- It focuses the field.
- It shows the validation message.
- It keeps the command.
- Save reusable bot replies.
- Connect them to chat words.
- You can also keep counters.
- You can also schedule reminders.
- Replies can include viewer placeholders.
- Replies can include channel placeholders.
- Replies can include argument placeholders.
Add random values to saved replies
- {random_from|one|two} picks one value.
- {random_between|1|10} picks an inclusive whole number.
- Each random token occurrence makes a fresh pick.
- {random_viewer} picks from Twitch chatters currently connected to chat. The active bot account must be a moderator with connected-chatter access.
- If Twitch cannot return the complete chatter list, {random_viewer} becomes empty text.
Other chat tools
- Counters let a command change and report a saved number.
- Scheduled chat can send a saved reply on a timer.
- Scheduled chat can send a saved reply after chat activity.
- Scheduled chat can send a saved reply once a week.
- Twitch announcement uses Twitch's colored announcement surface. The bot must currently be a moderator and authorized for announcements.
- If a scheduled send cannot happen, open its Alerts section. Follow the displayed next action.
Start visual automation flows
Choose Run automation flows under What happens. Every enabled flow whose Custom command event selects this command starts from the same chat invocation.
- Custom commands and Automations must both be on for a command to start a flow.
- Build the connection in Visual automations. The command does not keep a second flow picker.
- If either feature is off, BlokeBot keeps the command.
- If either feature is off, BlokeBot keeps the flow.
- If either feature is off, BlokeBot keeps the run history.
- It suppresses new work and does not replay it later.