Streamer.bot for IRL StreamingAutomate OBS, Step by Step

Contents of the Streamer.bot guide

• 1. Triggers, actions, and sub-actions
• 2. Requirements
• 3. Installing Streamer.bot
• 4. Connecting platforms
• 5. Setting up OBS WebSocket
• 6. Streamer.bot Deck without port forwarding
• 7. Building your first alert action
• 8. Twitch channel points, images, and clips
• 9. Useful IRL automations
• 10. Mobile feedback and other remote access
• 11. Testing and troubleshooting
• 12. Updates and backup
• 13. Security and privacy
• 14. Common questions

1. Understanding triggers, actions, and sub-actions

A trigger is what sets things off. That can be a follow, a subscription, a donation, a chat command, an OBS scene change, or a timer. An action describes the complete sequence that should react to it. The individual steps inside the action are called sub-actions.

A follow can, for example, show an OBS source, start a local audio file, insert a name, wait a few seconds, and hide the source again. Variables from the trigger, such as the display name or the amount, can be reused in later steps.

2. Requirements for the IRL setup

• A stably set up OBS production PC.
• A connected Twitch, YouTube, or Kick account.
• A working signal path from the mobile encoder through a relay or server to OBS.
• Prepared OBS scenes and clearly named sources.
• A local test recording or a private test stream.

Only add Streamer.bot once the mobile video path works reliably. That way, if something goes wrong, it's clear whether the fault is in the uplink, the relay, OBS, or the automation.

3. Installing Streamer.bot

1. Download Streamer.bot only from the official website.
2. Unpack the ZIP archive into a local folder of its own. According to the official guide, you should avoid a synchronized OneDrive, Google Drive, or similar cloud folder.
3. Start Streamer.bot.exe. The Windows version is portable and needs no traditional installation.
4. Normally don't start Streamer.bot as administrator. Custom C# code in particular deserves the same caution as any other locally executed program.
5. After the first launch, set a fixed backup location for exports and backups.

4. Connecting Twitch, YouTube, or Kick

In the platform settings, connect only the accounts whose events or chat functions you actually need. For a Twitch setup, for example, you can use separate broadcaster and bot accounts. For YouTube and Kick, the exact feature set depends on the integration currently supported.

1. Open the platform you want in Streamer.bot and start the official sign-in or authorization process.
2. Check the account name and channel after signing in.
3. Avoid permissions you don't need and account connections you don't use.
4. Use a simple chat or test trigger to check that events are coming in.

5. Setting up OBS WebSocket securely

Since OBS Studio 28, OBS WebSocket v5 is built in. It lets Streamer.bot read and control scenes, sources, and the stream status.

1. In OBS, open Tools → WebSocket Server Settings.
2. Enable the WebSocket server, set a strong password, and change the default port 4455 only if there's a real conflict.
3. In Streamer.bot, open Stream Apps → OBS and add a new connection.
4. If both programs run on the same PC, use 127.0.0.1, WebSocket v5, port 4455, and the password you set.
5. Enable Auto Connect on Startup and Reconnect on Disconnect.
6. Check that the current scene, sources, and stream status show up in Streamer.bot.

6. Streamer.bot Deck: IRL control without open router ports

Streamer.bot Decks are the official web-based alternative to a classic Stream Deck. Streamer.bot itself runs with OBS on the production PC. The application connects to the Streamer.bot web service, and the IRL streamer signs in on the website while on the road and operates their private deck there.

You create the deck on the Streamer.bot website. To do that, you sign in there with your own Streamer.bot account and create a new deck. Because this interface is web-based, you can then open it on the road on a smartphone, tablet, or other suitable browser device.

An example of a prepared IRL deck: the large buttons trigger mute, 180-degree rotation, screenshot, stream marker, BRB scene, and camera switch on the connected production system. The button labels in the illustration are in German.

The right order: actions first, then the web deck

