Automation Scenarios

What this page is

Automation → Scenarios is where a viewer event is wired to a chain of actions: "Configure reaction rules for Twitch rewards and timers". One scenario holds a list of Triggers and a Step chain, and groups let a condition switch a whole set on and off.

How to set it up

1. Open Automation → Scenarios and press Create Scenario in the header. An empty page reads "No scenarios found. Create your first scenario above."
2. Fill in Scenario Name and pick a Group — No Group is a valid answer, and [ Create new group... ] makes one on the spot.
3. Triggers is the list of ways in: "Any of these starts the same chain of steps. Add a second one instead of copying the scenario." + Trigger opens Add Trigger with a Trigger Type:
   • Channel Reward — pick from -- Choose Reward --, where rewards are grouped by Twitch and Kick and each shows its cost. -- Enter ID manually -- opens a field for the id instead. An empty list says "No rewards found. Please connect Twitch or check your Twitch Dashboard."
   • Panel Button — pick a Panel Button Slot. A slot is one of the buttons on the Panel: Buttons tile of the Control Panel; pressing that button runs this scenario.
   • Donation — Amount condition is Any donation, From this amount and up, Exactly this amount or Between two amounts, with Amount and Up to beneath it. Count donations from lists your donation connectors as tickboxes: "Unchecked platforms are ignored by this scenario."
   • Subscription — Which subscriptions: Any subscription, Only new ones, Only renewals.
   • Gifted subscriptions, Raid and Bits (cheer) each take a minimum — Minimum subscriptions gifted at once, Minimum viewers in the raid, Minimum bits — and zero means any.
   • New follower, Stream started and Stream ended have no settings at all: "Fires once when the stream state changes. There is nothing to configure." Done puts the trigger into the list; a saved trigger can be reopened or removed there.
4. Step chain is what happens. + Delay drops in a Delay step with a seconds box; + Action opens Add Action. Empty, it reads "No steps yet. Add an action or a delay."
5. The Action list comes in two groups. OBS holds OBS: Switch scene (Select Scene), OBS: Show or hide source (Select Scene, Select Source, What to do — Show source, Hide source, Toggle), OBS: Source filter (plus Select Filter and Filter State — Enable filter or Disable filter), OBS: Mute or unmute audio (Audio input, then Mute, Unmute or Toggle) and OBS: Audio input volume (Audio input and a Volume slider).
6. strAImer holds Play Sound (Select Sound — every item shows its length and a play button for Preview — and Volume), Say it out loud and Send chat message (Text, and for chat a Where to send — All connected chats, Twitch, YouTube or Kick), Smart Plug and Create Twitch clip. Done adds the step.
7. Under Text are the chips {user}, {amount}, {reward} and {message}: "Click a name below to insert it. It is replaced by what triggered the scenario; an unknown name is left as is."
8. Smart Plug asks for the plug and What to do: Turn on for a while (which adds Duration, sec), Turn on and leave it on or Turn off. With no plugs it says "No plugs added — see Devices → Shelly".
9. Steps run top to bottom, and each row has arrows Up and Down, plus Edit and Delete. Press Save to store the scenario.
10. The card in the list shows a tag per trigger, the whole chain and the number of steps. Beside it: the switch that turns the scenario on and off, Test run, Duplicate (the copy opens for editing at once, named " (copy)"), Edit and Delete, which asks "Delete this scenario?"
11. Create Group in the header makes a group. Give it a Group Name; scenarios are put into it by the Group field in step 2, and a group with none in it says "No scenarios in this group yet."
12. Automatic control in the group makes the group follow a Condition Type: Source visibility on scene, Active scene, Source visible on current scene or Auction accepts channel points. The first three ask for Select OBS Scene and Select OBS Source; each explains itself under the picker, for instance "The condition holds while the selected scene is live."
13. What the condition controls is the list underneath: "While the condition holds, everything listed here is on; once it stops holding, it is off." The locked first line is always there — "Scenarios in this group do not fire while the condition is not met." + Add adds Twitch channel point rewards, a tickbox list of your rewards, and Remove takes the entry away.
14. In that list, a reward you created by hand on the Twitch site is greyed out, marked "created outside strAImer" and cannot be ticked. Twitch lets an app switch only the rewards it created itself, so such a reward would be refused every time — the group would say it is on while nothing changed on Twitch. To automate one, recreate it as a managed reward on Automation → Channel Rewards — the guide "Channel Points Manager" covers that page. One that is already ticked can still be unticked, so an old setting is not stuck.
15. A condition that changes does not switch the group at once: the new state has to hold for three seconds first. A source that blinks on and off again inside those three seconds changes nothing — the switch that was waiting is dropped and the group stays as it was. That is deliberate: a source nobody had time to see on stream is no reason to open the rewards, and switching a group means one write to Twitch per reward in it, so a flickering source used to fire dozens of them in a row. The wait applies only to what comes from OBS. Turning Automatic control on or off, pressing Save, the auction opening or closing channel points, and OBS losing the connection all take effect immediately.
16. In the list a group header carries the Auto tickbox, the group switch, Condition Settings and Delete; clicking the header itself folds the group. Deleting asks "Delete group "{name}"? All nested scenarios will be safely moved to the "No Group" section."

What it cannot do

• Scenes, sources, filters and audio inputs are read from OBS; without it those pickers have nothing to offer.
• The chain has no branching and no conditions of its own: steps run in order, top to bottom. Conditions live on the trigger and on the group.
• The trigger types are exactly the ten in Trigger Type. There is no clock trigger and no repeating timer — Delay is a step inside a chain, not a way to start one.
• A group's hold over its own scenarios cannot be switched off: "This is what a group is, so it cannot be turned off separately."
• Twitch channel point rewards is the only entry + Add offers under What the condition controls, and only rewards strAImer created itself can be put under it.
• With Automatic control on, the group's own switch is locked and reads "Managed automatically by a condition".
• The three seconds a condition has to hold before the group follows it are fixed. There is no field for them and no way to make an OBS condition switch the group instantly.
• Amounts are compared in your base currency (Settings → Localization), and a donation that could not be converted does not fire the scenario. Exactly this amount "only works for donations already in your base currency: after conversion the amount lands on kopecks and practically never matches."
• Duration, sec exists only for Turn on for a while; the other two plug actions are ended by the chain, not by a countdown.