Give viewers a clear Twitch Bits flow for triggering sounds

Set Bits prices correctly

SoundSlap uses a supported Bits ladder so streamer-entered prices line up with valid Twitch product values while staying under Twitch's SKU cap. The ladder uses 25-Bit steps up to 5,000, 100-Bit steps through 7,000, and 250-Bit steps through 10,000.

1. Open My SoundSlap List and choose a sound.
2. Enable Bits for that sound.
3. Set low and mid prices in 25-Bit increments through 5,000 Bits.
4. Use 100-Bit increments from 5,100 through 7,000 Bits.
5. Use 250-Bit increments from 7,250 through 10,000 Bits.
6. Save the sound and confirm the panel displays the new price.
7. Use a low-cost test sound before making expensive interruptions public.

If a typed value does not land on the supported ladder, SoundSlap rounds it to the nearest valid amount. If the panel shows a different price than the dashboard, refresh the panel and save the sound again.

Future loyalty support

Channel Points integration is planned for a future release and is not available in the current SoundSlap product. Setup controls and redemption processing remain disabled until that release is ready and documented.

Know how subscriber-only mode affects Bits purchases

When Subscribers only is enabled in Settings, SoundSlap verifies that the viewer is a current channel subscriber before it accepts a Bits slap. This keeps the feature usable as a subscriber perk without relying on front-end-only checks.

• Bits: the panel blocks the action when possible, and the server checks eligibility again before queueing the sound.
• Identity sharing: viewers may need to share Twitch identity in the extension panel so subscriber status can be checked.
• Permissions: the broadcaster should reconnect Twitch when SoundSlap asks for subscriber-read access.

If a viewer is denied because they are not a subscriber, the sound is not eligible to play and no Restore Token is created. Restore Tokens are for accepted paid slaps that later fail playback, not for safety or eligibility denials.

Understand Restore Tokens

Restore Tokens protect viewers when a paid slap is accepted but cannot finish playback. They are meant for playback failures, not for ordinary denials like cooldowns or a paused panel.

1. Check dashboard history for paid slaps that were accepted but did not complete playback.
2. Verify the overlay was connected at the time of the failure.
3. Use Restore Tokens to let the viewer replay the paid sound once service is healthy again.
4. Do not use Restore Tokens to bypass cooldowns or safety controls.

A healthy setup should rarely need restore handling. If tokens are common, troubleshoot the overlay connection, browser source, queue mode, or audio file itself.

Choose prices that match stream impact

Price sounds by how disruptive they are. A subtle reaction can be cheap and frequent. A loud jump scare should be more expensive and protected by a cooldown.

• Low-impact reactions: low Bits price, shorter cooldown.
• Medium-impact jokes: moderate price, moderate cooldown.
• Loud interruptions: higher price, longer cooldown, lower volume test first.
• Signature channel memes: price high enough that they feel special but still reachable.

After a stream, review which sounds were used most. If a sound is funny once but exhausting ten times, raise its price or cooldown.