Skip to content

Troubleshooting / FAQ

Nightbot not responding to commands

Check these in order:

  1. Is the command added in Nightbot? Go to your Nightbot dashboard → Custom Commands. Confirm the command exists and the URL is correct.
  2. Is the command userlevel set correctly? If a viewer is trying to run a command you set to Moderator, Nightbot will silently ignore it. (The reverse is also true: apart from !health, !here @user, and letting the channel owner, mods and subscribers past Supporter Only mode on !here, RaidQ itself never checks who sent a command, so a mod command left at Everyone works for anyone.)
  3. Is the queue (or registration) open? The queue and registration must be open. Run !start from chat to open both. RaidQ replies "The queue is currently closed" if a viewer tries !here while it's closed.
  4. Is Nightbot joined to your channel? Check the Nightbot dashboard → Channels.
  5. Is Nightbot timed out or rate-limited? Nightbot enforces a cooldown per command. If two viewers fire the same command in rapid succession, Nightbot may suppress the second response.

Viewer not appearing in the queue after !here

  1. Are they registered? They must run !reg TrainerName first. If unregistered, !here returns a message asking them to register.
  2. Is the queue in Supporter Only mode? Non-supporters without a Hall Pass are blocked. They can type !here mem to get in the queue anyway, but they won't be picked for the raid group until they have a Hall Pass.
  3. Is the viewer blocked? Run !whoami username (set to Moderator in Nightbot) to check their status.
  4. Is the queue closed? Check the QUE badge on /que or run !start que.
  5. Did they already join? !que shows the current queue. Search the list.

Overlay is blank

  1. Wrong channel parameter? Verify the ?channel= value matches your exact channel ID. Mismatch = empty overlay.
  2. OBS browser source needs one manual refresh. Right-click the source → Refresh. After that, auto-refresh handles updates.
  3. Is RaidQ returning errors? Check the /que page in a browser — if that loads, RaidQ is up. If the overlay is still blank, the channel ID is the most likely culprit.

FREE badge stuck / Hall Pass not clearing

  • A one-time Hall Pass is used up when the holder is picked for the raid group by !next. If they were moved or removed by hand instead, the pass may not clear. Grant a new one with !tier NAME hp, or take it away by long-pressing their card on /que.
  • A timed Hall Pass stays active until it expires, no matter how many times !next is run. Check when it expires with !whoami NAME (set to Moderator in Nightbot).

Name edit not saving

  1. Is the name too long? Trainer names are capped at 15 characters. Longer names are refused with Name too long, max 15 characters. in chat, and the Members page refuses the save and names the row.
  2. Is the user registered? The user must already be registered. Run !reg for them first, or use !setpogo YTname PoGoName from chat.
  3. Are you editing the right card? Long-press opens the modal for the card you held. Check the name shown at the top of the modal.

/que page shows wrong channel / auto-redirected to wrong channel

If you open /que without a ?channel= parameter, the page redirects to the last channel that browser opened, or to the streamer sign-in page if it has never opened one. Always use the full link copied from your Streamer Dashboard, or sign in and use /streamer/que, which always shows your own channel.

Rate limit errors

Each user is rate-limited per command per rolling window. If a viewer is spamming a command they may see a rate-limit response. This resets automatically.

The /que page, OBS overlays, and the boss overlay also have a generous built-in ceiling on how often they can be refreshed from one network connection. Normal use — even several overlays and the queue page open at once — stays well under it. If it's ever hit (for example a misbehaving browser tab stuck in a refresh loop), the affected view will briefly show a "↻ reconnecting" pill and recover on its own once the limit window passes, usually within a minute or so; nothing needs to be reset manually.

Common chat replies and what they mean

  • "You need to register first. Type !reg followed by your Pokémon Go in game name. EXAMPLE: !reg StreamerName": the viewer hasn't run !reg yet, was removed with !forgetme, or only has a snipe on record from before they registered. They type !reg with their in game name (not a friend code), keep any snipe credit, and then !here works. The example name is your !set name streamer name when one is set, otherwise your channel name with spaces turned into underscores.
  • "The queue is currently closed. Please wait for the streamer to open it." — run !start or !start que, or tap the QUE badge on /que.
  • "Supporter-only raids right now. Unlock access: !here mem" — the queue is in Supporter Only mode and the viewer isn't a supporter or Hall Pass holder. See Queue Modes.
  • "You are blocked." — the viewer was blocked with !block. !unblock reverses it.
  • "You are in the next raid group." — the viewer is in the current raid group; they don't need to !here again.
  • "Roster full, ask the streamer" — the channel has hit its plan's registered-viewer cap. Plan limits aren't switched on yet, so this reply can't appear today. See Plans & Pricing.
  • "Rate limited" — the viewer sent commands too fast. Wait a few seconds.
  • "Queue temporarily read-only — try again in a few minutes" — a RaidQ maintenance window. Commands that only read (!que, !deck, !who) keep working.
  • "Bad cmd" — the cmd= value in the Nightbot command URL isn't a RaidQ command. Check the spelling against Chat Commands.

My queue disappeared after I changed the boss

This is expected. Setting a new boss — from chat with !set NewBoss or by holding one on /que — clears out everyone who was waiting for (or already picked for) the old boss. It doesn't carry them over to the new one. If it was a mistake, !undo (or the /que Undo button) right away brings back the old boss, its raid group and its queue, and takes back the raid credit. If you want to keep the waiting queue when you switch, use the boss picker on /que and tap Keep Q in the confirmation, or type !set keep NewBoss in chat; a plain !set NewBoss always clears. Check with your mods before switching bosses mid-raid.

Another cause: if nobody has typed a chat command or tapped /que for 2 hours, the queue, raid group and boss reset on their own the next time something happens (whoever was in the raid group still gets credit). That's expected too.

Something feels broken and I don't know why

Run !health (mods only) for a quick system status check — database, Discord webhook, and queue-link token. The /que page also shows a "Channel health check failed" banner when the last check went red. If it reports a problem, wait a few minutes and try again; if it persists, reach out to an admin.