Rules and cooldowns
Decide who can trigger an event, how often, in what order, and what a chat command costs.
Rules keep an event fair and calm. Limit it to subscribers or moderators, give each viewer a cooldown, line actions up so they take turns, or charge points for a chat command.
Open an event's rules
In the event editor, click Settings under the action list. The line beside it sums up the rules while they are closed, such as Everyone or a cooldown per viewer, so you can check an event without opening them.
A Blueprint event keeps the same rules. Select its Event node, change the rules in Details, then click Apply trigger.
Choose who can trigger it
Under Who can trigger this, pick one or more roles: Followers, Friends, Subscribers, Super Fans, Moderators, Fan club members or Top gifters. With nothing picked, everyone can. Top gifters reads this stream's gift leaderboard; set How many top gifters to choose how far down it goes. On YouTube, a channel member counts as a subscriber.
Add names to Always allowed to let those viewers in whatever their roles, and to Never allowed to keep them out. Type a name and press Enter, or paste a whole list.
Roles come from each platform
If a platform doesn't report a viewer's roles, an event limited by role stays quiet for that viewer instead of firing for everyone.
Set a cooldown
Under Cooldown, set Per viewer (seconds) so one viewer can't set the event off again right away, and For everyone (seconds) to space it out for the whole room. Click a preset, or type your own number.
While cooling down decides what happens to a trigger that arrives too soon: Ignore the trigger, or Run it when the wait ends. The second keeps one waiting trigger per viewer and drops the rest, so a long wait never ends in a burst.
A cooldown is different from the rate limit under Advanced Settings:
Counts triggers. A gift combo uses one cooldown and still runs every repeat. Can apply per viewer.
Counts action runs across everyone: at most Max Triggers runs in each Time Window (seconds). Five every 60 seconds to start.
Set rules for every event
SettingsAutomation & rulesViewer controls holds rules that apply everywhere:
- Blocked viewers can't trigger actions, use text to speech or appear in overlay chat.
- Seconds between triggers, per viewer is a cooldown on every event. Gifts are exempt.
- Trigger history resets milestones, first chats and running cooldowns with Reset history…, for a fresh start.
Queue actions so they take turns
Without the queue, an event's steps start the moment it fires, even if another event is still running. Turn on Action Queue and the event waits for earlier actions to finish.
- Queue lane (same name runs in order): events in one lane take turns. Events in different lanes run side by side, one at a time in each.
- Queue priority (higher runs first): a waiting run with a higher number jumps ahead.
- Prioritize by gift diamond value: bigger gifts jump ahead of smaller ones.
- Discard queued runs after seconds: a run that waits too long is dropped, so a reaction never plays minutes late.
Add Delay (ms) under Advanced Settings to hold an event for a moment before it starts. A Blueprint event has no such field; it waits with a Delay node instead.
Use chat arguments
With a Chat message trigger set to Command and arguments, the words
after the command reach your steps. For !spin 90, {arg1} is 90, and
{args} is everything after the command.
Use the first command argument for model movement goes one step further: choose Rotation (°), Size, Position X or Position Y, and the first word sets that value in the event's Move Model step. Viewers then decide how far the model turns. If the first word isn't a number, the event doesn't run.
Charge points for a command
Set Points cost per command on a chat event, and a viewer spends that many points each time they use it. A viewer without enough points gets nothing. If the run is dropped before it starts, the points go back.
Viewers earn points from likes, chat, follows, gifts and more, at the rates in SettingsPoints. The !scream for 100 points recipe is a ready-made example.