• Getting Started
  • Platforms
  • Twitch
  • YouTube
  • Kick
  • Velora
  • Integrations
  • Amazon Polly
  • Crowd Control
  • Discord
  • DonorDrive
  • Fourthwall
  • Google Cloud TTS
  • IFTTT
  • JustGiving
  • Ko-fi
  • Loupedeck
  • Lumia Stream
  • Meld Studio
  • Microsoft Azure Speech
  • mtion studio
  • OBS Studio
  • Pally.gg
  • Patreon
  • PixelChat
  • PolyPop
  • Pulsoid
  • Rainmaker
  • ResponsiveVoice
  • SAMMI
  • Stream Avatars
  • Stream Deck
  • StreamElements
  • Streamlabs
  • Streamlabs Desktop
  • Streamloots
  • Throne
  • Tiltify
  • TipeeeStream
  • TITS
  • TreatStream
  • TTS.Monster
  • Twitter / X
  • veadotube
  • Voicemod
  • VTS Pog
  • VTube Studio
  • XSplit
  • Actions
  • Actions
  • Chat Action
  • Command Action
  • Conditional Action
  • Consumable Action
  • Counter Action
  • External Program Action
  • File Action
  • Game Queue Action
  • Group Action
  • Input Action
  • Moderation Action
  • Music Player Action
  • Overlay Action
  • Platform Message Action
  • Random Action
  • Repeat Action
  • Script Action
  • Serial Action
  • Sound Action
  • Special Identifier Action
  • Streaming Software Action
  • Text To Speech Action
  • User Lookup Action
  • Wait Action
  • Web Request Action
  • Action Groups
  • Events
  • Commands
  • Consumables
  • Consumables
  • Currency
  • Rank
  • Inventory
  • Stream Pass
  • Redemption Store
  • Overlays
  • Overlays
  • Overlay Widgets
  • Chat Widget
  • Custom Widget
  • End Credits Widget
  • Event List Widget
  • Game Queue Widget
  • Goal Widget
  • HTML Widget
  • Image Widget
  • Label Widget
  • Leaderboard Widget
  • Persistent Emote Effect Widget
  • Persistent Timer Widget
  • Poll Widget
  • Stream Boss Widget
  • Text Widget
  • Video Widget
  • Wheel Widget
  • YouTube Widget
  • Chat
  • Chat
  • Chat Commands
  • Pre-Made Chat Commands
  • Timers
  • Games
  • Moderation
  • Game Queue
  • Giveaways
  • Quotes
  • Music Player
  • Webhooks
  • Users
  • Reference
  • Special Identifiers
  • Developer API
  • MCP Server

  • Chat commands are triggered based on chat text entered by users. Commands by default are single word, case-insensitive, and all start with the “!” character. You must specify the name of the command, the minimum user type that can use it, the actual chat text commands that correspond to it, and the cooldown before the command can be used again.

    You can specify 1 or more chat triggers per command, which is what will be looked for in order to run the command. Each trigger must be separated by a space, or if you want to have a multi-word trigger, place a semi-colon “;” character between each set of words. (EX: “here is a trigger;here’s another one” OR “here is a single trigger;”)

    You also have the option to allow for Wildcard support for a chat command. This makes it so that if any of the triggers you specify are found ANYWHERE in the chat message as a whole word, it will trigger the command. For example, using the chat trigger “what” with the Wildcards option would cause the command to be run for any of the following messages:

    • what is going on?”
    • “who what where”
    • “how in the what

    Note that this will not trigger the command for messages where the chat trigger is inside of another word. For example, if your chat trigger is “abs” and the Wildcards option is enabled, it will NOT trigger off of a message containing the word “absolutely”

    Chat commands provide the following additional Special Identifiers:

    • $message = The entire message sent that triggered the command, including the command trigger itself.

    Site Settings

    Accessibility

    Choose how the site looks. System follows your device setting.

    Cookies

    Choose which cookies to allow. Your preference is saved for 6 months.

    Necessary
    Required for the site to function correctly. Cannot be disabled.
    Analytics
    Helps us understand how visitors use the site. No personal data is shared with third parties.