The Playbook

The Streamer’s Playbook.

Real-world automation scenarios built with the Auto-Hype Director.

Scenario 01

The Boss Fight: Pushing In the OBS Facecam on a Chat-Velocity Hype Spike

You’re forty minutes into a brutal boss attempt and the run is finally going right. You can’t feel it from inside the fight, but chat can — the messages start stacking faster, the emotes pour in, and the room leans forward all at once. That surge of chat velocity is the most honest hype signal you have, and it’s happening at the exact moment your hands are least free to do anything about it.

So you let the Auto-Hype Director watch it for you. A Trigger node compares chat velocity against your hype threshold, and an Action node switches OBS to a tighter facecam angle the moment it crosses. The switch fires once when the condition becomes true — not on every tick — and when chat settles back below the threshold, streamerOS returns you to the scene you were on. You never touch a hotkey; the broadcast simply tightens around the moment.

Node setup · Boss Fight

Trigger

Chat Velocity > 50 / s

hype detected

Action

Scene = Facecam Close-Up

push in on the reaction

Scenario 02

The Big Super Chat: A Celebration Scene and Sound When Support Lands

A viewer drops a big Super Chat in the middle of a fight. It deserves a moment on stream — but you’re mid-game, and by the time you’ve read it and reached for a hotkey, the moment has passed and the supporter got a flat “thanks” three minutes late.

The Auto-Hype Director catches it for you. A Super Chat Trigger fires when a single Super Chat crosses the amount you set, and two Action nodes run together: one switches OBS to your celebration scene, the other plays your thank-you sting from the clips folder. Super Chats interrupt the rule loop ahead of the regular velocity ticks, so the reaction lands while the donation is still on screen.

Node setup · Big Super Chat

Trigger

Super Chat ≥ $20

real support lands

Action

Scene = Celebration

give it a moment

Action

Play Sound = Thank-You Sting

with a cooldown

Scenario 03

The Clutch: Switching OBS Studio to a Focus Scene When Chat Goes Silent

You’re in a 1v5. The whole lobby is on you, and there is no universe where you take a hand off the mouse to reach for an OBS hotkey and swap to your “Tryhard / Focus” scene — the moment you do, you lose the round. Meanwhile chat goes dead silent, everyone holding their breath at once.

The Auto-Hype Director reads that silence for exactly what it is. A Trigger watches for chat velocity dropping below a low threshold and switches you to a clean Focus scene, stripping away the overlays that would distract you. Then, when you clutch it, chat detonates — velocity spikes past your hype threshold — and streamerOS cuts to your Victory / Replay scene and saves the OBS replay buffer, so the round is already on disk. You never touched a key; the broadcast told your story for you.

Node setup · The Clutch

Trigger

Chat Velocity < 0.5 / s

the room holds its breath

Action

Scene = Focus Mode

cut the distractions

Trigger

Chat Velocity > 40 / s

chat detonates

Action

Scene = Victory / Replay + Save Replay

ride the moment

Scenario 04

The Snack Break: A BRB Scene and Muted Mic When the Room Goes Quiet

You step away for thirty seconds to grab food. Thirty seconds becomes five minutes. You forgot to hit the BRB screen — so viewers are watching an empty chair and a paused game, and the energy you spent all stream building quietly drains away.

A rule built on a very low chat-velocity threshold catches it: when chat falls almost silent, the Action nodes switch to your AFK / Be Right Back scene and mute your mic input in OBS, so the kitchen stays off-stream. Set the threshold low enough that only a genuinely empty room trips it — a normal lull should not — and when chat picks back up, streamerOS returns to the scene you left.

Node setup · Snack Break

Trigger

Chat Velocity < 0.1 / s

the room goes quiet

Action

Scene = BRB + Mute Mic

a tidy “back soon”

Scenario 05

The Jump Scare: Saving the Clip the Moment Chat Floods

The horror game finally gets you. You scream, you flinch clean out of frame — and chat instantly floods with OMEGALUL and LMAO. It’s a perfect clip moment, the kind that makes the rounds the next day, and right now it’s slipping past completely unmarked.

The flood itself is the signal: chat velocity jumps far above your normal pace. A Trigger on that spike saves the OBS replay buffer, so the last few seconds are already on disk, and sets your Aura overlay to its Hype mood for the moment. Viral Moments independently drops a timestamped marker on the spike, so the clip is easy to find after the stream. The bit lands on its own, and you just keep playing.

Node setup · Jump Scare

Trigger

Chat Velocity > 30 / s

the laughter flood

Action

Save Replay Buffer

the clip is already saved

Action

Aura Mood = Hype

the overlay reacts

Key concepts

streamerOS Automation Glossary: Key Terms Defined

Auto-Hype Director

The Auto-Hype Director is streamerOS’s visual, node-based automation engine. It links Trigger nodes (chat velocity and Super Chat amount, each above or below a threshold you set), Logic nodes (AND / OR), and Action nodes so that Open Broadcaster Software (OBS) Studio scenes switch automatically the instant your stream peaks — without touching a hotkey.

Chat Velocity

Chat velocity is the rate of incoming chat messages over a short rolling window, such as messages per second. streamerOS treats a sharp rise in chat velocity as a real-time hype signal, and a drop below a low threshold as a lull, using both to drive automatic scene changes.

Interprocess Communication (IPC)

Interprocess Communication (IPC) is the set of operating-system mechanisms that let two separate local applications — such as streamerOS and Open Broadcaster Software (OBS) Studio — exchange data and commands directly on the same machine, without routing anything over the internet.

Local Loopback Adapter

A local loopback adapter, reachable at the IP address 127.0.0.1, routes network traffic entirely inside your own computer’s memory. streamerOS communicates with OBS Studio over this loopback connection, so scene-switch commands never leave the device and execute in milliseconds.

Zero-Cloud Architecture

Zero-cloud architecture means the software runs and stores all of its data on the local machine, with no remote server, user account, or backend. For streamerOS, your chat, audio, credentials, and automation rules never leave your computer.

Write your own plays.

These are just five. The Auto-Hype Director is a blank canvas — wire your own triggers, logic, and actions, and let the broadcast run itself.

Launching February 2027