Role menus

Role menus are reaction-based role pickers: you map each Discord role to an emoji (Unicode or a custom emoji from your server), save the configuration in the Antidote dashboard, then run a short Discord command on the target message so Antidote attaches reactions and listens for clicks.

Limits (plan defaults in code)

• Role menus — typical caps 10 (free) / 250 (premium).
• Role menu groups — typical caps 2 / 25.

Exact numbers follow your server’s plan in the dashboard.

Per-menu options (reaction menu editor)

These fields apply when the menu is not assigned to a group (see Grouped menus below).

• Reaction menu name — Internal label in the dashboard list.
• Role menu group (optional) — Attach this menu to a group. When set, several per-menu controls move to the group (see below).
• Require users to keep a role in this menu (force_role) — When enabled, members must keep at least one role from this menu’s reaction list (only for standalone menus).
• Remove previously given role from menu (remove_old_role) — When enabled, picking a new role from this menu can remove another role that came from the same menu (standalone only).
• Reaction roles — One row per choice: emoji (picker: native or server custom) + Discord role. Add/remove rows with Add role / trash. Each row is one reaction Antidote will place on the posted message.
• Required roles — Member must have at least one of these roles to use the menu.
• Ignored roles — Members with any of these roles cannot use the menu.
• Role notification DMs — Only for standalone menus; see DM mode below.

DM mode (role_dm_mode) for standalone menus:

• Default bot messages — Antidote sends its built-in short DM text when roles are given or taken.
• Disabled — No DM when roles change from this menu.
• Custom embeds — Two saved server embeds: one when a role is given, one when a role is taken (from Server embeds). The editor links to the embed manager and offers a variables reference (User, Guild, Menu, Role placeholders).

Grouped menus

If Role menu group is set on a menu:

• Force role, Remove old role, Required roles, and Ignored roles on that menu are not edited there — the group defines them for all menus in the group.
• Role notification DMs for menus in the group are configured under Role menu groups (not on the single menu). If you later remove the menu from the group, the menu’s own DM settings are kept.

The group editor exposes:

• Group name — Required; max 100 characters in validation.
• Ignored roles — Users with any of these roles cannot interact with menus in this group.
• Required roles — User must have at least one of these roles to interact.
• Remove old roles when selecting new ones — Turning a role on in one menu in the group can strip conflicting roles from other menus in the same group (useful for mutually exclusive color roles).
• Force users to have at least one role from this group — Same idea as standalone force_role, scoped to the group.
• Role notification DMs — Same three modes as a standalone menu (default / disabled / custom with give/take embeds).

Posting the menu in Discord

After Create or Update, the editor shows a fixed initialization command of the form rolemenu create <menu_id>. The dashboard may display a default prefix character; use whatever your server uses.

• Reply to the message that should become the menu or pass the message ID as an argument.
• Antidote uses that message to add reactions and register collectors.

Clearing a menu from a message

Use rolemenu clear with the menu message’s ID (Developer Mode → copy ID), or follow the bot’s usage for replying to that message — see in-Discord help for your prefix.

Related

• Role templates — bulk packages of embeds, roles, and menus; optional shortcut if your host exposes a template library.