Commands
ProModeration Config
Configure how the moderation suite behaves — set log channels, escalation thresholds, and the opt-in staff server-tag enforcement that automatically retires staff members who stop displaying your server tag.
/modconfig logchannel
ProSet or change the channel where moderation actions are logged.
/modconfig logchannel <#channel>Requires: Admin only
/modconfig escalation
ProConfigure automatic escalation rules based on warning count (e.g. auto-mute at 3 warnings).
/modconfig escalation <threshold> <action>- • threshold — Number of warnings to trigger the action.
- • action — The action to take (mute, kick, ban).
Requires: Admin only
/modconfig roles
ProAssign a Discord role to one of the six staff slots used for permission checks and staff management. Each slot holds exactly one role.
/modconfig roles <admin|moderator|retired_staff|staff_1|staff_2|staff_3> @role- • admin|moderator|retired_staff|staff_1|staff_2|staff_3 — Which slot to assign. All slots hold a single role.
- • @role — The role to assign to the chosen slot.
Requires: Admin only
/modconfig removerole
ProClear the role assigned to a staff slot.
/modconfig removerole <admin|moderator|retired_staff|staff_1|staff_2|staff_3> @role- • admin|moderator|retired_staff|staff_1|staff_2|staff_3 — Which slot to clear.
- • @role — The role to remove.
Requires: Admin only
/modconfig show
ProDisplay the current moderation configuration.
/modconfig showRequires: Admin only
/modconfig recruit
ProAssign a member to a staff role. Any other configured staff roles they currently hold are removed first, making this command work for first-time recruitment, promotion, and demotion alike. Removes the Retired Staff role if they have it. Requires admin, mod, and retired staff roles to all be configured first.
/modconfig recruit @user <admin|moderator|staff_1|staff_2|staff_3> [public] [channel]- • @user — The member to recruit (required).
- • admin|moderator|staff_1|staff_2|staff_3 — The role slot to assign (required).
- • public — Post the announcement publicly in this channel (optional).
- • channel — Send the announcement to a specific channel instead (optional).
Requires: Admin only
When public or a channel is specified, the recruited member is mentioned alongside the embed. The action is always logged in the configured moderation log channel.
/modconfig fire
ProRemove a member from the staff team. Strips all configured staff roles (admin, moderator, and all staff position slots) and assigns the Retired Staff role. Requires admin, mod, and retired staff roles to all be configured first.
/modconfig fire @user [public] [channel]- • @user — The member to retire (required).
- • public — Post the announcement publicly in this channel (optional).
- • channel — Send the announcement to a specific channel instead (optional).
Requires: Admin only
All configured staff roles are removed in one action — no role selection required. The retired member is never mentioned, even when the announcement is posted publicly. The action is always logged in the configured moderation log channel.
/modconfig fireall
ProFire every member that holds any configured staff role (admin, moderator, staff 1/2/3) in a single pass. Each member has their staff role stripped and the Retired Staff role assigned. A two-step confirmation preview shows the per-role breakdown before any change is made. Requires admin, mod, and retired staff roles to all be configured first.
/modconfig fireall [public] [channel]- • public — Post the announcement publicly in this channel (optional).
- • channel — Send the announcement to a specific channel instead (optional).
Requires: Admin only
The response embed shows a consolidated summary (members fired, per-role breakdown, retired role assigned count). Fired members are never individually mentioned, even when the announcement is posted publicly. The audit log embed posted to the moderation channel additionally carries the invoker and timestamp. Members the bot cannot demote (role hierarchy) are skipped and surfaced as 'N failed' in the response.
/modconfig unretire all
ProRemove the Retired Staff role from every member that currently holds it. Two-step confirmation preview shows the affected member count before any change is made.
/modconfig unretire all [public] [channel]- • public — Post the announcement publicly in this channel (optional).
- • channel — Send the announcement to a specific channel instead (optional).
Requires: Admin only
/modconfig unretire staff
ProRemove the Retired Staff role from a single member. Idempotent — returns a friendly message if the member does not currently hold the role.
/modconfig unretire staff @user [public] [channel]- • @user — The member to unretire (required).
- • public — Post the announcement publicly in this channel (optional).
- • channel — Send the announcement to a specific channel instead (optional).
Requires: Admin only
/modconfig tagenforcement
ProOpt in to an automatic 15-minute background scan that retires staff members who are not displaying the server (clan) tag. Off by default. Uses the same fire flow as /modconfig fire — strips all configured staff roles and assigns the Retired Staff role.
/modconfig tagenforcement <enabled> [channel]- • enabled — True turns the scan on; False turns it off.
- • channel — Text channel where the retirement embed is posted with a mention of the fired staff member. Required the first time you enable the feature; kept across toggles so re-enabling later does not require re-specifying it.
Requires: Admin only
The retirement embed is posted twice: once to the moderation log channel (no mention, same as manual /modconfig fire) and once to the notify channel (with a user mention so the fired staff sees it). The same toggle and notify-channel picker are also available under `/settings → Moderation → Staff tag enforcement` as a `🏷️ Tag Enforcement: On/Off` button and a `📢 Notify Channel` button — both surfaces enforce the same "notify channel must be set before enabling" rule. Requires admin, mod, and retired staff roles to all be configured first. Once fired, a staff member is not automatically rehired if their tag reappears — an admin must run /modconfig recruit to reinstate them. Bots and the guild owner are never auto-fired.