Build conditions

Conditions let an event trigger skip events that do not match. Top-level conditions are joined by AND — all of them must match. Use an OR-group when any one of several alternatives is acceptable.

If you add no conditions, the trigger fires on every occurrence of the selected event.

See the full operator and field reference in Trigger conditions.

Add a single condition (AND)

1. Open a trigger’s editor (create or edit an event trigger).
2. In the If section, click Add condition.
3. A new row appears with three controls:
   • Field — the event field to check, such as player.name, message, or weapon. The available fields depend on the event selected in When.
   • Operator — how to compare: $eq, $ne, $contains, $ncontains, $regex, $gt, $gte, $lt, $lte, $has, $lacks.
   • Value — the value to match against.
4. Repeat to add more conditions. All top-level conditions must match (AND).
5. To remove a condition, click the trash icon on that row.

Add an OR-group

Use an OR-group when multiple alternative values are acceptable — for example, a message contains !ban or !voteban.

1. In the If section, click Add OR-group.
2. A bordered group appears with two leaf rows already inside.
3. Set the field, operator, and value for each leaf. Leaves inside a group are joined by OR — the group passes if any one leaf matches.
4. Click Add to group to add more alternatives inside the group.
5. Click Remove group to delete the whole group.
6. To remove a single leaf, click its trash icon (disabled when only one leaf remains). To remove the whole group — including its last leaf — click Remove group instead.

Combining AND and OR

Top-level items (single conditions and OR-groups) are always joined by AND. For example:

• Condition: channel $eq ChatTeam
• OR-group: message $contains voteban OR message $contains !voteban

This fires only when the channel is ChatTeam AND the message contains either variant.

Using regex

Select $regex as the operator, then enter a regular expression pattern (max 256 characters, matching is case-insensitive). The editor validates the pattern when you save. Avoid nested unbounded quantifiers such as (a+)+ — these are rejected as potentially unsafe.

Operator reference

The table below covers the most common operators. For the complete list (including $nregex, $exists, $nexists, and others), see Trigger conditions reference.

Operator	Passes when
$eq	field equals value exactly
$ne	field does not equal value
$contains	field contains value (case-insensitive)
$ncontains	field does not contain value
$regex	field matches the regex pattern
$gt / $gte	field is greater than / greater than or equal to value (numeric)
$lt / $lte	field is less than / less than or equal to value (numeric)
$has	field’s comma-separated list includes value
$lacks	field’s comma-separated list does not include value

See also

• Trigger conditions reference
• Create an event trigger