Mass Roles

Give a role to many members in one go, or take it away. You see who is affected first, confirm by typing the role name, watch the progress, and can cancel or undo.

Pre-alpha — not open yet. It is switched on for testers only.

How a job runs

1. Pick the server, the role and whether to give or take it.
2. Choose who it applies to: everyone, only people, only bots — optionally only members who have (or don't have) another role.
3. CloudMod shows a preview: how many members are affected and how many are skipped (they already have the role, or never had it).
4. Type the role name to confirm. Nothing starts without this step.
5. CloudMod works through the list slowly, because Discord limits how fast roles can change. Watch the progress bar, or cancel at any time — members already changed stay changed.
6. When it ends, the job is written to your log channel and the audit log.

Limits

• Up to 1000 members per job and 3 jobs per server per day.
• Only one job at a time runs on a server.
• The role must sit below the CloudMod role, and CloudMod needs Manage Roles.

Roles that are never handed out

A role that carries any of these permissions can't be given with Mass Roles: Administrator, Manage Server, Manage Roles, Manage Channels, Manage Webhooks, Ban Members, Kick Members, Moderate Members, Mention Everyone. It's a safety rule so a slip can't hand out power by accident. You can still take such a role away from many members.

Undo

A finished job can be undone for 7 days. The undo only touches the members the job actually changed — never everyone with the role. After 7 days the list of those members is deleted, and the undo is no longer possible.

Good to know

• CloudMod re-checks the role before every batch. If the role changes, or the plugin is switched off, the job stops.
• If many changes fail in a row, the job stops by itself instead of repeating the same error.
• This plugin doesn't use up one of your plugin slots.