Ping
Check the bot’s API latency and responsiveness.Syntax
Parameters
This command takes no parameters.Example
Output
Displays the bot’s API latency in milliseconds with a fun, randomized message:- “Is this really my ping?”
- “Is this okay? I can’t look!”
- “I hope it isn’t bad!”
Lower latency (closer to 0ms) indicates better bot performance and responsiveness.
Purge
Bulk delete messages from a channel.Syntax
Parameters
The number of messages to delete (1-100)
Required permissions
User permission
MANAGE_MESSAGESBot permission
MANAGE_MESSAGESExamples
Limitations
Error handling
If the purge fails, you’ll receive an error message with:- Possible reasons for failure
- Link to the Support Server for assistance
- Reminder about the 14-day limitation
Common issues
Messages won't delete
Messages won't delete
Possible causes:
- Messages are older than 14 days (Discord limitation)
- Bot lacks
MANAGE_MESSAGESpermission - Bot doesn’t have access to the channel
- Channel permissions prevent message deletion
Permission errors
Permission errors
Ensure:
- You have the
MANAGE_MESSAGESpermission - Yato has the
MANAGE_MESSAGESpermission - Both have access to the channel
Say
Make the bot repeat a message in the channel.Syntax
Parameters
The message you want the bot to send
Example
Output
- The bot sends your message in the channel
- You receive an ephemeral confirmation: “Echo Message: [your message]”
The confirmation message is only visible to you (ephemeral) while the actual message is visible to everyone in the channel.
Use cases
- Creating announcements
- Making formatted messages
- Adding personality to server communications
- Creating custom welcome messages
Uptime
Check how long the bot has been running.Syntax
Parameters
This command takes no parameters.Example
Output
Displays the bot’s uptime in a human-readable format:- Days, hours, minutes, and seconds
- Example: “2 days, 5 hours, 30 minutes, 15 seconds”
Uptime resets when the bot restarts for updates, maintenance, or unexpected issues.
Best practices
Using purge responsibly
Using purge responsibly
- Always double-check the number before purging
- Consider the 14-day limit when cleaning old channels
- Use smaller numbers first to test
- Remember that purged messages cannot be recovered
- Inform moderators before large purges
Say command etiquette
Say command etiquette
- Don’t abuse the say command for spam
- Use it for legitimate server communications
- Consider using it for announcements and welcome messages
- Remember that the message appears to come from the bot
Monitoring bot health
Monitoring bot health
- Use
/pingto check if the bot is responsive - Use
/uptimeto see when the bot last restarted - High ping (>300ms) may indicate performance issues
- Report consistent high latency to the support server
Troubleshooting
Purge command issues
Permission errors
Most utility commands require specific permissions:/purgerequiresMANAGE_MESSAGESfor both user and bot- Ensure Yato’s role is properly configured in Server Settings > Roles
- Check channel-specific permission overrides
General troubleshooting
- Use
/pingto verify the bot is responsive - Check
/uptimeto see if recent restarts might explain issues - Verify you’re using the correct command syntax
- Join the Yato Support Server for help
Performance indicators
- Ping ranges
- Common uptime events
| Latency | Status | Description |
|---|---|---|
| 0-100ms | Excellent | Optimal performance |
| 100-200ms | Good | Normal performance |
| 200-400ms | Fair | Slight delays possible |
| 400ms+ | Poor | May experience lag |