Community interaction · Raids

Use the raid and collaboration hub

Manage raid collaboration.

Connect Twitch and enable the feature

The feature card saves the change immediately. Each channel starts with this switch off.

Connect the selected Twitch channel.
Ask its owner or permitted moderator to turn on Raid & collaboration in Channel setup.
As the owner or a permitted moderator, configure the welcome settings and shortlist.
Operate the hub.
As a viewer, do not approve channels or start provider actions.
If Confirm and start raid reports no authority, ask the channel owner to reconnect Twitch with raid management access.

Choose whether the welcome message runs.
Write the bounded tokenized message.
Set the duplicate-prevention window.
Twitch EventSub supplies the source channel and one total viewer count. BlokeBot does not infer or store individual viewer attribution.
Duplicate deliveries create one history entry. Repeated raids within the configured window do not repeat the welcome sequence.
The history records welcome and shoutout outcomes.
A cooldown records an explicit non-success.
An offline state records an explicit non-success.
A provider rejection records an explicit non-success.

Automatic raid shoutouts start off.

Open Settings.
Turn on automatic raid shoutouts.
Set the minimum viewer count.
Turn on Only shoutout approved channels to restrict shoutouts to channels that you approved.
Choose either a Native Twitch shoutout or a Chat message.
For a chat message, select one message kind.
For Pinned, set a duration from 30 to 1,800 seconds, or until stream end.
For Announcement, select one of the colors below.
Write the message.
Check its preview.
Save the settings once.

Message kind: Regular.
Message kind: Pinned.
Message kind: Announcement.
Announcement color: Default.
Announcement color: Blue.
Announcement color: Green.
Announcement color: Orange.
Announcement color: Purple.
Message tokens include {twitch_handle} and {display_name}.
Message tokens include {channel_url} and {viewer_count}.
Message tokens include {last_game|fallback} and {stream_title|fallback}.
Last game and stream title require an inline fallback because Twitch can omit them.
BlokeBot processes each eligible raid once. It does not replace a failed native shoutout with a chat message.
BlokeBot does not replace a failed announcement with a regular message.

Enter a live Twitch name with viewers in Send a shoutout.
Wait for the result.
Use the displayed cooldown before another send.
Select Approve channel on a history entry to add that channel to Approved channels. After approval, the action disappears.
Automatic shoutout outcomes shows the newest raid results and reasons for a skipped or incomplete send. Twitch can skip native shoutouts during its cooldown.
Twitch can send a Pinned message but fail to pin it. The outcome reports both parts.
Before the next raid, correct the connection or permission in the outcome. Do not retry or use a fallback for an earlier raid.
If BlokeBot requests a bot account reconnection, restore its moderator role. Then reconnect it from Channel setup.

Add Twitch channels to Approved channels only after this channel makes a deliberate approval decision.
To add another source, turn on Include followed live channels.
When BlokeBot requests permission to read followed channels, reconnect the channel owner.
Treat a Twitch follow only as discovery evidence.
If required, restrict the language and categories.
Set the recent outgoing-relationship gap.
Save the settings.
Review the live candidates and each exclusion reason.
Use an approved clip only if Twitch confirms its channel and an age of 30 days or fewer.

Shoutout uses the shared native Twitch boundary.
Before the send, BlokeBot repeats the authority check.
Before the send, BlokeBot repeats the live-state check.
Before the send, BlokeBot repeats the cooldown check.
Before the send, BlokeBot repeats the duplicate check.
Select Prepare raid to open confirmation for the live shortlist channel. This action does not call Twitch.
Only Confirm and start raid calls the outgoing provider after new feature and Twitch authority checks. The hub never starts a raid automatically.
Before each shortlist action, BlokeBot checks the stable channel ID again.
Before each shortlist action, BlokeBot checks the source again.
Before each shortlist action, BlokeBot checks the live state again.
Before each shortlist action, BlokeBot checks the filters again.
Before each shortlist action, BlokeBot checks the relationship gap again.
If the target goes offline or becomes ineligible, refresh the hub. Make a new host decision.
If authorization expires or the provider declines, use the same recovery. Do not treat the previous preparation as authority.

Turn off Raid & collaboration to remove discovery.
With Raid & collaboration off, BlokeBot blocks the hub and EventSub subscription before effects.
With Raid & collaboration off, BlokeBot blocks reconciliation and the welcome sequence before effects.
With Raid & collaboration off, BlokeBot blocks history changes and shortlist checks before effects.
With Raid & collaboration off, BlokeBot blocks shoutout handoff and provider calls before effects.
BlokeBot retains private settings.
BlokeBot retains approved channels.
BlokeBot retains history.
The signed-in direct route points to Channel setup.
Re-enable the feature to establish current subscriptions and accept new work.
BlokeBot does not replay suppressed events and welcome steps.
BlokeBot does not replay suppressed shoutouts and timers.
BlokeBot does not replay suppressed queued work and raid actions from the host.
If raids remain absent, check the selected channel ID and Twitch connection. Do not rely on a login fallback.
If native actions fail, reconnect the account for the owning channel with the requested permission.