Skip to main content

Condition Types

Conditions are the "IF" part of your rules. They determine which members a rule applies to by checking their current roles.

Understanding Conditions​

Every condition asks a question about a member's roles:

  • Does this member have certain roles?
  • Is this member missing certain roles?
  • How many roles from a specific set does this member have?

When the answer matches your criteria, the condition is "true" and the rule's action fires.

Basic Role Conditions​

These conditions check whether members have or lack specific roles.

Has Some Roles​

Matches if: The member has at least one of the specified roles.

Use case: Trigger actions when a member has any qualifying role.

Example:

IF member has some of [Booster, Premium, VIP] THEN add Exclusive-Access

This fires if the member has Booster OR Premium OR VIP (or any combination).

Has All Roles​

Matches if: The member has every single one of the specified roles.

Use case: Require multiple qualifications before triggering.

Example:

IF member has all of [Verified, Level 10, Active] THEN add Trusted-Member

This only fires if the member has ALL THREE roles.

Lacks Some Roles​

Matches if: The member is missing at least one of the specified roles.

Use case: Target members who don't meet all requirements.

Example:

IF member lacks some of [Verified, Rules-Accepted] THEN add Needs-Setup

This fires if the member is missing Verified OR Rules-Accepted OR both.

Lacks All Roles​

Matches if: The member has none of the specified roles.

Use case: Target completely new or unassigned members.

Example:

IF member lacks all of [Bronze, Silver, Gold, Platinum] THEN add No-Tier

This only fires if the member has NONE of the tier roles.

Threshold-Based Conditions​

These conditions count how many roles a member has from a specified set, then compare against a number you choose.

Exactly N Roles​

Matches if: The member has exactly N roles from the set.

Example:

IF member has exactly 1 of [Bronze, Silver, Gold] THEN add Single-Tier

Only fires if the member has precisely one tier role (not zero, not two).

At Least N Roles​

Matches if: The member has N or more roles from the set.

Example:

IF member has at least 2 of [Helper, Mod, Admin, Owner] THEN add Multi-Staff

Fires if the member has 2, 3, or 4 of these staff roles.

At Most N Roles​

Matches if: The member has N or fewer roles from the set.

Example:

IF member has at most 1 of [Warning-1, Warning-2, Warning-3] THEN add Good-Standing

Fires if the member has 0 or 1 warning roles.

More Than N Roles​

Matches if: The member has more than N roles from the set.

Example:

IF member has more than 3 of [Badge-1, Badge-2, Badge-3, Badge-4, Badge-5] THEN add Badge-Collector

Fires if the member has 4 or 5 badges (not 3 or fewer).

Less Than N Roles​

Matches if: The member has fewer than N roles from the set.

Example:

IF member has less than 2 of [Daily-1, Daily-2, Daily-3] THEN add Needs-Activity

Fires if the member has 0 or 1 daily roles (not 2 or more).

Quick Reference Table​

Condition TypeMatches When
Has Some RolesMember has any of the roles
Has All RolesMember has every role
Lacks Some RolesMember is missing any role
Lacks All RolesMember has none of the roles
Exactly NMember has precisely N roles
At Least NMember has N or more roles
At Most NMember has N or fewer roles
More Than NMember has over N roles
Less Than NMember has under N roles

Combining Conditions (AND Logic)​

For more precise targeting, you can add up to 9 additional conditions that must ALL be true.

How It Works​

When you click "Add AND Condition," you create a second condition that must also match. Both conditions need to be true for the rule to fire.

Example: Multi-Condition Rule​

IF member has some of [Verified] AND member has at least 2 of [Event-1, Event-2, Event-3, Event-4] AND member lacks all of [Banned, Muted] THEN add Event-Regular

This rule only fires when ALL THREE conditions are met:

  1. Member is Verified
  2. Member participated in 2+ events
  3. Member is not Banned or Muted

Choosing the Right Condition​

For Simple "Has This Role" Checks​

Use Has Some Roles with a single role:

IF has some of [Verified] → THEN add Member-Channel-Access

For "Has Both X and Y" Checks​

Use Has All Roles:

IF has all of [Verified, Level-10] → THEN add Trusted

For "Missing Setup" Checks​

Use Lacks All Roles to find members without any setup:

IF lacks all of [Verified, Pending-Verification] → THEN add Needs-Verification

For Tier/Level Systems​

Use threshold conditions:

IF has at least 1 of [Tier-1, Tier-2, Tier-3] → THEN remove No-Tier

For Complex Requirements​

Combine multiple conditions:

IF has all of [Verified, Active] AND lacks some of [Warned, Muted] → THEN add Trusted

Tips and Gotchas​

Empty Selections​

You must select at least one role for each condition. Empty role selections aren't allowed.

The @everyone Role​

Every member has the @everyone role. Include it in your testing when using "Lacks" conditions.

Role Changes Mid-Processing​

If rules cascade (one rule triggers another), conditions are re-evaluated with the updated roles after each rule fires.

Performance with Many Conditions​

Using many AND conditions is fine—RoleLogic handles them efficiently. However, simpler rules are easier to understand and maintain.

Next Steps​