Skip to main content

RoleLogic v1.19.0

Release Date: September 11, 2026

What's New​

Safe Apply — Know What a Change Will Do Before It Runs​

The costliest RoleLogic mistake is a role condition saved the wrong way round. By the time anyone notices, a role has been removed from — or handed to — a large part of the server. Safe Apply is built so that a change like that is something you see coming, confirm on purpose, and can take back.

Every save is estimated first. When you save a role condition, the bot works the new rule set out against your server's current member list and counts who would gain or lose which roles. The save message tells you how many members will change, and until the change goes live the status bar shows that count, with role removals and additions, beside the Going live at time. Details lists the affected roles, largest first, with the share of each role's current holders the change touches. When an exact count isn't possible, the numbers are marked as an estimate from a sample.

Check before you save. A new Check impact button in the unsaved-changes bar runs the same estimate on your draft without saving it.

Ordinary changes stay quick. A saved change that stays within your server's safety limits goes live on its own about a minute after you save — enough time to catch a typo, short enough not to be a wait. This replaces the previous delay of up to an hour after saving. To stop a change before it goes live, press Pause Live (previously labelled Extend Time).

Large changes wait for one confirmation. A change is saved but put on hold — the bot does not receive it — when, for any single role, it would:

  • remove the role from about 3% of your members or more (at least 10 members, and at most 100 before trust widens it);
  • remove the role from a quarter or more of the members who currently hold it (at least 10);
  • add the role to about 20% of your members or more (at least 25, and at most 1,000 before trust widens it);
  • grant a role that carries moderation permissions, such as Administrator, Manage Server, Manage Roles, Ban Members or Kick Members;
  • or when the rule removes roles while matching every member, or through an else branch — the classic sign of an inverted condition.

A Review before applying dialog shows the numbers and the reasons. Apply is a single button, and Keep on hold changes nothing. If other role conditions changed after the numbers were shown, Apply checks again first: a change that is now within the limits goes ahead, and otherwise you see the current numbers. If the bot can't estimate a change at the moment you save it — during a restart, for example — the change is held the same way, so nothing goes live unchecked.

Limits that grow with a good track record. The removal and addition limits widen by 1.5× for every deployment that finishes cleanly and stays that way for 72 hours, up to 8×. A safety stop, a paused staged rollout or an undo resets them. The quarter-of-holders, moderation-permission and inverted-condition checks never widen.

The riskiest changes roll out in stages. When a confirmed change removes a role from four times the removal limit or more, or grants a role with moderation permissions, it is first applied to a small slice of the affected members — 2%, at least 25, with the server owner and admins first — and then pauses for 10 minutes (5 on Premium). If moderators start undoing those first changes, RoleLogic pauses the rollout instead of continuing. Continue now skips the wait, and Stop ends it at any point.

Undo. Every role the bot adds or removes is now recorded. For 24 hours after a deployment finishes, Undo changes puts the roles it changed back the way they were. A role that has changed again since — by a moderator, another bot or another rule — is left alone. The rules behind the deployment are put on hold so they don't redo it; edit a rule or press Resume when you're ready.

One status bar for all of it. The status bar above your rules now shows, in one place:

  • a deployment in progress, with a progress bar;
  • the staged-rollout countdown, with Continue now and Stop;
  • changes waiting for your confirmation, with Review and apply;
  • rules on hold, with the reason and a Resume button;
  • the last finished deployment, with Undo changes.

Deployments that changed nothing are left out.

Rules the Bot Puts on Hold Itself​

Beyond the checks at save time, the bot now holds a rule instead of failing quietly when it can no longer act on it safely — and the status bar says why:

  • Hierarchy. If Discord refuses the bot permission to change a role three times in a row, every rule that changes that role is put on hold rather than retrying. Move the bot's role above it, then press Resume.
  • Role deleted. If a role used in a rule's conditions is deleted, the rule is held at once instead of acting on a condition that now means something different. Edit the rule, then resume it.

A rule is never held just for changing many members. Once a change has passed the checks at save and Start, large bursts — an event role reaching hundreds of members at once — run at your plan's normal pace.

Role Changes History​

The Activity Log has a new Role changes section: every role the bot added or removed, one line per member and role, with the role condition behind it, where the change came from (member update, scheduled sweep, deployment, cross-server, integration or undo) and what happened (applied, already so, no permission, member left, failed or skipped). Changes that someone later reversed are marked.

Paste a member ID, or click one, to see only that member — the quickest way to answer "why did this person lose that role?". You can also filter by outcome. History is kept for 30 days on Free and 90 days on Premium.

When an integration sends a list that would remove the role from a quarter or more of the current members (and at least 10) — or would empty the list — RoleLogic no longer applies it straight away.

  • The Role Link card shows how many members would lose the role, with an Apply removals button. After you confirm, the integration can send its list again for the next hour.
  • Integrations receive a 409 response with confirm_required and a change ID, and can retry within an hour using the X-RoleLink-Confirm header.
  • For integrations you run yourself, tick Trusted integration in the link's settings to skip the check.

