Skip to main content
There are around 1,600 commands, which is far too many to memorise. You don’t need to — the help menu is browsable and every group tells you its own subcommands.

​
The help menu

help · aliases commands, cmds, h
Running !help on its own opens a category picker. Choose a category and you get a paginated list; choose a command and you get its syntax, aliases, required permissions, cooldown, and an example with realistic arguments filled in. For groups like starboard or tickets, the help page includes a dropdown of every subcommand, so you can drill down without typing anything.
Groups also respond to being run bare. !starboard with no subcommand shows you what starboard can do, same as !help starboard. This is usually the fastest way to explore.

​
Reading a syntax line

  • <angle brackets> — required
  • [square brackets] — optional, with a default
  • --flag value — a named option, see flags
Arguments that take a channel, role, member or message accept several formats: a mention, an ID, an exact name, or a partial name. !role add jake mod will resolve fine as long as the match is unambiguous.

​
Every command, in one place

The full command tree is published at mira.party/commands — searchable, always current, and generated from the running bot rather than maintained by hand. If a command exists, it’s on that page.

​
Making responses look right

Every response the bot sends can be restyled per server. This is under customize and needs Administrator.
Four response types can each be given their own emoji and colour:
!customize response reset puts everything back.
Two small toggles that change the tone of every reply:
ping controls whether responses mention you. punctuation controls whether they end in a full stop — off is the more casual look.
You can change how mira appears in your server specifically:
!customize reset reverts to the default profile. For a genuinely separate bot account with its own name and token, see custom instances.
Reskin forwards command responses through a webhook so they appear under your name and avatar instead of the bot’s. Set up per channel by a moderator, then configured per user:
!reskin list shows which channels have it enabled, !reskin remove clears your personal settings, and !reskin disable #general turns it off for a channel.Last.fm users can go further and have their reskin avatar follow whatever they’re listening to — see Last.fm settings.

​
When a command doesn’t respond

In order of likelihood:
1

Wrong prefix

Try @mira ping. Mentioning always works.
2

You lack the permission

Check the command’s help page for what it needs. If you should have it but don’t, fake permissions can grant it without handing out the real Discord permission.
3

The command is disabled here

!command disable list and !module disable list show what’s been turned off, and where.
4

You or the channel are ignored

!ignore list shows every ignored member and channel.
5

The bot can't see or speak in the channel

It needs View Channel, Send Messages and Embed Links at minimum. Check the channel’s permission overwrites, not just the role.
More on all of this in the FAQ.