Scenarios: when this happens, do that

What starts a scenario

A trigger is the thing that happened. Today there are two, and they cover the cases that matter most on a live stream.

• A channel point reward being redeemed — the viewer pays, the scenario fires.
• A button on the control panel — the same automation, run by you, for the moments a viewer should not be the one deciding.

What a scenario can do

Actions come from the modules you have installed, so the list grows as you add them.

• Switch an OBS scene, show or hide a source, turn a filter on or off.
• Play a sound from your own folder into the stream.
• Switch a Shelly smart plug on — the lamp, the fan, whatever is plugged in.
• Turn an effect on for a set number of seconds and take it back automatically, which is what makes a paid effect a moment rather than a permanent change.

Seeing what happened

Automation that works silently is indistinguishable from automation that is broken. Two tiles make it visible on the control panel.

• The scenarios tile shows what is running right now and what fired a minute ago.
• A repeat button re-runs an effect that jammed — the usual case being OBS not answering for a second.
• The buttons tile holds your own named slots, so a scenario is one press away while you play.

What it is made of

Each part is a separate module: you install only the ones you need, and any of them can be removed without breaking the rest.

Getting started

1. Install the modules the actions need — OBS control, smart plugs. Sound needs no module: the app plays it itself.
2. Create a scenario: pick the trigger, add the actions.
3. For an effect that should not stay on, set how many seconds it lasts.
4. Add the scenarios tile to the panel so you can see it fire.

Works together with