Additions are never held.

A role can have members before it is ever linked to an integration — a hand-assigned supporter role, say. From the first sync on, the integration's list decides who has the role, so those members would lose it the moment the integration sent a list without them, and a removal below the threshold above would not even be held.

The New Role Link dialog now counts who holds each role before anything is created. The role picker shows the count beside each role, and choosing a role that already has members asks what should happen to them:

  • Hand the role over to the integration. Members not on its list lose the role at the first sync; a removal of a quarter or more of them (at least 10) waits for your confirmation as above.
  • Keep the current members. They are added to the link's list right away, so the first sync changes nothing, and a later list that drops them goes through the same confirmation. Offered when the count is exact and the role has no more members than your plan syncs per link.

A link cannot be created on such a role without one of these choices — the API refuses it too. Counts come from the bot's own member pass; on servers above 250,000 members they are an estimate from a sample, marked as such, and keeping members is not offered. If the bot cannot count at that moment, the dialog says so and only handing the role over is possible.

AI Connections See the Impact Too​

When a connected assistant proposes creating or editing a role condition, the review card now shows the estimated impact — members affected, role additions and removals — and says when the change would still wait for your confirmation in the dashboard after you approve it. Rule validation through the assistant also runs the new safety checks: conditions that match everyone, negative operators, else branches, grants of roles with moderation permissions, and roles the bot can't manage.

Changes to Pause, Start and Safety Stops​

  • Pause stays paused. Pausing now holds your rules until you press Start Live, instead of resuming on its own an hour later. The status bar reads "Paused — nothing is being applied" in yellow; red is kept for the bot's own safety stop.
  • Start checks first. Pressing Start Live now runs your whole rule set through the same estimate. Rules whose catch-up would reach many members come back on hold for your confirmation, and the rest go live immediately. If the estimate can't run, nothing starts until you confirm.
  • The safety stop scales with activity. The stop that triggers when someone keeps undoing the bot's changes now trips when reverts within 20 minutes reach 5% of the bot's own recent changes — at least 10, at most 20 — instead of a fixed 20. Quieter servers are protected sooner. To recover, fix the conflict and press Start Live; the rule set is estimated again first.
  • AI connections live in the account menu. The separate AI assistant button in the server sidebar has been removed. AI connections, including the pending-approval badge, are in your account menu.

Under the Hood​

Everything above runs on a rebuilt role-change queue in the bot, designed around Discord's limits:

  • Stale work is dropped, not sent. Queued changes carry the version of the rules that produced them. When you save, pause or stop, or when a rule is put on hold, work queued under the old rules is skipped instead of applied, and pausing stops the bot's queued work for your server at once.
  • Member events stay fast during big changes. Part of the bot's request budget is reserved for real-time member events, and they always go first, so a large deployment doesn't make a member wait for a role they just earned.
  • Removals are re-checked before sending. If a queued removal has waited more than 30 seconds and the member's roles have changed since it was planned, it is skipped and handled by the next update instead of being applied blind.
  • An invalid-request brake. The bot watches its own rejected requests and slows, then pauses, bulk work long before Discord would temporarily block it.
  • Adaptive pacing, and faster Premium rollouts. Pacing backs off when Discord rate-limits the bot and speeds up again after a run of successful changes. On Premium servers, large changes can now run at up to about twice the previous pace; Free pacing is unchanged.
  • Fewer audit-log entries. When one member gains and loses several roles at once, the bot now sends a single update, so it appears as one audit-log entry instead of several.
  • Cross-server and integration changes follow the target server's rules. Role changes delivered by a cross-server rule or an integration now go through that server's own queue, so they respect its pause, holds and pacing and appear in its role-change history.
  • Deployments survive restarts. A deployment in progress picks up where it left off after the bot restarts.

Bug Fixes​

Audit-Log Reasons Name the Right Rules​

The reason RoleLogic writes to Discord's audit log now names only the rules that actually caused each role change. Previously, a cross-server rule could be listed on an unrelated local change (appearing as two rule reasons in moderation logs), rules from your server could appear in the target server's reason, and rules whose change was undone later in the same pass could still be named.

A crash when shortening a very long reason containing characters such as emoji or non-Latin text has also been fixed. Deployments and undos are now labelled in the reason as well (Deployment and Undo #N).

Improvements​

  • Loop notice in the Testing Sandbox. When the selected roles make your role conditions undo each other, the sandbox now says "These role conditions loop" and explains that the bot changes nothing in that case, rather than leaving you with an empty result.
  • Held rules stand out. Held rules are marked in the sidebar and sorted under Needs attention, and the sandbox labels them on hold.
  • Safe Apply in the Activity Log. Holds, confirmations, resumes, deployments started, paused and finished, and undos are recorded with a one-line summary. Entries posted to your Activity Log channel in Discord include an Open in RoleLogic link.
  • Fully translated. Everything new in this release is available in English, Arabic, German, Spanish, French, Malay, and Brazilian Portuguese.
Last updated on