Channel plugins

Use plugin features in your channel

A trusted plugin can add channel tools. Each channel controls its own plugin features and settings.

Channel setup for Sample Channel shows connection and bot status. It also shows chat tool controls. Channel setup for Sample Channel shows connection and bot status. It also shows chat tool controls.
Use Channel setup to select a channel and find its feature controls.

Enable one feature

Every plugin feature is Disabled after installation. The dashboard labels this state Off.

  1. Open Channel setup.
  2. Select the channel.
  3. Open the plugin feature that you want to use.
  4. Enter the generated settings.
  5. Save the settings.
  6. Enable the feature.

Feature readiness

An absent Twitch scope or incomplete EventSub subscription can cause EnabledDegraded. Work that does not need that readiness can continue.

Use the action on the feature page to reconnect Twitch or retry the subscription check.

  • A Disabled plugin feature receives no commands.
  • A Disabled plugin feature receives no events.
  • A Disabled plugin feature receives no schedules.
  • A Disabled plugin feature receives no actions.
  • A Disabled plugin feature receives no pages.
  • A Disabled plugin feature receives no automatic work.
Disabled
The feature is off.
Ready
The feature is on. BlokeBot admits work that matches the current installation and channel.
EnabledDegraded
The feature is on, but some declared work is unavailable. The dashboard labels this state Needs attention.

Plugin work in a channel

  • Built-in commands have first precedence.
  • Custom commands have second precedence.
  • Plugin commands have third precedence.
  • A built-in or custom route shadows the plugin command. The feature stays enabled.
  • A second enabled plugin cannot claim the same plugin command route. BlokeBot rejects that feature enablement.
  • BlokeBot admits typed events only while their feature and required readiness are admitted.
  • BlokeBot admits schedules only while their feature and required readiness are admitted.
  • BlokeBot admits actions only while their feature and required readiness are admitted.
  • A plugin can store private data in its own SQLite database. The plugin must separate rows for each channel.

Use pages and automatic flows

  • A generated page uses BlokeBot controls and validation.
  • An embedded page stays in a contained frame. The frame is not a security sandbox for the trusted plugin.
  • A declared template can create one flow when you enable the feature. BlokeBot does not show a separate preview or confirmation.
  • Repeated startup checks do not create duplicate flows. BlokeBot never overwrites or silently renames a flow that already exists.

Recover a channel feature

If you deleted an automatic flow, disable the feature. Enable it again. BlokeBot creates the flow again.

If the plugin is faulted or absent, ask a BlokeBot administrator to recover the installation.