1. Finish the actions locally: On the production PC, first create every function you want as an action in Streamer.bot, for example muting the microphone, rotating a source, taking a screenshot, setting a marker, switching the camera, or switching to BRB.
2. Test each action on its own: Run each action directly in Streamer.bot and check that OBS reacts exactly as intended. Only set up the web deck after that.
3. Connect Streamer.bot to the website: In the local Streamer.bot application, click Login at the bottom left and finish the sign-in or authorization in your browser. That links this Streamer.bot instance to your own website account.
4. Sign in on the Streamer.bot website: Open the official web-based deck interface with the same account.
5. Create a new deck: On the website, create a new private deck for IRL use and, if needed, prepare several pages or function groups.
6. Put actions on buttons: Assign the actions you created locally to the deck buttons you want. Keep labels short and unambiguous, for example MIC OFF, MIC ON, BRB, or CAM 2.
7. Open it on the road: Open the new deck on your smartphone or tablet through the Streamer.bot website and test it over cellular, away from your home Wi-Fi.
8. Keep the production system running: At the production site, OBS, Streamer.bot, and the connection to the Streamer.bot web service have to stay active. A check image should confirm that the triggered action really ran.

Useful deck buttons for IRL streams

Important for the camera: In this setup, Streamer.bot controls OBS. An OBS source can be switched, mirrored, or rotated. Switching between the front and rear camera of the mobile smartphone only works if the streaming app you use, or an additional connection, explicitly passes that function on to Streamer.bot.

For use outdoors, a few large, high-contrast buttons beat an overloaded grid. Give audio, camera, scenes, and emergency functions separate areas. Critical functions like End stream don't belong right next to switches you use often.

7. Your first alert action, step by step

1. In OBS, prepare an alert scene or source group with an image, text, and a short local media file.
2. In Streamer.bot, create an action with a clear name such as IRL: new follow.
3. Add the matching platform trigger. For the first test, activate just a single event type.
4. As OBS sub-actions, show the alert source and restart the media file from the beginning.
5. Insert a short wait and then hide the source again.
6. Run the trigger with Test Trigger and check the Action History if something goes wrong.
7. Make a local OBS test recording and check that picture and sound play exactly once.

Only once this simple sequence works should you add names, amounts, random selection, queues, or more platforms.

8. Twitch channel points for images, Discord, and clips

Twitch channel points aren't just good for short pop-ups. A redeemed reward can start a complete action in Streamer.bot. That lets viewers, for example, request a snapshot from OBS, create a Twitch clip, set a stream marker, or briefly change a prepared scene or source.

Connecting a channel point reward

1. Under Platforms → Twitch → Channel Point Rewards, load the existing rewards or create a new reward directly in Streamer.bot.
2. Create an action with a clear name such as Channel points: IRL screenshot.
3. As the trigger, pick Twitch → Channel Reward → Reward Redemption and assign exactly the reward you want.
4. Limit the cost, the global cooldown, and the maximum number per stream and per viewer. Expensive actions shouldn't run uncontrolled at the same time.
5. If you need input from the viewer, it's available to the action as a variable. Texts have to be filtered before any public display or forwarding.

Taking a screenshot from OBS

With the OBS sub-action Take Screenshot, Streamer.bot can save an image from a selected scene or source. The resulting file path is then available for further steps.

• Pick a media source: The image contains only that source's content, which makes sense for a clean camera picture without extra graphics.
• Pick the complete scene: The image contains the output composed in that scene, so for example the camera, frame, chat, alert, and other visible overlays.
• File name: Date and time plus a sanitized viewer name keep existing images from being overwritten.
• Privacy: Before saving, check whether chat, location, license plates, private notifications, or other sensitive content could be visible in the image.

Passing an image or link to Discord

Streamer.bot supports Discord webhooks for messages. The simple built-in Basic Webhook sends text, for example the viewer's name and a clip link. For the actual screenshot file, you also need a vetted file upload action, such as your own webhook/C# action or a controlled upload whose image URL is then sent to Discord.

Creating a Twitch clip or stream marker

For a reward like Create clip, the action can run the Twitch sub-action Create Clip. The documented duration is between 5 and 60 seconds. On success, Streamer.bot returns the clip URL, among other things, and you can then send it to Twitch chat or through a Discord webhook.

