-
Notifications
You must be signed in to change notification settings - Fork 0
Conditions
Maxime Tonie edited this page Apr 11, 2026
·
1 revision
Conditions let you control whether a trigger should fire based on the data values or player state. All conditions in the list must pass — if any one fails, the trigger is skipped entirely (the packet is still cancelled though).
conditions:
- "<left> <operator> <right>"Both sides support any placeholder, including {1}, %player_level%, and {math:...}.
| Operator | Meaning |
|---|---|
== |
Equal (case-insensitive) |
!= |
Not equal |
> |
Greater than (numeric) |
< |
Less than (numeric) |
>= |
Greater than or equal (numeric) |
<= |
Less than or equal (numeric) |
contains |
Left contains right (string) |
startswith |
Left starts with right (string) |
endswith |
Left ends with right (string) |
Only fire if the XP value is greater than 0:
conditions:
- "{1} > 0"Only fire for players at level 10 or above:
conditions:
- "%player_level% >= 10"Only fire if the quest name contains "daily":
conditions:
- "{1} contains daily"Only fire if a calculated value is above a threshold:
conditions:
- "{math:{1}*2} > 100"Multiple conditions — all must pass:
conditions:
- "{1} > 0"
- "%player_level% >= 5"
- "{2} != 0"