Keep viewer interaction fun without losing control

Control chaos mid-stream

Use the dashboard controls when the stream needs a quick reset. These tools should be visible and easy to reach before a raid, collab, tournament, or serious segment.

1. Pause the panel before sensitive moments so viewers cannot start new alerts.
2. Mute the overlay when alerts should still be tracked but not heard.
3. Clear the queue if too many alerts are stacked.
4. Check whether paid alerts are held, rejected, or restored according to the current state.
5. Unpause gradually and run a test slap before returning to normal use.

For important stream moments, pause before the moment starts. Reacting after a bad alert is always harder than preventing it.

Use global, per-sound, and per-viewer cooldowns

Cooldowns decide how often sounds can fire. A balanced setup usually uses multiple cooldown types at once.

• Global cooldown: protects the entire stream from too many alerts at once.
• Per-sound cooldown: protects loud or special sounds from being spammed.
• Per-viewer cooldown: keeps one viewer from dominating the panel.
• Queue cap: prevents a raid from stacking an endless backlog.

If the stream feels too quiet, lower cooldowns on subtle reactions. If the stream feels chaotic, raise cooldowns on loud sounds first.

Limit SoundSlaps to channel subscribers

Subscribers only is a Stream Guard setting that lets the broadcaster decide whether all viewers can trigger SoundSlaps or only current channel subscribers can trigger them. When it is off, subscribers and non-subscribers can use any enabled sound. When it is on, SoundSlap checks subscriber status before accepting Bits or Channel Points activations.

1. Open the SoundSlap dashboard as the broadcaster.
2. Go to Settings and find Twitch Panel Access.
3. Turn on Subscribers only when you want sounds to act like a subscriber perk.
4. Reconnect Twitch if the dashboard asks for subscriber-read permission.
5. Make sure the Twitch Developer Console has Subscription Status enabled for the extension before using this in review or production.

Subscriber-only checks are enforced server-side. The extension panel can show the viewer a lock message or identity-sharing prompt, but the final decision happens before the sound enters the queue.

• Viewers may need to share Twitch identity so SoundSlap can verify their subscription.
• Anonymous or opaque extension viewers cannot pass subscriber-only mode until Twitch provides a usable viewer identity.
• Manual dashboard tests still work so the broadcaster can test audio without needing a viewer subscription.
• Denied subscriber-only attempts do not create Restore Tokens because the slap was never eligible to play.

This setting is best for subscriber perk streams, lower-risk community nights, and moments where the streamer wants a smaller trusted audience controlling alerts. Leave it off when you want everyone in chat to participate.

Block problem viewers from slapping sounds

Viewer blocks are for people who repeatedly use alerts in bad faith. Blocks should be specific, reversible when appropriate, and separate from ordinary cooldown management.

1. Find the viewer in dashboard activity or history.
2. Confirm the behavior is intentional and not a one-time mistake.
3. Block the viewer from future SoundSlap interactions.
4. Leave channel moderation actions, such as timeout or ban, to Twitch mods when needed.

Blocking a viewer in SoundSlap should stop them from triggering sounds. It does not replace Twitch moderation if the viewer is also causing problems in chat.

Use SoundSlapBot in chat

SoundSlapBot can post clean chat messages when alerts fire. For richer chat features, the channel should grant bot permissions and moderate the bot account.

1. Connect the broadcaster account from the dashboard.
2. Grant the requested Twitch chat permissions when prompted.
3. Mod SoundSlapBot in the channel if the dashboard setup asks for it or future moderation features require it.
4. Keep bot messages short so they add context without flooding chat.

If bot messages stop appearing, reconnect Twitch and confirm the bot still has permission to join and post in the channel.