Skip to main content

RoleLogic v1.20.0

Release Date: October 13, 2026

What's New​

Edits to a Running Role Condition No Longer Pause It​

Until now, when an edit to a live role condition needed your confirmation, the condition was taken away from the bot while it waited. That stopped more than the edit: the old version stopped too, and so did the role locks it held, so other conditions could act on members it had been keeping. To stay safe, the save often had to pause those conditions as well.

Now the condition keeps running exactly as it was while your edit waits:

  • The rule editor opens your saved edit under Changes waiting for your confirmation, with Review and apply and Discard changes. Discarding asks first, then drops the edit and leaves the running condition untouched.
  • Saving again replaces the waiting edit and checks it again.
  • Switching a running condition off works the same way: it keeps running until you confirm.
  • An edit that does not move the condition keeps its place in the priority order when it is applied.
  • Apply runs the save's checks again at that moment. The roles must still exist and be manageable, you must still manage every server the edit reaches, and it must not duplicate another condition or create a loop. If anything has changed, the edit is refused and keeps waiting rather than going out unchecked.
  • The Testing Sandbox tests the waiting edit, so you can try it before applying it.

New role conditions, and edits to conditions that are not running, still wait without running until you apply them, as before. Messages in the save toast, status bar, sidebar and review dialog now say plainly that the condition keeps running.

Impact Checks Count Everything a Change Causes​

When several role conditions use the same role, the first one in priority order to act on it holds it for that pass. So switching a condition off, narrowing it or moving it down can hand its members to the next condition, whose else branch may then remove the role. Previously the safety check only looked at the condition you edited, so a knock-on change like that could go live without a confirmation.

The impact check now compares what runs now with what would run after your change, member by member, and counts only the changes your edit causes, wherever they land:

  • Knock-on changes are judged. A change that lands on another condition counts toward the safety limits like one on the condition you edited.
  • Limits are per role across all conditions. Two conditions that each remove a role from 40 members count as 80.
  • Moderation roles are checked in every server. Granting a role with moderation permissions in another server is caught, judged by that server's own permissions.
  • Other conditions that would pause are named. If applying your change means other conditions must wait too, the dialog lists them and says whether they keep running meanwhile.
  • Deleting is covered. Deleting a condition still takes effect at once. If that hands members to other conditions beyond the limits, those conditions are put on hold for you to check.

