Automation Scenarios

What this page is

Automation → Scenarios wires an event to a chain of actions: a viewer redeems a reward, and OBS switches scene, a sound plays and the bot writes a line in chat. Its own description puts it as "Configure reaction rules for Twitch rewards and timers".

Three things make up a scenario, and it helps to keep them apart:

• Triggers — the ways in. Several triggers can start the same scenario.
• Step chain — what happens, top to bottom. No branching, no conditions.
• Group — an optional wrapper that can switch a whole set of scenarios on and off by itself, based on what OBS is showing.

Building a scenario

1. Create it

Create Scenario in the header. An empty page reads "No scenarios found. Create your first scenario above." Fill in Scenario Name and pick a Group — No Group is a valid answer, and [ Create new group... ] makes one on the spot.

2. Add a trigger

Triggers is the list of ways in, and the page says why there is a list rather than one: "Any of these starts the same chain of steps. Add a second one instead of copying the scenario." + Trigger opens Add Trigger, and Trigger Type offers twelve:

On the three minimums, zero means any. The last three say so themselves: "Fires once when the stream state changes. There is nothing to configure."

Done puts the trigger into the list, where a saved one can be reopened or removed.

Two guards sit in the same window, and both start switched off. Do not run more often than, seconds is the pause between runs: "Zero means no limit — every event runs the scenario. A follow-bot raid sends hundreds of follows a minute, and without a cooldown each one writes to chat, speaks and clips." Once per viewer per hour is the other half — the same person cannot start it again within the hour. They are shown only for the ways in that a crowd can push: a reward, a panel button, the edges of a stream, a spoken phrase. A scenario written before they existed behaves exactly as it did.

An empty reward list says "No rewards found. Please connect Twitch or check your Twitch Dashboard."

3. Donation triggers have two filters

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. A newly installed donation connector counts right away."

Amounts are compared in your base currency (Settings → Localization), and a donation that could not be converted does not fire the scenario at all. That is also why Exactly this amount is a trap for anything arriving in another currency — the page warns about it in as many words: "An exact match only works for donations already in your base currency: after conversion the amount lands on fractions of a unit and practically never matches."

4. Build the chain

Step chain is what happens. Empty, it reads "No steps yet. Add an action or a delay."

• + Delay drops in a Delay step with a seconds box.
• + Action opens Add Action, and the list comes in two groups.

A Delay also decides what a second trigger does while the chain is still waiting. A chain that switches something on and then off is extended: the deadline moves by the length of the delay and the actions are not run again — buying the effect twice buys twice the time, and repeating the switch would have turned it off. A chain that says or writes what the trigger brought — {message}, {user} — runs once per trigger instead: three redemptions in five seconds are three separate runs, so nobody's message is dropped. Nothing to set here; the app decides by what the steps do.

OBS — needs the OBS connection, and the pickers are filled from OBS itself:

• 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 — the same plus Select Filter and Filter State (Enable filter, Disable filter).
• OBS: Mute or unmute audio — Audio input, then Mute, Unmute or Toggle.
• OBS: Audio input volume — Audio input and a Volume slider.

strAImer — everything the app does itself:

• Play Sound — Select Sound, where every item shows its length and a play button for Preview, plus Volume.
• Say it out loud and Send chat message — both take Text; the chat one also takes Where to send (All connected chats, Twitch, YouTube or Kick).
• Smart Plug — 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".
• Create Twitch clip.

Under Text sit 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."

5. Order and save

Steps run top to bottom. Each row has arrows Up and Down, plus Edit and Delete. Save stores the scenario.

The card in the list then shows a tag per trigger, the whole chain and the number of steps. Beside it: the on/off switch, Test run, Duplicate (the copy opens for editing at once, named " (copy)"), Edit and Delete, which asks "Delete this scenario?"

Groups, and letting OBS switch them

A group is a folder that can also be a switch. Create Group in the header makes one; give it a Group Name, and scenarios join it through the Group field. An empty group says "No scenarios in this group yet."

Automatic control

Automatic control makes the group follow a Condition Type:

• Source visibility on scene
• Active scene
• Source visible on current scene
• Auction accepts channel points

The first three ask for Select OBS Scene and Select OBS Source, and each explains itself under the picker — for instance "The condition holds while the selected scene is live."

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 first line is locked and 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 an entry away.

Why some rewards are greyed out

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 — and the group would report itself as 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 never stuck.

The three-second wait

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 pending switch 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.

The group in the list

A group header carries the Auto tickbox, the group switch, Condition Settings and Delete; clicking the header folds the group. Deleting asks first and reassures: "Delete group "{name}"? All nested scenarios will be safely moved to the "No Group" section."

What it cannot do

• No branching and no conditions inside a chain. Steps run in order, top to bottom. Conditions live on the trigger and on the group, nowhere else.
• No clock trigger and no repeating timer. The trigger types are exactly the twelve above; Delay is a step inside a chain, not a way to start one. Repeating messages are a different page — Chat Bot → Chat Timers.
• Scenes, sources, filters and audio inputs are read from OBS. Without the OBS connection those pickers have nothing to offer.
• 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."
• Only rewards strAImer created can be put under a condition. Twitch channel point rewards is the only entry + Add offers under What the condition controls.
• With Automatic control on, the group's own switch is locked and reads "Managed automatically by a condition".
• The three seconds are fixed. There is no field for them and no way to make an OBS condition switch a group instantly.
• Duration, sec exists only for Turn on for a while. The other two plug actions are ended by the chain, not by a countdown.