Self-assignable roles

Three ways to do the same thing. Buttons are the modern default; dropdowns are best when there are a lot of options; reactions are the classic approach and still work fine. All require Manage Roles, and mira’s role must sit above every role being handed out.

Post the message first

Whatever the members will click on. Use !embed if you want it to look designed:

!embed {title: Pick your roles} {description: React below to get notified about the things you care about.} {color: #5cacec}

Attach roles to it

Every command below takes that message — as a link, an ID, or a reply.

Button roles

The best default. Clear, mobile-friendly, and clicking toggles the role.

!buttonrole add <message> @Announcements

!buttonrole add <message> @Announcements success 📢 "Announcements"

!buttonrole remove <message> @Announcements

!buttonrole clear <message>

!buttonrole list

Arguments after the role are optional and positional: style, emoji, label.

Style	Colour
`primary`	Blurple
`secondary`	Grey
`success`	Green
`danger`	Red

If a message gets edited by something else and loses its buttons:

!buttonrole render <message>

Aliases: buttonroles, btr. render aliases: refresh, sync. Better past about five roles — one compact menu instead of a wall of buttons.

!dropdownrole add <message> @Announcements 📢 "Announcements"

!dropdownrole description <message> @Announcements "Get pinged for news"

!dropdownrole placeholder <message> "Choose your roles..."

!dropdownrole remove <message> @Announcements

!dropdownrole list

Members can select multiple options, and deselecting removes the role. Aliases: dropdownroles, selectrole, dropdown, dd.

Discord caps a dropdown at 25 options. Past that, use a second message.

Reaction roles

!reactionrole add <message> 📢 @Announcements

!reactionrole remove <message> 📢

!reactionrole clear <message>

!reactionrole list

Aliases: reactionroles, rr.

Limiting picks

!reactionrole limit <message> 1

Caps how many roles a member can take from that message. Set to 1 for mutually exclusive choices — picking a new one removes the old.

Inverting

!reactionrole reverse <message> on

Reacting removes the role instead of granting it. Useful for opt-outs: “react to stop being pinged for events”.

Fixing desyncs

!reactionrole sync <message>

Discord occasionally drops reaction events during outages, leaving people with a reaction but no role. This walks the reactions and fixes every mismatch. Aliases: fix, refresh.

Which should I use?

Under 5 roles

Buttons. One click, visible without interacting, works well on mobile.

5–25 roles

Dropdown. Keeps the message short and supports per-option descriptions, which matters when the role names aren’t self-explanatory.

Over 25 roles

Multiple messages, one per category — colours, pings, games. A dropdown each, or buttons if each category is small.

Aesthetic reasons

Reactions. Some people prefer how they look, and they’re the only option that works on very old messages you can’t edit. They’re also the least reliable — reaction events get dropped, which is what reactionrole sync exists for.

Nothing stops you mixing them. Buttons and a dropdown on the same message both work — dropdownrole render re-applies the dropdown and any button roles on that message.

A worked example

// 1. post the message
!embed {title: Roles} {description: **Notifications** — pick what you want pinged for.
**Colours** — one at a time.} {color: dominant}

// 2. notification roles as a dropdown
!dropdownrole placeholder <message> "Notifications..."
!dropdownrole add <message> @Announcements 📢 "Announcements"
!dropdownrole add <message> @Events 🎉 "Events"
!dropdownrole add <message> @Giveaways 🎁 "Giveaways"
!dropdownrole description <message> @Announcements "Server news and updates"

// 3. colours as buttons on a second message
!buttonrole add <message2> @Pink secondary 🌸
!buttonrole add <message2> @Blue secondary 💙
!buttonrole add <message2> @Green secondary 💚

Command reference

Command	Permission	Description
`buttonrole add <message> <role> [style] [emoji] [label]`	Manage Roles	Add a button
`buttonrole remove <message> [role]`	Manage Roles	Remove a button
`buttonrole clear [message]`	Manage Roles	Clear a message, or the server
`buttonrole list`	Manage Roles	View all button roles
`buttonrole render [message]`	Manage Roles	Re-apply components
`dropdownrole add <message> <role> [emoji] [label]`	Manage Roles	Add an option
`dropdownrole description <message> <role> [text]`	Manage Roles	Describe an option
`dropdownrole placeholder <message> <text>`	Manage Roles	Set placeholder text
`dropdownrole remove <message> [role]`	Manage Roles	Remove an option
`dropdownrole clear [message]`	Manage Roles	Clear a message, or the server
`dropdownrole list`	Manage Roles	View all dropdown roles
`dropdownrole render [message]`	Manage Roles	Re-apply the dropdown
`reactionrole add <message> <emoji> <role>`	Manage Roles	Add a reaction role
`reactionrole remove <message> <emoji>`	Manage Roles	Remove one
`reactionrole clear <message>`	Manage Roles	Clear a message
`reactionrole limit <message> <amount>`	Manage Roles	Cap roles per member
`reactionrole reverse <message> (on/off)`	Manage Roles	Invert the behaviour
`reactionrole sync <message>`	Manage Roles	Fix mismatches
`reactionrole list`	Manage Roles	View all reaction roles

Start here

Security

Moderation

Server setup

Music & audio

Last.fm

Social

Utility

Self-assignable roles

Button roles

Reaction roles

Limiting picks

Inverting

Fixing desyncs

Which should I use?

A worked example

Command reference

​Button roles

​Dropdown roles

​Reaction roles

​Limiting picks

​Inverting

​Fixing desyncs

​Which should I use?

​A worked example

​Command reference

Button roles

Dropdown roles

Reaction roles

Limiting picks

Inverting

Fixing desyncs

Which should I use?

A worked example

Command reference