MODERATION TOOLS

Most controls live in the dock now, so importing the extension does not fill Streamer.bot with 10,000 actions. If your mods need something as a chat command, you can make one for the method you want.

1. Create a new Action in Streamer.bot and give it a name you will recognize.
2. Create your command in the Commands tab, enable it and set its permissions to Moderators. Set any cooldowns here too.
3. Go back to your action, add a Core → Commands → Command Triggered trigger and pick the command you just created.
4. Add a subaction: Core → C# → Execute C# Method.
5. Pick MODERATION TOOLS Handler as the code, then choose the method you want from the method dropdown. There are plenty to choose from :)
6. Save, then test the command in your Twitch chat.

For example, pick SetTitle for a !title command. A moderator can then type !title Definitely a professional stream to change the stream title. Everything after the command is passed to the method automatically. If you already have !title, edit that command and its action instead of creating a duplicate.

Keep permissions on the command, the method itself does not decide who is allowed to use it.

Nope. If you only want the bot to post a response or keep a counter, use the dock's Commands tab. Those custom commands have their own text, permissions and cooldowns, and do not need a separate Streamer.bot action.

The action and Execute C# Method setup above is for controls that do something, like changing the stream title.

Make sure Streamer.bot is running and its WebSocket Server is started under Servers/Clients → WebSocket Server. The dock uses 127.0.0.1 and port 8080 by default.

If you use a different address, port or a password, add them to the dock URL, for example ?address=127.0.0.1&port=8080&password=YOUR-PASSWORD. Leave out the password part if you do not use one, and leave Enforce All Requests unchecked in Streamer.bot.

If the dock connects but says the handler is missing or disabled, check that you imported the extension and enabled its handler action. If it says Streamer.bot did not answer, check that the handler still has its Trigger Custom Event subaction after the code, with %sbClientResponse% as the event name and Use Args enabled.

The dock connects to your running Streamer.bot. Sending a moderator the dock URL alone will not connect them to your PC, 127.0.0.1 always means the PC opening it.

For mods working from their own PCs, create the chat commands they need using the guide above. They can then use those commands in your Twitch chat while your Streamer.bot handles them.

Twitch only lets the app that created a channel point reward change it. Rewards created outside Streamer.bot can be viewed in the dock, but cannot be edited there.

If you want the dock to manage a reward, create it through Streamer.bot.

Check that Ban Sale Bots and Ban Scam Bots are enabled under Bot Protection. These checks look for known patterns, so they will not catch every possible message.

Streamer.bot 1.0.7 also has an issue with identifying first-time chatters. In that version, MODERATION TOOLS uses the chat log as a fallback. Keep Monitoring → Keep A Chat Log on and let it build up some history. A fresh log cannot reliably tell an older account from a regular who just has not chatted recently, so the extension leaves it alone when it is unsure.

Clearing the chat log or turning it off and on resets that history. The Streamer.bot log tells you why a matching message was left alone.

The chat log stays on your PC, in tawmae - MODERATION TOOLS - Chat Log inside your Streamer.bot folder. It only contains messages recorded while Streamer.bot and Keep A Chat Log were running.

Under Settings UI → Monitoring, choose how long messages are kept or use Clear Chat Log to delete the saved messages and chatters. Clearing it also resets the history used for the first-time chatter fallback on Streamer.bot 1.0.7.