Description
Currently every event that matches a trigger goes off, with no way to control order or exclusivity. For setups with many events on the same trigger type (like chat messages), a single message can trigger several unrelated events at once. It would be nice to have a numeric priority field per event, plus a per-event "stop further events for this trigger" toggle, allowing user to have a "first match wins" system when enabled. Preset effect lists inside one dispatcher event partially cover this, but that collapses everything into a single event entry, costing the user ability to disable/enable individual events, and making the whole rule set a single, hard to navigate block instead of a searchable list.
Submitted By
murphyowo
Created via Discord.
Description
Currently every event that matches a trigger goes off, with no way to control order or exclusivity. For setups with many events on the same trigger type (like chat messages), a single message can trigger several unrelated events at once. It would be nice to have a numeric priority field per event, plus a per-event "stop further events for this trigger" toggle, allowing user to have a "first match wins" system when enabled. Preset effect lists inside one dispatcher event partially cover this, but that collapses everything into a single event entry, costing the user ability to disable/enable individual events, and making the whole rule set a single, hard to navigate block instead of a searchable list.
Submitted By
murphyowo