Troubleshooting
AI is not responding
Check the Dashboard AI status indicator. "Starting…" means Ollama is still loading — give it a minute. If it stays yellow, verify the Ollama URL in Settings (http://localhost:11434) or switch to Cloud (Claude API) to isolate the issue.
Voice plays the default Windows voice instead of Neural
Neural speech comes from a Microsoft cloud service, and StreamBuddy retries before falling back to the Windows voice. If it keeps happening, check the Logs tab on the Dashboard for "Neural TTS: synthesis failed" and check your internet connection. Also confirm you selected a voice and clicked Save before testing.
No audio through OBS
Right-click the browser source → Properties → confirm "Control audio via OBS" is checked, and that the Audio Mixer shows a "Browser" channel with its volume up.
Overlay shows blank in OBS
StreamBuddy must be running before OBS loads the source — close and reopen the browser source after starting the app. Confirm port 3847 isn't blocked by Windows Firewall.
Audio or game events feel delayed
All voice playback shares one queue and waits for each open overlay source. Make sure every overlay source you've added is actually loaded in OBS — a source that is open but never loads can stall the queue.
Bot responds too much / too little
Adjust Response Rate in Personality. On busy channels, switch to trigger words so the bot only replies when directly addressed. Confirm "Ignore bot accounts" is on.
Text replies aren't showing up in chat
Check both toggles under Settings → Post Replies in Chat — they are independent. Also confirm the platform shows connected with write access on the Connect page; a read-only connection can't post.
Chat TTS isn't reading any messages
Check that Chat TTS is enabled, that Subscribers Only isn't filtering out the chatters you're testing with, and that your blocked-word list isn't matching common words.
Mic picks up sound but nothing gets transcribed
Lower Mic Sensitivity in Settings → Voice Input, then restart the mic with the Dashboard button — sensitivity only applies on the next start.
Twitch connection fails
Disconnect and sign in again from the Connect page to refresh your access — Twitch tokens can expire or be revoked.
Serial won't activate
Double-check the format: GB-XXXX-XXXX-XXXX-XX. Each key allows up to 3 activations, and reinstalling on the same PC doesn't use another one. If you've hit the limit, contact support to reset your activation count. This applies to Base too — every install needs an account and an active license before its serial will activate.
Custom command or automated event doesn't fire
Confirm it's enabled on the Commands tab and that its cooldown hasn't just been hit. A command can't reuse a built-in command name.
Velora bot won't create or select
Your main Velora account must be connected first — the bot section stays inactive until it is. If it still fails, let us know on Discord.
!shoutout / !so or the giveaway isn't working
Shoutout only responds to mods and the streamer, needs a username after the command, and has a 10-second cooldown. For giveaways, check that the platform you're testing from matches the giveaway's scope (All Platforms vs. one specific one).
A Stream Deck button returns an error
A 401 means the token in that button's URL doesn't match the current one — re-copy the URL from Settings → External Control. A 404 usually means the sound clip, ad, or command it points to was renamed or deleted.
Still stuck? Email support@modminds.site or see the support options below.