Bots tab
This is where you see which part of this server each of our bots, such as Yeonhong and Yeonha, is handling, and where you find out why messages aren't being read. How several bots read together is covered in Several bots read together.
In Discord, press [Open in dashboard] on /bots or /voice-server to open this tab directly.
Our bots
The more bots you have, the more voice channels you can use at the same time. Each bot gets one row showing its current status.
| Status | Meaning |
|---|---|
| Reading | It's in a voice channel, reading messages |
| Relaying | It joined briefly through /relay and is reading a message |
| Idle | It's in the server but not in a voice channel |
| Offline right now | The bot is temporarily off, for example for maintenance |
| Not in this server | It hasn't been invited to this server yet |
For a reading bot, the status is followed by the voice channel it handles, '· reads #channel', and how long it's been handling it, like 'for 10 min'. The bot that takes commands is marked 'Main bot'.
If a bot isn't in the server or is offline, a line at the top of the list tells you.
- If one bot is missing, you see "○○ isn't in this server. Invite it to read in one more voice channel at a time." and [Invite].
- If several bots are missing, it tells you how many are there, like "○ of ○ bots are in this server."
- If a bot is offline, you see "○ of ○ bots are offline right now. The other bots read until they're back."
Rows for bots that aren't in the server or are offline look faded. A missing bot's row also says 'Invite it so this bot can read too'.
Inviting and removing
| Button | When it's shown | What it does |
|---|---|---|
| [Invite] | Bots that aren't in this server | Opens Discord's invite screen with this server already selected |
| [Remove] | Bots handling a voice channel | Removes that bot from the voice channel |
[Remove] is shown only to people who can change server settings. After removing, you're told "Removed ○○."
Check permissions
Press [Check permissions] and each bot is asked directly which permissions it's missing in this server. This quickly finds bots that can't get into locked channels.
| Result | Meaning |
|---|---|
| Check: no missing permissions | That bot has every permission it needs |
| Whole server: missing ○○ | That permission is missing across the whole server |
| #channel: ○○ | That permission is missing only in that channel |
| Check: the bot is offline, so it can't be asked | The bot is off. Please press it again in a moment |
| Check: the bot didn't answer | The bot didn't answer in time. Please press it again in a moment |
The permission names in the results are the same as the names shown in Discord's server settings. It checks View Channel, Connect, Speak, Send Messages, Embed Links, Read Message History, Manage Messages and Change Nickname.
- Without 'Connect' or 'Speak', the bot can't join that voice channel or make sound in it.
- Without 'Manage Messages', 'Delete read messages' on the Reading tab doesn't work.
- Without 'Change Nickname', the bot can't change its name to match the main language.
If you see 'The channel is full', the voice channel has reached its member limit, so the bot can't join.
Voice server of the reading bot
The row of a reading bot shows the voice server it's using now, like 'Voice server ○○ (region) · ○ connections'. A voice server is the server that actually sends out the bot's voice.
If the sound cuts out or lags, try picking another voice server in 'Move to another voice server'. It may pause briefly while moving. The details are in Voice servers.
Reading issues
This shows why messages weren't read, newest first. Press [Refresh] to load it again. If there haven't been any recent problems, it shows 'No recent issues'.
Each row shows which bot it happened on and when.
This isn't a channel set to be read
Yeonha 1 · 10/6 (T) PM 3:20If the same thing happens on several bots at the same time, it's grouped into one row, like 'Yeonha 1·Yeonhong'. Normal events, such as handing a message to another bot, aren't recorded.
Common reasons
| Record | Meaning and what to do |
|---|---|
| Messages starting with // aren't read | It's a message that's skipped on purpose |
| Reading is paused for maintenance | Reading resumes when maintenance is over |
| Not connected to a voice channel | The bot isn't in a voice channel. Call it with /join or turn on Auto-join |
| This isn't a channel set to be read | It's not in 'Channels to read', or it's not the text channel the bot handles |
| This user is excluded from reading | The person is in 'People not to read' |
| The writer doesn't have a role to read | The person has no role that matches 'Roles to read' |
| The message doesn't start with the prefix | It didn't start with the 'Message prefix' |
| Not in a voice channel | The writer isn't in a voice channel. 'Read outside the voice channel' is off, or the auto-join conditions weren't met |
| Nothing to read, or it was excluded by reading rules | Nothing was left to read, as in a message with only symbols or links |
| The message was deleted before it was read | The message was deleted before it could be read |
| Auto-join failed. Please check the connect permission | The bot couldn't join that voice channel. Try [Check permissions] |
| The bot doesn't have permission to join that voice channel. In the channel permissions, allow View Channel, Connect, and Speak. | The channel is one the bot can't see or join, such as a private voice channel. In the channel's permission settings in Discord, allow View Channel, Connect and Speak for the bot |
| The voice channel was full, so the bot couldn't join | The voice channel has reached its user limit |
| No bot was free to join. Invite more bots and they'll share the work | Every bot is reading in another channel. Invite more bots from 'Our bots' above |
| This bot joined briefly through '/relay', so it doesn't read chat | A bot that joined to read a /relay message doesn't handle chat |
| Too many bot messages in a minute, so some were skipped | A bot you set to be read sent too many messages in a short time |
| The reading queue is full | Too many messages to read piled up at once |
| Skipped by the user | Someone skipped it with /skip |
Messages that couldn't be read because of credits or usage limits are also recorded here. For credits, see Voice credits.