Skip to content

Blueprints

A scenario you can point at

Something happens on the left — the stream reacts on the right. If a step fails, you see the block. No guessing which bot went quiet.

How it looks in practice

A $5 donation. If it’s over the threshold — show an alert and ping mods on Discord. Three blocks. One story.

The blocks a scenario is made of

Same colors and names as in the app. Nothing new to memorize.

Triggers

A chat command, donation, follow, sub, resub, raid, channel points, timer or schedule.

Conditions

Amount, role, cooldown, comparisons, extra branches. Yes goes one way, no the other.

Actions

Show an alert, reply in chat, send HTTP, play a sound, write to Discord or Telegram.

Data

Names, amounts, counters, lists, templates. Check text and do the math without opening a code editor.

Examples

How it looks on a real stream

A tip and a thank-you

A donation arrives. Past the threshold — an OBS alert and a chat line with the name.

A subs-only command

!song checks the role, waits 30 seconds between calls and replies with the current track.

A raid

An alert on screen, a short welcome in chat and a Discord ping so the team doesn’t miss the spike.

A donation goal

Every tip adds to one variable. The overlay widget reads the same one. The counter and the thank-you stay in sync.

When blocks aren’t enough

The Windows app has a code mode: you write the scenario as text and it runs locally. That’s a backup for rare cases, not the default start. Free includes a short code scenario; Pro has no cap.

Browser and app

You build and save scenarios in the dashboard. The Veris app runs them during the stream. The interface stays light, and reactions stay steady while you’re live.

Put the first alert on your stream

Open the dashboard or download Veris for Windows. A thank-you for a donation takes a few minutes to build.