Miki Bot commands are designed to streamline your Discord experience with clear, predictable actions for moderation, music, and utility tasks. This guide explains the most common command patterns and how to configure them for your server.
Use the summary table below to quickly compare core capabilities, required permissions, and typical use cases for Miki Bot commands.
| Command Category | Example Commands | Required Permissions | Primary Use Case |
|---|---|---|---|
| Moderation | kick, ban, mute, warn | Kick Members, Ban Members, Manage Roles | Maintain server rules and remove disruptive users |
| Music Playback | play, pause, skip, queue | Connect, Speak in Voice Channels | Control bot audio playback in real time |
| Utility & Info | ping, avatar, userinfo, serverinfo | Send Messages, Read Message History | Quick diagnostics and social features |
| Custom Prefix & Settings | setprefix, togglelogs, setrole | Manage Server, Administrator | Personalize command prefixes and logging |
Setting Up Miki Bot Commands
Proper installation and role configuration ensure your Miki Bot commands execute without permission errors. Invite the bot with the appropriate scopes and grant it a high position in the role hierarchy.
Start by adding Miki Bot to your server using the official OAuth2 URL. Select the necessary scopes, such as Bot and Applications Commands, and assign the required permissions for moderation, voice, and information features.
Managing Command Permissions
Command restrictions depend on roles and channel permissions, making it essential to set up role hierarchy carefully. You can limit sensitive commands to administrators or specific trusted roles.
Use the dashboard or in-server commands to define who can use music, moderation, and utility features. You may lock dangerous commands to senior staff while allowing general users to use info and utility commands.
Using Music and Media Commands
Miki Bot music commands give you straightforward control over playback directly from chat. These commands work in voice channels and rely on proper voice connection permissions.
Common patterns include play, pause, resume, skip, and queue, which let you manage the current track list efficiently. You can use song URLs, search terms, or presets to start playback instantly.
Customizing Server Settings
Server settings commands allow you to adjust logging, prefixes, and automated roles to match your community culture. Small changes here can reduce noise and streamline moderation workflows.
With setprefix and togglelogs, you can choose which channels receive audit entries and how commands are triggered. Consistent settings across servers make it easier for members to learn and use Miki Bot commands.
Optimizing Your Workflow with Miki Bot Commands
Streamlined server management is possible when you align roles, channels, and command permissions with your team structure. Regular reviews of command usage help you prune unused features and highlight high-value actions.
- Assign Miki Bot a high role to ensure moderation commands always function
- Create a dedicated log channel and enable togglelogs for clear audit trails
- Limit sensitive commands to trusted roles while keeping music and info open
- Use setprefix to match your existing naming conventions and reduce confusion
- Test play, pause, and skip in a private voice channel before public events
FAQ
Reader questions
How do I change the bot prefix for my server?
Use the setprefix command followed by your desired prefix, ensuring you have permission to manage server settings.
Can I restrict music commands to certain roles?
Yes, you can limit voice and playback commands to specific roles through the role and permission settings in the dashboard.
What permissions are needed for moderation commands to work?
Moderation commands require Kick Members, Ban Members, and Manage Roles permissions at a minimum, plus a high role position.
How are logs displayed for user actions?
Enable logging with togglelogs, then choose a dedicated log channel where Miki Bot will send moderation and setup events.