Changelog - Version 5.7.14 (2026-06-28)
Version Information
- Updated version from 5.7.13 to 5.7.14
- Fix: the bot now reads its Specter chat credentials from the website database instead of relying only on the environment, so chat messages keep sending after a token rotation
Bug Fixes
- Specter chat token is now sourced from the database
- The
botofthespecteraccount posts chat messages through the Twitch Helix “Send Chat Message” API, which needs a valid access token and client ID. Previously the stable bot only ever read these from its local environment configuration. When those credentials were rotated centrally, the running bot kept using its stale environment copy and chat messages silently stopped sending until the bot was restarted. - Fix: the bot now pulls the Specter chat credentials from the same central store the beta bot already uses, refreshing at most once a minute. If that lookup fails, it transparently falls back to the existing environment values, so behaviour is never worse than before.
- The
Technical Details
- Chat send now uses a shared helper that caches the current app credentials briefly and falls back to environment values if the lookup fails. This change is scoped to the Specter chat path only; the beta and v6 bots already had this behaviour.
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/