A stream marker is a low-key alternative if you only want to review and cut the spot later in the VOD. Stream markers require VODs to be enabled on Twitch.

Community project: Wheel of fortune for Streamer.bot

Streamer.bot can bring the wheel of fortune ("Glücksrad") by Bittersweet1987 straight into your stream as an interactive extension. The freely available GitHub project includes the local browser source needed for OBS, an extensive settings page, and a prepared Streamer.bot import. You can customize the colors, texts, images, probabilities, and win messages of the segments.

Preview from the project "Glücksrad for Streamer.bot" by Bittersweet1987. The repository describes the project as MIT-licensed.

How the wheel fits into the IRL workflow

1. Download the project from GitHub and check all files before importing.
2. Import the bundled StreamerBot_Import file into Streamer.bot. That creates the prepared action.
3. Design the wheel through settings.html, then add the generated or adjusted index.html as a local browser source in OBS.
4. Connect the imported wheel action to the trigger you want, for example a specific Twitch channel point reward.
5. For donations, use the event trigger of the provider you've actually connected. Only if Streamer.bot receives the donation through that integration can it start the same wheel action automatically.
6. Test the prizes and probabilities in a local recording first. Monetary values or binding prizes need clear rules. For pure fun actions, harmless effects, scenes, sounds, or short challenges work well.

The wheel of fortune is an independent community project and not part of IRL4YOU or Streamer.bot. The project description, the current source code, and the developer's notes in the repository are what counts.

9. Useful Streamer.bot automations for IRL

Streamer.bot can also kick off TTS, sound effects, and external integrations. Test these functions one at a time, so you don't end up with parallel audio paths or uncontrolled viewer texts.

10. Mobile feedback and other remote access

Streamer.bot runs on the production PC and doesn't automatically replace feedback to the mobile streamer. For classic browser alerts, you can keep opening your personal alert page in StreamBuddy and play it through a Bluetooth speaker or headphones.

For freely assignable buttons, the Streamer.bot Deck is the preferred route. If you also need direct access to WebSocket functions, the official documentation describes a VPN route with Tailscale, among other options. Authentication and encrypted connections have to be set up consistently.

11. Testing and troubleshooting

1. Test the platform connection and the incoming trigger separately from OBS.
2. Check the OBS connection status, host, port, WebSocket version, and password.
3. Run the action manually with Test Trigger.
4. In the Action History, check which step last succeeded and which variables were passed.
5. Compare OBS source names exactly. Renamed sources can make existing actions invalid.
6. Use a local recording and a private test stream before you process real viewer events.
7. Also test the deck over cellular, away from your home Wi-Fi, and check each button clearly in the program view or audio mixer.

12. Updates, exports, and backup

Before an update or a bigger rework, export or back up your actions, triggers, and important settings. Review imported community actions completely before you enable them. An export is no substitute for a backup of the entire Streamer.bot folder and the local media that goes with it.

• Use only stable versions for live streams.
• Before updates, close Streamer.bot and back up the whole folder.
• Document the OBS scene collection and the Streamer.bot configuration together.
• After every update, run a private functional test.

13. Security, privacy, and moderation

• Don't publish tokens, passwords, WebSocket credentials, or exported actions.
• Connect only the platform accounts and integrations you need.
• Review community imports and custom C# code before running them.
• Moderate chat texts, TTS, and donation messages, and set length and volume limits.
• Limit WebSocket access to localhost, your own LAN, or a secured VPN.
• Regularly remove old tokens and permissions you no longer need.

Streamer.bot processes its configuration locally. Once you connect Twitch, YouTube, Kick, Discord, or other integrations, their privacy terms apply as well. More information is in the IRL4YOU privacy policy.

14. Common questions about Streamer.bot in IRL streams

Official documentation and more guides

For current features, the official Streamer.bot documentation is what counts, including its notes on installation, the OBS connection, Twitch channel points, OBS screenshots, clip creation, the deck feature, and the Discord webhook integration.

Streamer.bot setup service & consulting

We help with connecting to OBS, building your own triggers and actions, alert sequences, the mobile audio path, and troubleshooting in your IRL production system.