Changelog - Version 5.7.17 (2026-08-14)
Version Information
- Updated version from 5.7.16 to 5.7.17
- Fix: AutoMod-held spam is now denied as well as banned
Bug Fixes
- Spam pattern AutoMod deny never reached Twitch
- When a spam/bot message was held by AutoMod, the bot banned the account but left the hold in the AutoMod queue. Deny failed because it queried
twitch_bot_accesson the channel database (that table does not exist there). - The deny path also sent
user_idas the spam author. Twitch’s Manage Held AutoMod Messages API requiresuser_idto be the moderator that matches the token (971436498when denying as the bot).twitch_bot_accesslives inwebsite. - Fix: new
deny_automod_message()helper next toban_user()— openswebsite, uses the bot token, postsuser_id= moderator,msg_id= hold id,action=DENY. Wired onautomod.message.holdandchannel.chat.user_message_holdafter a spam-pattern match.
- When a spam/bot message was held by AutoMod, the bot banned the account but left the hold in the AutoMod queue. Deny failed because it queried
Technical Details
- Helix:
POST https://api.twitch.tv/helix/moderation/automod/message— scopemoderator:manage:automod, success204. - Token source matches
ban_user():website.twitch_bot_accessfor bot id971436498, fallbackCHANNEL_AUTH.
Thank you for your feedback and support!
As always, your feedback is appreciated. Please report any issues, bugs, or suggestions in the #ticket-info channel on our Discord server. You can also submit feedback and bug reports directly on our support website: https://support.botofthespecter.com/