Frequently asked questions
Does AveloBot post to chat as my account or its own?
It depends on how your operator set things up:
- If a shared bot account is configured, the bot posts as that account.
- Otherwise, it posts as your broadcaster account.
You don't switch this yourself — it's controlled by the operator.
Can I use the same workspace for two channels?
No. A workspace is tied to a single Twitch broadcaster account. To run AveloBot for a different channel, sign in with that channel's Twitch account — it gets its own workspace.
What happens to my settings if I disconnect?
Disconnecting your channel removes Twitch tokens and stops EventSub, but keeps your commands, timers, quotes, and event response settings. Reconnecting picks up where you left off.
Why didn't the bot react to a follow / sub / raid?
Check, in this order:
- Is the channel connected on
/channel? If it says "Needs reauth", reauthorize. - Is the matching event response enabled on
/events? - Is the response message empty? An empty template means "stay quiet".
- For tips, is StreamElements connected?
The Test button on the Events page is the fastest way to confirm the response itself works.
Why was my chat command ignored?
Common reasons:
- Trigger mismatch — typos count.
!ping≠!Ping(triggers are case-insensitive but only with exact text match after the!). - Cooldown — global or per-user cooldown still active. Wait it out or lower the cooldown.
- Permission — the chatter doesn't meet the required level (e.g. "Subscriber" gating).
- Disabled — the command is toggled off on
/commands. - Channel offline — some commands behave differently or stay quiet when offline (e.g.
!uptime).
Can I export my commands or quotes?
Not directly through the UI today. Ask your operator if you need a database export.
What permissions does AveloBot ask for, and why?
See Sign in for the full list of OAuth scopes and what each one is used for.
Where are server-side errors logged?
That's your operator's domain — AveloBot writes structured logs they can inspect. If something seems persistently broken (commands disappearing, events not firing across the board), report it to whoever runs your AveloBot deployment.