/info — check the bot's status
/info shows, on a single card, whether the bot is running normally right now, how long it's been on, and how fast it responds. It's the first command to use when you want to check "the bot is acting strange — is it just me?"
This page explains what each line on the card means, which values to look at to judge a problem, and what to include when you contact us.
Good to know first — this card stays public
WARNING
Settings commands are visible only to the person who ran them, but /info stays in the channel where you ran it as a message everyone can see. Requested by and your name are attached at the bottom, so everyone can also see who ran it. It can be disruptive in a quiet channel, so run it somewhere convenient, like a channel for bots. If you've already posted it, someone who can delete messages needs to delete it.
This card shows Yeonhong's status
/info shows the status of Yeonhong, the bot that takes the commands. It doesn't include the server count or voice connections of other bots such as Yeonha. To see which bot is reading where, use /bots.
The whole card
## Yeonhong Info
Everything is working normally right now · Uptime: 3d 4h 21m
Service Stats
> Servers: 1,234 · Voice channels: 87 · Response time: 42ms
Bot Server Status
> CPU: 18% ▰▱▱▱▱▱▱▱▱▱
> MEM: 43% (6.9G / 16.0G)
Voice Servers
> Online: 4/4
Requested by usernameThree link buttons are attached below the card.
Reading it line by line
| Line | What the value is |
|---|---|
| Uptime | How long it's been since the bot last started |
| Servers | The number of servers Yeonhong is in |
| Voice channels | The number of voice channels Yeonhong is in right now |
| Response time | The response time between the bot and Discord |
| CPU · MEM | Usage on the computer the bot runs on |
| Online | The number of voice servers available for playing audio / the total number |
The top line — bot name and uptime
The first part of Yeonhong Info is the name Yeonhong has in this server. The name changes with the main language, so it may look different from server to server.
NOTE
Everything is working normally right now means "the bot can take commands and reply." To judge its condition in more detail, look at the Response time and Online lines below.
Uptime looks like 3d 4h 21m. If someone else runs /info at the same time, they may get a different value. A short uptime doesn't necessarily mean an outage. If the bot just restarted, it shows a short time.
Service Stats — Servers · Voice channels · Response time
- Servers — the number of servers Yeonhong is in.
- Voice channels — the number of voice channels Yeonhong is in right now.
- Response time — the response delay between the bot and Discord, in milliseconds (ms).
When the response time goes over a few hundred ms, command responses and the start of reading slow down noticeably. Around 100 ms is a normal value.
NOTE
The server and voice channel numbers update about a minute late. If you just invited the bot or just left a voice channel, you may still see the old numbers. Now and then a number much smaller than usual appears, but if you run it again a little later it goes back to the usual value.
Bot Server Status — CPU · MEM
Usage on the computer the bot runs on.
CPU: 18% ▰▱▱▱▱▱▱▱▱▱— the bar has 10 blocks, and one fills for every 10%.MEM: 43% (6.9G / 16.0G)— the value in brackets is memory in use / total memory.
These values are for reference only, so a high number doesn't mean it's the cause of a problem you're having. Running it again may give different numbers.
Voice Servers — Online: 4/4
Of the voice servers used for playing audio, this shows how many are available right now (left) and the total number (right).
| Shows | Meaning |
|---|---|
4/4 | All are working normally |
3/4 | One is out. The sound may cut out briefly |
0/4 | No sound can be played right now |
WARNING
If the left number is smaller than the right, the sound may cut out or /join may fail. While the bot moves itself over to a remaining voice server, the sound pauses for a moment, and a 'Moved to another voice server' message is posted in the text channel the bot was reading. If this happens, wait a moment and then call the bot again with /join. If the same thing keeps happening, let us know on the Official Discord Server, along with the Online value.
The bottom line — Requested by
The name of the person who ran the command is attached in small text. Because the card is a public message, everyone in the channel sees who ran it.
The three buttons below
| Button | What it does |
|---|---|
| Server Status | Opens the Yeonhong status page in a new window |
| Official Discord Server | Opens the invite link to the Studio Yeonhong Official Discord Server |
| Official Docs | Opens the official docs |
All three buttons are links. Clicking them doesn't send any request to the bot, so it's fine to click them as often as you like.
The numbers on the card are the values at the moment it was run, so they don't update on their own over time. To see the latest values, run /info again. The link buttons keep working even on old cards.
What this card can't tell you
/info is a card that shows the status of the bot as a whole. It doesn't show your account or this server's settings.
| What you want to know | Where to look |
|---|---|
| Your membership | Membership status & storage |
| Your voice, pitch and speed | User settings |
| Which bot covers which voice channel and chat | /bots |
| Whether the bot reads messages in this channel | Ask a server admin to check the Reading tab of the dashboard |
| The voice server the bot uses in this server | /voice-server |
Values worth sending when you report a problem
When you contact us on the Official Discord Server, sending a screenshot of the /info card helps us check faster. These three are especially important.
- The
Onlinevalue — the first thing we look at when there's no sound. Response time— evidence for when responses are slow.Uptime— shows whether the bot had only just restarted.