Server Roles - CosmicCubicle/PariahBot GitHub Wiki
Server Roles
The roles PariahBot's features depend on, set with /setup. Set these
first. Several features won't work without them.
| Role | How many | What it's for |
|---|---|---|
| Admin roles | Any number | Who counts as an admin, besides Administrators |
| Mod roles | Any number | Who counts as a mod: staff below admin |
| Member role | One | What Verification grants, and who can see Role-Menus channels |
| Streamer role | One | Who can link their own channel for Streamer-Alerts |
All /setup commands are admin-only.
Staff levels
| Level | Who |
|---|---|
| Admin | Discord's Administrator permission, or an admin role (/setup admin-role add) |
| Mod | A mod role (/setup mod-role add), or any admin |
| User | Everyone else |
| Admins can | Mods can |
|---|---|
Everything mods can, plus: /setup (roles, including these), /security (verification and honeypot), the Admin-Dashboard, /mod config and /mod remove-case, and /bannedwords on/off and lists |
Every other staff command: moderation (/mod warn, kick, ban, timeout, history, and right-click actions), /alerts, /autodelete, /voice, /roles, /streamers, /instagram, /rss, /giveaway, and custom banned words |
The split keeps server setup, and the power to erase records of what staff did, with admins. Day-to-day moderation is for mods.
Admins and mods are both staff: the bot never acts against either. The
Honeypot skips them, and /mod can't target them.
Upgrading from before admin roles existed? Mod roles used to count as admin. They're now mods only, so until you add an admin role, only members with Administrator can use
/setup,/securityand the dashboard.
Admin roles
/setup admin-role add role:@Admins
/setup admin-role remove role:@Admins
/setup admin-role list
/setup admin-role clear
Discord's Administrator permission always counts as admin, with or without an admin role.
Mod roles
/setup mod-role add role:@Moderators
/setup mod-role add name:Helpers color:Green
/setup mod-role remove role:@Helpers
/setup mod-role list
/setup mod-role clear
Members holding any mod role:
- can use every staff command marked (Mod), but not the (Admin) ones
- are never removed by the Honeypot
- can force-claim a temp voice channel with
/vc claim, and can't have theirs claimed (see Temp-Voice-Channels) - can still see the screening channel when Verification hides it
Manage Channels alone doesn't make someone a mod or an admin.
Member role
/setup member-role role:@Members
- Verification grants it when someone passes, and refuses to run until it's set.
/roles apply-channel-defaultsuses it to decide who can see a role-menu channel. Without one, everyone can.
Streamer role
/setup streamer-role role:@Streamer
Members with it can link their own Twitch or YouTube channel with /streamers link. Their alerts stop if they lose the role. Mods and admins can add channels without
it. See Streamer-Alerts.
Options
member-role, streamer-role, admin-role add and mod-role add all work the same way. Give
exactly one of:
| Option | Effect |
|---|---|
role |
Use an existing role |
name, plus optional color |
Create a new role with that name. color is a hex code (#3498db) or a Discord colour name (Red, DarkBlue, Blurple) |
clear: true |
Unset it (member-role and streamer-role only) |
Creating a role needs the bot to have Manage Roles. Choosing an existing one doesn't. See Permissions.