Redeem configuration

Use Channel Points to assign device actions to your channel's custom rewards. Complete Twitch connection setup first, then show Channel Points in the sidebar through Manage plugins.

Load existing rewards

  1. Open Channel Points and leave the page's master switch Disabled while configuring it.
  2. Click Fetch Rewards to load the connected channel's rewards.
  3. Open All Rewards to find an existing reward. The Manageable tab shows rewards created through this plugin, which it can also edit and delete on Twitch.
  4. Expand the reward you want to configure.

Newly fetched rewards start with their local action disabled. Fetching again updates titles and costs while retaining the action settings for rewards that still exist. Rewards deleted from Twitch are removed from the configuration.

Create a reward

  1. In Manageable, choose Create New Reward.
  2. Enter a Title, Cost (Channel Points), and optionally a Description.
  3. Click Create. This creates an enabled reward on Twitch, but its local MultiShock action starts disabled until you configure and enable it.

For a manageable reward, Edit Reward and Save Changes update its Twitch details. Delete Reward deletes the reward on Twitch and removes its local configuration. Rewards created elsewhere can have local actions here, but the plugin cannot edit or delete their Twitch details.

Configure the device action

  1. Expand the reward and select its Shockers.
  2. Set Mode to All, Random, or Round Robin.
  3. Choose Device Command: Shock, Vibrate, or Beep. Newly loaded rewards default to Shock, so check this before enabling the action.
  4. Set Intensity and Duration. For Shock, you can enable Warning Vibrate. See shared device settings.
  5. Turn on the reward's switch, then enable the page's master switch when ready. Local action settings save as you change them.

Each matching redemption runs the reward's configured action once. The action is matched by reward ID, so two rewards with similar titles remain separate.

Local actions and Twitch availability

There are separate controls for what viewers can redeem and what MultiShock does when a redemption arrives:

ControlEffect
Channel Points master switchEnables or disables all direct redemption actions in MultiShock.
Individual reward switchEnables or disables that reward's direct action in MultiShock.
Set Config Redeem Enabled flow nodeChanges the individual reward's local action switch.
Set Redeem Enabled flow nodePauses or unpauses a reward on Twitch; requires a reward created through this plugin.

Turning off a local action does not remove or pause the reward on Twitch. The master switch must still be enabled for an individually enabled local action to run.

Use redeems in a flow

Channel Point Redemption exposes the reward ID, title, point cost, viewer, and viewer input. Its Reward Title Filter matches part of a title without case sensitivity; leave it empty for all rewards. To distinguish rewards precisely, use the Reward ID output in your flow.

This trigger can fire even when the local direct action is disabled. If both the reward's direct action and a flow are enabled, both can react. Disable the local action when the flow should handle the device command by itself.

Use Set Config Redeem Enabled to change a fetched reward's local action, or Set Redeem Enabled to control availability on Twitch for a plugin-created reward. Check Success and Error after these actions.

If a redeem does not trigger an action

  • Confirm the connection is using the channel owner's account, then fetch rewards again and check the fetch result.
  • Check both the master switch and the individual reward switch. New rewards start with their local action disabled.
  • Confirm the reward has selected shockers and they are loaded in MultiShock.
  • If the reward was deleted and recreated, fetch again and configure the new reward; it has a different ID.
  • If a flow cannot pause a reward, check whether it appears under Manageable. For a redemption trigger, check its title filter and that the flow is running.

Contributors

Thank you to everyone who has helped improve this documentation.