Troubleshooting

What to check when something is quiet.

A squad bot did not join

• Is that squad bot invited? The server page shows an invite button for any missing bot.
• Can it see and connect to the party channel? Private channels need an explicit permission overwrite.
• Is the slot above your plan limit? Locked slots are skipped and reported by /start.

Nobody hears the caller

• Is the caller in the command channel with a starter or priority role?
• Is Warcaller Command server-deafened? It must be able to hear the channel.
• Run /status: it names the current caller and each squad's state.

Audio is choppy or late

Warcaller forwards the caller's packets untouched and adds about 20 ms; listeners hear the caller a single Discord hop later than in a shared channel. Choppiness usually comes from the caller's own upload. The dashboard's console shows dropped frames per relay; a rising number points at the caller's network. A delay that feels large usually means the command channel and the party channels sit in different voice regions: pin them to the same region in each channel's settings.

Restarting a squad

Click a squad's tile in the Fleet panel, or the restart link on its row in the field plan. It rejoins that bot and clears any pause caused by repeated failures. Squads also recover on their own every few minutes.

Rejoining the command channel

If the caller can be seen speaking but nothing reaches the party channels, use the rejoin link on the Command row of the Fleet panel. The listener drops its voice connection and joins the command channel again with a fresh encrypted session; the relay keeps running and the squads stay where they are. The relay does this on its own when it notices the problem, so the link is for the rare case where it does not.