Chat commands · Viewer discovery

Publish the commands viewers can use now

Choose one global Commands trigger and let viewers discover a canonical, viewer-safe list that follows the selected channel's current state.

Channel setup showing the global Commands trigger, expanded Available viewer commands list and a command-name conflict. Channel setup on a phone showing the global Commands trigger and expanded Available viewer commands list.
Channel setup shows the same canonical, viewer-safe command catalog that the global chat trigger publishes.

Choose the global trigger

If a word is already owned by another command, Channel setup names the conflict. Choose another word and save; BlokeBot does not silently replace the existing command.

  1. Choose the channel, open Channel setup and expand Commands.
  2. Enter the command words viewers may use, separated by commas and without the exclamation mark. The default is commands.
  3. Select Save Commands. The setting applies to the whole selected channel, not to one Custom Command.
  4. Leave the field blank and save only when you intend to disable the viewer command catalog.

Check what viewers will see

  1. Open Available viewer commands inside the Commands section. It starts collapsed so the setup page stays compact.
  2. Review the current canonical command names and any conflict or availability explanation.
  3. In chat, send the saved trigger such as !commands to publish the same ordered list.
  • The disclosure requests a fresh snapshot whenever it opens. Supported state changes also refresh an open list without replacing an unsaved trigger draft.
  • The list includes its own saved trigger and only commands an ordinary viewer can use.
  • Moderator-only commands and private administration actions are never disclosed.

Understand canonical names

Each Custom Command contributes only the first command word in its saved alias list. That canonical-first rule keeps the catalog short and predictable; secondary aliases still work in chat but are not advertised.

  • Built-in commands use their supported public canonical names.
  • A Custom Command that is moderator-only is omitted even when its canonical name works for moderators.
  • When two routes claim the same word, the catalog reports which entry is shadowed instead of pretending both are available.

Why commands appear or disappear

An unavailable feature is explained beside the list when BlokeBot can identify the cause. If no viewer commands are currently available, the disclosure says so rather than publishing a misleading list.

  • Guess and round-summary commands appear only while the guessing game has the matching active round state.
  • Giveaway entry appears only while a giveaway is accepting entries.
  • Request-board and play-queue commands follow the channel's saved, enabled boards and queues.
  • Moment and clip commands depend on live-stream identity and disappear while the channel is offline or Twitch stream identity is unavailable.
  • Feature commands disappear when that feature is off for the selected channel.

Long lists and live changes

BlokeBot keeps the canonical ordering stable. When the chat response is longer than Twitch permits in one message, it splits the list across multiple ordinary replies without dropping or duplicating command names.

A game opening, giveaway ending, board or queue changing, feature switch, or stream-liveness change can alter membership. Reopen Available viewer commands for a fresh check when you are preparing an announcement or stream instructions.

Fix common catalog problems

  • The chat trigger does nothing: confirm at least one Commands word is saved and resolve any conflict shown in Channel setup.
  • A Custom Command alias is missing: only its first saved word is advertised.
  • A moderator command is missing: the public catalog deliberately shows viewer-safe commands only.
  • A game or Moment command is missing: check the feature, active round or giveaway, and live-stream availability named by the disclosure.
  • The list is empty: enable or configure at least one viewer-facing feature, board, queue or Custom Command, then reopen the disclosure.