Community interaction · Moments

Channel Moments

Turn live viewer calls into one moderated Twitch clip or marker. Then publish safe stream and weekly recaps.

The Sample Channel stream recap on a narrow screen with an approved Community clutch save and a recorded vote. — Moderators work at /moments. Approved entries appear in channel and stream recaps. They also appear in weekly recaps.

Prepare a live channel

Select the channel.
Open Moments at /moments. Captures require a Twitch-reported live channel and the selected channel's Twitch connection.
Set the Merge window from 15 to 300 seconds. 90 seconds is the default. Calls inside that window join the same stream moment and keep each contributor and suggestion.
Select one reward option:
Reward option: No reward.
Reward option: First viewer to request.
Reward option: All contributing viewers.
Set the amount. Choose whether a confirmed clip failure can use a stream marker.
Save settings.
Check that the page shows Live stream with a stream identity.
Invite viewers to capture.

Capture a candidate

A viewer uses !moment <suggested title> | category=<suggested category>. !clip accepts the same form.
A moderator can use Capture now. BlokeBot first requests a Twitch clip. BlokeBot uses marker fallback only after a confirmed clip failure and only when you enable it.
Each call returns a public moment number. Repeated or concurrent calls for the same live moment converge. They do not create duplicate Twitch actions or rewards.

Moderate public metadata

Public recaps show only the listed public recap fields.

Reject keeps its reason private. Merge uses another moment number.

Only approved moments appear in public recaps.

In Candidates, review the applicable capture state.
Review the contributor count and viewer suggestions.
Set Public title and Category.
Select Save details.
Select Approve.
Use Open on Twitch to check available media.

Capture state: Creating clip.
Capture state: Clip ready.
Capture state: Marker ready.
Capture state: Could not create clip.
Public recap field: approved title.
Public recap field: category.
Public recap field: counts.
Public recap field: Twitch link.
The moderator view retains Moderator note.
The moderator view retains rejection reason.
The moderator view retains audit text.
The moderator view retains Twitch failure details.

The Sample Channel public bounty shows an attached approved Moment on a narrow screen. Its public-safe title and Twitch media link are visible. — Authorized staff attach by reference in the destination. Viewers receive only the Moment's current approved public-safe fields.

Attach approved Moments to progression

The destination context stays visible. This context distinguishes the confirmed result from another match.

Detachment neither copies nor deletes these records.

Approve the Moment for the selected channel first.
As the channel owner or permitted moderator, open the destination for the attachment.
Open the destination's Moments section.
Select a same-host approved Moment.
Attach it.
Use Remove in the same section to detach the reference.

Moments still owns the Moment.
Moments still owns its Twitch clip or marker.
Moments still owns the moderation history.
Attachment destination: a bounty.
Attachment destination: an achievement.
Attachment destination: a confirmed tournament match.
A bounty attachment inherits Moments.
A bounty attachment inherits Bounties.
A bounty attachment inherits the effective Points requirement for Bounties.
An achievement attachment inherits Moments and Community progression. A match attachment inherits Moments and Tournaments & leagues. This feature does not add an attachment switch.
Discovery requires all these conditions:
The Moment must be approved.
The Moment must belong to the same host.
The Moment must be currently public-safe.
BlokeBot suppresses unavailable Moments from management.
BlokeBot suppresses unavailable Moments from public destination pages.
BlokeBot suppresses unavailable Moments from events.
BlokeBot suppresses unavailable Moments from downstream presentation.
If the same source Moment returns to Approved, a retained link becomes visible again. Every parent gate must also be available. BlokeBot does not replay an attach event or suppressed work when it reappears.
Public destinations can show the current title.
Public destinations can show the current category.
Public destinations can show the current Twitch media link.
These Moment fields remain private: moderator notes and rejection reasons.
These Moment fields remain private: failure detail and internal IDs.
These Moment fields remain private: audit text.
If a parent is off, the embedded section shows Channel setup recovery.
If a parent is off, BlokeBot blocks discovery.
If a parent is off, BlokeBot blocks changes.
If a parent is off, BlokeBot blocks public relationships.
If a parent is off, BlokeBot blocks events.
If a parent is off, BlokeBot blocks overlays.
If a parent is off, BlokeBot blocks automations.
Valid links remain saved and reappear from current state after re-enable without replay.

Read Twitch states before you retry

Creating clip means that Twitch continues to prepare the clip. Reload the same candidate later. Do not capture again just to force an answer.
An ambiguous outcome means Twitch did not confirm whether its request completed. BlokeBot preserves that uncertainty and does not create a fallback marker from it.
If the state is Offline, wait for a live stream.
If Twitch reports that clips or VODs are disabled, correct that setting or continue with no marker fallback.
If access is unauthorized, reconnect the selected channel account.
If the failure continues, keep the candidate.
Include the channel in the information for the server owner.
Include the moment number in the information for the server owner.
Include the stream identity in the information for the server owner.
Include the approximate time in the information for the server owner.
Include the Twitch message in the information for the server owner.
Never send tokens or private moderation text.