Join & reaction roles
Two ways members end up with roles without a moderator doing it.
#Join roles
Roles applied automatically when someone joins.
| Setting | What it does |
|---|---|
| Roles | What everyone gets on join |
| Bot roles | A separate set for bots, so they do not get the member role |
| User specific | A role for one particular account when they next join |
#Syncing
/joinroles sync applies the join roles to everyone already in the server. It is the fix
for setting join roles up after the server already has members.
Syncing a large server takes a while and reports progress as it goes.
#Reaction roles
A message where a reaction or a button gives a role.
#Setting one up
Either have the bot post a new message, or point it at an existing message you already wrote. Then pair each emoji or button with a role.
| Mode | Behaviour |
|---|---|
| Toggle | React to add, unreact to remove |
| Add only | Once taken, the role stays |
| Unique | Taking one removes the others in that group |
Unique is how colour roles should be set up. Picking blue takes red away rather than collecting both.
#Buttons or reactions
Buttons are cleaner: no reaction pile-up under the message, and the member is not left wondering whether their reaction registered. Reactions are more familiar. Both work the same way underneath.
#Role connections
Roles that follow other roles. When a member gains role A, give them role B; when they lose it, take B away.
The usual use is a staff role that should always carry the moderator colour, without anyone having to remember to add both.
#Role persistence
Roles applied by a restrict, or by automod, come back if the member leaves and rejoins. That closes the oldest hole in Discord moderation: leaving to shed a muted role.
Ordinary roles are not persisted, only ones the bot applied as a punishment.