Skip to main content

Understanding Rules

A rule is the heart of RoleLogic. It's an automated instruction that tells RoleLogic exactly what to do when certain conditions are met.

What Is a Rule?​

Every rule answers two questions:

  1. WHEN should this happen? (the condition)
  2. WHAT should happen? (the action)

Here's a simple example:

IF a member has the "Server Booster" role THEN add the "VIP" role

Once this rule is active, RoleLogic automatically:

  • Adds "VIP" to all current boosters who don't have it
  • Adds "VIP" to anyone who becomes a booster
  • Keeps "VIP" on former boosters (unless you create another rule to remove it)

Parts of a Rule​

1. Description (Optional)​

A friendly name for your rule. This helps you remember what each rule does when you have many.

Good examples:

  • "Auto-VIP for Boosters"
  • "Remove Unverified when Member assigned"
  • "Staff gets Mod role"

2. Condition (IF)​

The condition defines which members this rule applies to. You choose:

  • Condition type: How to check for roles (has some, has all, lacks some, etc.)
  • Roles to check: Which roles to look for
  • Threshold (for some conditions): A specific number like "at least 3"

You can add multiple conditions combined with AND logic for more precise targeting.

See all condition types →

3. Action (THEN)​

The action defines what happens when a member matches the condition:

  • Add roles: Give the member one or more roles
  • Remove roles: Take away one or more roles

You can combine both actions in a single rule—adding some roles while removing others.

Learn more about actions →

4. Priority​

Priority determines the order in which rules run when multiple rules could apply.

  • Priority 0 runs first
  • Priority 1 runs second
  • And so on...
Each rule must have a unique priority

No two rules can share the same priority number. Each rule needs its own unique priority value. If you try to save a rule with a priority that's already in use, you'll need to choose a different number.

This matters when rules depend on each other. For example:

  • Rule A (priority 0): If member has "Trial", add "Member"
  • Rule B (priority 1): If member has "Member", remove "Trial"

Rule A runs first to add "Member", then Rule B runs to remove "Trial".

5. Enabled/Disabled Status​

You can turn any rule on or off without deleting it:

  • Enabled: The rule is active and processing
  • Disabled: The rule is saved but not running

This is useful for:

  • Temporarily pausing a rule during maintenance
  • Keeping seasonal rules ready but inactive
  • Testing new rules before fully committing

Creating Your First Rule​

Step 1: Open the Rule Editor​

In your server's dashboard, click "Add New Rule".

Step 2: Set the Condition​

  1. Choose a condition type (like "Has Some Roles")
  2. Select which roles to check
  3. If needed, add more conditions with the "Add AND Condition" button

Step 3: Set the Action​

  1. Choose an action type (Add Roles or Remove Roles)
  2. Select which roles to add or remove
  3. Optionally add a combined action to do both

Step 4: Configure Settings​

  1. Add a description so you remember what this rule does
  2. Set the priority if order matters
  3. Leave it enabled (default) to activate immediately

Step 5: Save​

Click "Save Changes". Your rule is now live!

How Rules Are Processed​

Understanding the processing flow helps you design better rules:

1. Trigger Event​

Something causes a member's roles to change:

  • You or a moderator assigns a role
  • Another bot changes roles
  • Discord changes roles (like Server Booster)
  • RoleLogic's own rules add/remove roles

2. Rule Evaluation​

RoleLogic checks all enabled rules in priority order:

  • Does this member match Rule 0's condition? If yes, run the action.
  • Does this member match Rule 1's condition? If yes, run the action.
  • Continue for all rules...

3. Cascading Changes​

If any rule made changes, RoleLogic checks all rules again. This "cascade" continues until no more rules match.

Example cascade:

  1. Member gets "Level 10" role
  2. Rule A fires: "If Level 10, add Premium"
  3. Member now has "Premium" role
  4. Rule B fires: "If Premium, add VIP-Chat-Access"
  5. Member now has "VIP-Chat-Access" role
  6. No more rules match—done!

4. Safety Limits​

To prevent infinite loops, RoleLogic limits processing to 100 passes. If rules keep triggering each other beyond this, processing stops.

Rule Statuses​

Your rules can have different statuses:

StatusMeaning
EnabledRule is active and processing
DisabledRule is saved but not running
PendingRule is queued, waiting for first sync
StoppedRule was auto-stopped due to conflicts (see troubleshooting)

Best Practices​

Use Clear Descriptions​

Name your rules so you understand them at a glance:

  • ✅ "Remove Guest when Verified"
  • ❌ "Rule 7"

Start Simple​

Begin with basic rules before creating complex chains. Test each rule individually.

Consider Order​

Think about which rules should run first. Use priority numbers intentionally, not randomly.

Test Before Going Live​

Use the testing sandbox to verify your rules work as expected.

Review Periodically​

As your server evolves, review your rules. Remove outdated ones and update others as needed.

Combining Multiple Conditions​

For advanced targeting, you can add up to 9 additional conditions combined with AND:

IF member has "Verified" AND member has "Level 5" AND member lacks "Muted" THEN add "Trusted"

All conditions must be true for the action to trigger.

Combining Multiple Actions​

You can add one additional action type, allowing you to add AND remove roles in the same rule:

IF member has "Promoted" THEN add "Staff" AND remove "Trial Staff"

Next Steps​