Shoutout

Puts another streamer in the spotlight. Type your shoutout command — !so pixelpanda — and the overlay shows their profile picture, your message and one of their Twitch clips. It can also do it on its own when someone raids you, or when a streamer from your Streamer.Bot user group writes in your chat.

Platforms: Twitch (switched off: the page says so and no browser source runs the widget)

Action pack: needed — Stream UI - Backend fetches the streamer's picture, last game and clips, checks the user group and sends Twitch's shoutout. See Who needs what.

How it works

• Three ways to start one: your command, a raid (Shout out raiders), or the first message of a member of a Streamer.Bot user group (Group members at their first message).
• One shoutout at a time. Others wait in a queue and play one after the other. A channel already on screen or in the queue is not added twice.
• A clip from their channel. The widget picks a random clip from the last year (from all time if the channel has none), and plays it with its title and who clipped it. When it ends, the shoutout leaves.
• No clip, no problem. When the channel has no clip, or its video can't play, the shoutout shows the picture and header alone, for Time on screen without a clip.
• Chat and Twitch's shoutout are sent by the overlay that runs the actions only, never by the preview on the website, so testing never posts in your chat. When the shoutout is shown in another overlay, that overlay plays the clip and the one that runs the actions sends the messages without showing anything. → Which overlay runs the actions
• Show it in one overlay. Each overlay showing it plays the clip, sound included — the Layout tab warns you.

The page

The widget's page works like a small app:

• Settings, Style and Controls, the tabs over the editor, switch what it shows.
• The Settings tab has one section, Shoutout settings, so its fields fill the main area with no column on the left, in five parts: Player header, Player footer, Sound, Chat message and Triggers (Commands, Raids and First message). The Style and Controls tabs list theirs in a column on the left: click one to edit it in the main area.
• Widget preview, the panel against the window's right edge: the preview, the test buttons and the widget's own URL. The arrow at the top folds it to a slim rail. Drag its left edge to widen it, up to half the window; it keeps its width. Widget shows the widget in its position, cut from the canvas as your browser source draws it; On canvas, the whole canvas.

How to set it up

Settings

Player header

Player footer

Sound

Chat message

Triggers

Header and Chat message can use these variables (listed under each field on the page):

Style

Shoutout and Clip Autoplayer share one clip player, so they look alike until you change a field of one of them. On the Style tab, the Styles column lists the elements: pick one to style it in the main area, highlighted on the preview; Text opens a column of its three texts. See Appearance.

Default position

Position Center, automatic width, size 100 %. The player's size is the Background width on the Style tab; the position is changed on the Overlay builder's Layout tab.

Streamer.Bot events it listens to

Controls

On the widget page's Controls tab:

• Controls, the column on the left, lists Pause, Resume, Skip shoutout and Clear queue, each with the names of its triggers. Pick one to see its triggers in Trigger list, beside it.
• Trigger list: the Streamer.Bot triggers that do it. Add trigger adds one, conditions included → Triggers and conditions.
  • Pause — default: Twitch Stream Offline.
  • Resume — default: Twitch Stream Online.
  • Skip shoutout, Clear queue — none by default.
• The main area shows Shoutout: Running or Paused, with the buttons Resume and Pause, then the other buttons, all also in the controls window:

The buttons need Streamer.Bot connected.

Pause and resume

While paused, nobody is shouted out: no clip, no chat message, no Twitch shoutout. Your command, raids and group members writing meanwhile are ignored, not queued, so resuming never plays a backlog. Group members who write while it is paused count as shouted out until the browser source reloads.

The state is kept in Streamer.Bot, in the persisted global streamUi.off.shoutout (1: paused; 0 or none: running), so it lasts until you resume, even if the browser source reloads, and every overlay follows it at once. Your own actions can pause or resume the widget too, with a Global (Set) sub-action on that variable. The buttons and triggers need Stream UI - Backend.