Check impact now tells you what Save would actually do: go live, wait for your confirmation, or be refused (for example, a draft that would form a loop or uses a role the bot can't manage). It also says when you edited the draft while the check was running, with Check again, when the server is paused, when the draft switches the condition off, and how many changes were already waiting. Sampled estimates are now refreshed after 60 seconds instead of 5 minutes.

Cross-Server Changes Are Counted Properly​

For cross-server sync rules, the impact check could show 0 members affected while listing large changes per server, drop servers after the eighth, repeat the same reason once per server, and not scroll. Now:

  • Changes in other servers are counted against each destination server's current members, and only members who are actually in that server and would really gain or lose the role count.
  • Those changes are part of the headline numbers, with one line per destination server (for example Also in Lounge: +12 / −3) and a note such as Includes changes in 3 other servers.
  • If a destination server's members can't be read at that moment, its numbers are marked as an estimate and the server is named under Things to double-check.
  • The quarter-of-holders and moderation-permission checks apply in destination servers too.
  • Staged rollouts include changes in other servers in their first slice and progress count, and Undo changes now restores roles the deployment changed in other servers as well.
  • The review dialog scrolls, and long role and server lists are folded.

"Already Match" Counts​

A role condition that has already run changes nobody, and the estimate used to show 0 members, 0 additions, 0 removals, which read like "this applies to no one". The estimate now also shows how many members already match: the member tile, each role line (already have it / already lack it), destination-server lines, the save message and the AI approval card all include it. Members who already match are never written to and don't count toward any safety limit.

Deployments That Stop Early Explain Why​

When a deployment can't finish, the status bar now says why in plain words, for example that the role conditions changed between the check and the start, another deployment was still running, or the member list couldn't be read from Discord. The bot's exact message is available behind the info toggle, and you can Dismiss the row once you've read it.

Changes to How Rules Run​

  • The bot checks before catching up on newly reachable roles. When RoleLogic's own role moves up, or it is given Manage Roles, roles it could not change before come within reach, and waiting conditions could catch up all at once. That catch-up is now measured first. If it crosses the safety limits, the conditions involved wait for your confirmation and the review dialog says why. Otherwise they keep running. Renaming, recolouring or reordering roles without moving any past RoleLogic's role triggers no check.
  • Starting again after a safety stop is checked in full. If your rules were stopped by a safety stop, the next save or delete starts them again, so it is now checked like Start Live: everything the rules would do, not only your edit.
  • Conditions attached to different logs run in a fixed order. Role conditions that post to different logs are evaluated as separate groups. Those groups now always run in the priority order of their first condition. Previously the order could vary from one pass to the next, so when two groups touched the same role a member could occasionally end up with different roles, and an estimate could disagree with the sweep that followed it. Servers where such groups interact settle on the priority order once, after this update.
  • Disabled Role Links hold nothing. A disabled link removes no one, so it no longer holds large removals. Turning a link off, or marking it as a trusted integration, clears its held removal. When you turn it back on, the bot compares the list with who has the role and holds a large removal then if needed.

Bug Fixes​

Live Rules No Longer Pause After Reordering Roles​

A server owner found every role condition switched to "needs review" at once, logged as "The impact of this change could not be checked", after dragging one role in Discord. Each role that shifted set off its own background re-check, the checks crowded each other out and timed out, and every failed check paused the whole live rule set.

Background checks that nobody asked for now never pause running conditions just because they couldn't run. They pause only what their own numbers point to. Re-checks run one at a time per server, spaced out and retried once, and holds left by the old behaviour are cleared automatically within a few minutes (after confirming the roles they use still exist). Saves, Start Live and resuming a condition still wait for your confirmation when their impact can't be checked.

Every Held Rule Can Be Confirmed​

A held role condition could say "Waiting for your confirmation" with no Review and apply button, which was reported as a display bug on mobile. The rule's pending check could be retired by an unrelated edit or a dismissal, and the status listed at most five. Each held condition now always has its own numbers, the status lists every confirmable change, and the editor banner always offers Review and apply, getting fresh numbers when needed. Conditions stuck in this state are fixed on the first click.

An integration that sends its whole list on a timer, or the bot's next scan of a held link, posted a fresh "held" entry to the Activity Log every time, so an unanswered hold repeated every few minutes. A held removal is now announced when it starts and again only after a day without an answer. Repeats update it quietly, and an integration retrying the same list within the hour keeps the same change ID, so a retry with it still confirms.

On the Role Link card, Apply removals now asks before removing the role, showing how many members will lose it. The hold notice also explains that turning the link off or deleting it stops the removal without taking the role from anyone.

Other Fixes​

  • The loop message in Check impact no longer replaces every letter "s" with a space.

AI Connections​

  • The assistant approval screen shows the same impact details as the dashboard: knock-on changes, other conditions that would pause, already-matching members, and whether the condition keeps running while it waits.
  • Listing rules shows which are paused and which have an edit waiting, and viewing a rule shows its waiting edit in full.
  • An assistant can no longer switch a condition on or off while an edit to it is waiting, because that would apply or drop the edit without your review. Updating or deleting such a condition comes with a warning.

Website, Privacy and Security​

  • Faster pages. The dashboard, editor and other app pages now load on demand instead of all at once. The homepage's initial download is roughly half its previous size, and in our tests on a slow mobile connection it appears in about 2.5 seconds instead of 4. Opening the editor from a server's overview is quicker too, because its code is fetched in the background. A tab left open across an update recovers on its own instead of showing a broken link.
  • Faster integration and guide pages on phones. The background glow at the top of these pages is now drawn in a much cheaper way that looks the same.
  • Old and mistyped links lead somewhere useful. Older addresses (such as the previous plugin catalog links and /invite) and common wrong guesses at page addresses now redirect to the right page. Any other unknown address shows a not-found page that suggests Did you mean this page? when one page clearly fits, plus links to popular pages.
  • A one-minute explainer video on the homepage shows a rule handing out a role and taking it back, then Twitch subscribers getting a role in two servers at once. It has English captions and loads nothing until you press play.
  • Analytics consent. Google Analytics now respects your choice. Visitors in Europe, or whose time zone can't be read, are asked first and nothing is loaded until they accept. Elsewhere, analytics is on by default and can be turned off at any time. A Cookie settings link in the footer lets you change your choice, declining deletes the analytics cookies, and a browser's Global Privacy Control signal is treated as declining. The documentation site follows the same choice.
  • Discord IDs are never sent to Google. Server IDs are removed from page addresses before analytics records them, and dashboard pages report a generic title instead of your server's name. Integration-page video thumbnails are now served by RoleLogic instead of loading from Google.
  • An updated Privacy Policy (effective October 1, 2026) describes what RoleLogic actually stores and for how long, explains that member lists are kept in memory only, lists the permissions the bot needs (Manage Roles and Manage Webhooks), and explains that data for a removed server is deleted on request.
  • Safer login links. After signing in, RoleLogic now only returns you to a page on its own site, so a crafted login link can no longer send you somewhere else.
  • Easier to find guides. The site footer now has a Guides row, and the homepage lists every integration. Integration pages answer a few more common questions, and two answers were corrected: Genshin stats refresh every 30 minutes at best, and form quizzes allow configurable retries.

Improvements​

  • Rule optimization waits for waiting edits. Optimize Rules now waits until every waiting edit is applied or discarded, so it works on the role conditions that will actually run.
  • Clearer review dialog. It now opens with what paused the condition: a save, the bot's re-check of newly reachable roles, or a deletion that changed what other conditions do.
  • Documentation. The Discord role hierarchy page is expanded with how to move roles, the troubleshooting guide has been reorganized, the Safe Apply section explains everything above, and each release note now has a descriptive title.
  • Fully translated. Everything new in this release is available in English, Arabic, German, Spanish, French, Malay, and Brazilian Portuguese.
Last updated on