BlokeBotHelp & guides
Open the BlokeBot dashboard

Community progression · Seasons

Community progression

Turn supported channel events into individual or communal progress. Keep standings and viewer-earned rewards beyond the season.

The Sample Channel Community progression page shows new-season dates and Public visibility. Private moderator notes are also visible. The Sample Channel public season page that shows named standings and current viewer quest progress on a narrow screen.
The management page starts the season contract. The public page makes named standings and progress visible when the season is Public.

Choose authority and visibility

Public seasons show Twitch display names and recorded logins in standings.

The feature card saves the change immediately.

The channel owner or permitted moderator also controls lifecycle and reset schedules.

Private moderator notes stay on the management page in both modes.

  1. Select the channel.
  2. Open Channel setup.
  3. Turn on Community progression under Chat tools.
  4. Choose Public to publish participant Twitch identities and progression, or Hidden to publish no progression data.
  • Participant progress comes from authenticated Twitch chat.
  • Supported Twitch events can also supply participant progress.
  • Supported BlokeBot events can also supply participant progress.
  • A channel owner or permitted moderator creates seasons.
  • A channel owner or permitted moderator creates definitions.
  • A channel owner or permitted moderator creates rewards.
  • Public seasons never expose raw provider payloads.
  • Public seasons never expose provider credentials.
  • Public seasons never expose internal IDs.
  • Public seasons never expose moderator notes.
  • Public seasons never expose internal audit material.
  • Public seasons also show equipped rewards.
  • Public seasons also show unlock history.
  • Public seasons also show archived history.
  • Public seasons show individual quest progress.
  • Public seasons show individual achievement progress.
  • Public seasons show communal goals.
  • Public seasons show completions.

Create the season contract

BlokeBot does not accept arbitrary CSS.

BlokeBot does not count progress events outside the open season's start and end.

  1. Create a Draft season.
  2. Set its name and public description.
  3. Set its UTC start and end.
  4. Select Public or Hidden visibility.
  5. While it is Draft, add host-scoped rewards from the supported kinds.
  6. Select only supported presentation tokens.
  7. Add Quest or Achievement definitions.
  8. Select per-viewer or channel-wide communal progress.
  9. Select One-time or Repeatable completion.
  10. Select a target.
  11. Select optional reward keys.
  12. Select one supported event rule.
  13. Open the season only after the definition and reward inventory is complete.
  • Reward kind: Title.
  • Reward kind: Badge icon.
  • Reward kind: Cosmetic accent.
  • Typed rules cover chat messages and follows.
  • Typed rules cover subscriptions and cheers.
  • Typed rules cover incoming raids and reward redemptions.
  • Typed rules cover completed bounties and predeclared external achievement grants.
  • Definitions allow only supported combinations of these dimensions:
  • Definition dimension: rule.
  • Definition dimension: owner.
  • Definition dimension: increment.
  • Definition dimension: filter.
  • A rejected combination remains unsaved. Choose a compatible option. Do not treat the event as generic text.

Follow individual and communal progress

  • A host-scoped event that matches advances each applicable active definition once. Event-value rules use the supported numeric value, while occurrence rules add one.
  • Per-viewer definitions update that participant's current progress.
  • Per-viewer definitions update that participant's completions.
  • Per-viewer definitions update that participant's standings.
  • Communal definitions combine events that qualify into one channel-wide goal.
  • Participants use !progress for a short view of current Public season progress.
  • Participants use /community/{channel} for standings.
  • Participants use /community/{channel} for goals.
  • Participants use /community/{channel} for completions.
  • Participants use /community/{channel} for rewards.
  • Authorized staff can manage Hidden seasons. The !progress command reports that progression is hidden. The public route publishes no season data.
!progress
!equiptitle <reward-key>
!equipbadge <reward-key>
!equipaccent <reward-key>

Schedule repeatable resets

  • Daily and weekly repeatable definitions use the channel time zone.
  • These definitions also use the configured local time.
  • Weekly resets also use the configured weekday.
  • The page shows the next UTC reset.
  • A local time in a daylight-saving gap moves forward to the first valid instant. A local time in an overlap uses its first occurrence and does not reset again at the second.
  • After downtime, BlokeBot rolls at most once into the current period. It does not replay every missed daily or weekly period.
  • If you save a schedule change during an active period, BlokeBot closes that period. It resets active repeatable progress. Select Reset active progress now before Save schedule and roll over immediately. The confirmed change applies once across retries and multiple instances.

Grant and equip persistent rewards

  • A completion grants all its configured completion rewards atomically:
  • Completion reward: points.
  • Completion reward: a title.
  • Completion reward: a badge icon.
  • Completion reward: a supported cosmetic accent.
  • A retry of the same completion does not grant twice.
  • Viewer unlocks survive season closure and archival.
  • The chat commands above let a viewer equip one unlocked title for this host.
  • The chat commands above let a viewer equip one unlocked badge for this host.
  • The chat commands above let a viewer equip one unlocked accent for this host.
  • An equip action checks reward ownership and host scope. It changes the current selection and does not rewrite the immutable season completion record.
The Sample Channel public progression page shows completed achievement history and persistent reward unlocks. It also shows a snapshot of archived season standings. The Sample Channel Community progression direct route that shows retained-state recovery while the feature is off.
A close action preserves a final standings snapshot and completion history. A disable action preserves the same data and routes staff back to Channel setup.

Season lifecycle

  • Close and snapshot standings freezes final standings and completion history.
  • Archive keeps that snapshot.
  • Archive keeps every persistent viewer unlock.
  • Archive keeps every equipped selection.
  • If expected progress is absent, check the channel and dates.
  • Check the rule.
  • Check the scope.
  • Check the filter.
  • Check the period and visibility.
  • Send one new event.
  • If Community progression is off, BlokeBot stops commands and events before changes.
  • If Community progression is off, BlokeBot stops timers and automation before changes.
  • If Community progression is off, BlokeBot stops rewards and public output before changes.
  • While Community progression is off, BlokeBot keeps saved seasons.
  • While Community progression is off, BlokeBot keeps saved progress.
  • While Community progression is off, BlokeBot keeps saved schedules.
  • While Community progression is off, BlokeBot keeps saved rewards.
  • While Community progression is off, BlokeBot keeps saved history.
  • Re-enable to continue in the current period. BlokeBot does not replay suppressed events or every reset period missed while the feature was off.