#Commands

Chat commands let your viewers and you trigger actions by typing a keyword in chat, such as !tts or !ai. When a command runs, 4thRock performs an action (like reading a message aloud or queueing media) and can post a reply back to chat.

#Where to manage commands

Manage all of your commands from the Commands area of the dashboard. There you can see each command, set who is allowed to use it (its required role), adjust cooldowns, and edit its reply text. Changes apply live, so you do not need to restart anything.

Commands fall into a few categories:

• Feature commands that turn a feature on or off, such as !tts, !captions, !ai, and !media.
• Action commands that do something on demand, such as queueing media or interacting with a goal or giveaway.
• Info commands that reply with status or help text.

#Enabling a feature is enabling its command

Several features are turned on and off by their chat command, not by a separate enable toggle in the dashboard. This is the command-as-gate model: the command is the single control point for on/off, which keeps the dashboard and chat from drifting out of sync.

This applies to Text-to-Speech (!tts), captions (!captions), AI (!ai), and media (!media). To enable one of these features, enable its command (for example, !tts on). The dashboard settings for these features control configuration only, such as voices and appearance, while the command owns whether the feature is active.

For Text-to-Speech configuration details, see its page.

#Editing command responses

You can reword the text a command posts back to chat, with two safeguards.

System-locked responses cannot be edited. Lifecycle and help text (for example, working indicators and usage or status messages) are managed by 4thRock. These show as locked in the editor and stay read-only. You can still adjust the command's role, cooldown, and other settings; only the locked response text is protected.

Editable responses protect required placeholders. For data replies you are allowed to reword, 4thRock guards the placeholders the command needs, such as {user}, {channel}, and {target}. If you try to save a response that drops a required placeholder, the save is blocked so you cannot accidentally break the reply. Leaving a field blank falls back to the built-in default.

#Example

To turn on Text-to-Speech and let your viewers use it, enable the !tts command. A viewer then types:

!tts Hello {username}, welcome to the stream

4thRock reads the message aloud through your overlay. To turn the feature back off, run !tts off.

#Related

• Text-to-Speech
• Behavior