Role Commands and Bulk Roles

​

Overview

!role add <user> <roles> [reason]
!role remove <user> <roles> [reason]
!role temp <user> <role> <duration>
!role temp-list
!role all <role> [remove] [preview] [without] [reason]
!role humans <role> [remove] [preview] [reason]
!role has <filter_role> <target_role> [remove] [without] [preview] [reason]
!role bots <role> [preview] [reason]
!role bots-remove <role> [preview] [reason]
!role job [status|pause|resume|cancel]
!role cancel

!role @Mia Member
!role temp @Mia VIP 3d
!role all @Member
!role humans @Newcomer preview
!role has @Veteran @Elder --joined_before 365d
!role all @Old remove --max_roles 1 cleaning up the server
!role job pause

​

One role at a time

• add and remove take one or more roles (mentions, IDs or names). Petto says which ones it could not give and why, in your language: the role is above Petto, above you, or managed by an integration.
• temp gives a role for a while (up to one year) and Petto takes it away when the time is up. If the member already had the role, Petto says so: it will still be taken away. temp-list shows who has a temporary role and when it ends.
• A temporary role that you take away by hand, or give for good with add, is forgotten, so the timer never removes it later.
• group create|delete|view|list|give|take keeps named sets of roles to give or take in one go.
• create, delete, edit, color, icon, mentionable, hoist, topcolor, list and in manage the roles themselves.

​

Bulk roles

• One job per server at a time. A new one waits until the running one ends.
• Safe on big servers. Members are read in pages of 1000, never all at once, and Discord’s own limit paces the changes.
• It survives a restart. If Petto restarts while a job runs, the job goes on from the member where it was.
• A card follows it in the channel: members checked, changed, already fine and failed, the time left, and what to do to pause or cancel it. When it ends the card shows the result and how long it took.
• It stops by itself if Discord refuses 15 members in a row, which means Petto lost the permission or the role moved above its own.
• A member who left while the job ran is counted as already fine, not as a failure.

​

Options

​

Preview, status, pause and cancel

​

Join roles and sticky roles

• /role join add|remove|list|clear|apply is !joinrole: roles given when a member joins. apply gives a join role now to the members who are already in the server.
• /role sticky enable|disable|status is !stickyroles: Petto gives back a member’s roles when they return.

​

The Roles page of the dashboard

1. Choose the role and whether to assign or remove it. Roles Petto cannot give are greyed out with the reason. A role with powerful permissions shows a warning and a box to confirm.
2. Choose who: all members, humans or bots, a join date range (real date pickers, plus buttons for the last 7, 30 or 90 days and for older than 30 days, 90 days or a year), how many roles they have, roles they must have or must not have (any or all of them), and whether to skip members who have not accepted the rules yet.
3. Add a reason for the audit log and, if you want, a channel to be told when it ends.
4. Press Preview to see how many members would change, or Start. After a preview, Run it for real starts the same job.
5. Follow the job: a progress bar, members checked, changed, already fine and failed, the time left, and Pause, Resume and Cancel. The page keeps itself up to date.
6. Recent jobs lists the last ones with their result and, if a job failed, why: Petto is missing Manage Roles, the role was deleted, it is managed, it is above Petto, and so on.