Please consider the option of being able to select a specific trigger for activation.
The common use-case that I see is when a user sets up additional triggers for the sole purpose of feeding data into conditions. For example, when a user is tracking the cooldown of a spell as their core trigger while tracking the spell overlay glow or a buff (or both) to determine when to show a glow.
The current solution of setting up a custom activation function just to do a basic return trigger[1] seems unfriendly to those unfamiliar with custom code, and may limit those users' ability to design what they want.
My ideal would be to add an entry to the "Required for Activation" drop-down for all existing triggers, allowing the user to select "Trigger 1" etc.
I do understand that this may lead to additional feature requests down the line asking for GUI options for more complicated trigger combinations but I think selecting a single trigger is a good middle-ground.
Hi,
Please consider the option of being able to select a specific trigger for activation.
The common use-case that I see is when a user sets up additional triggers for the sole purpose of feeding data into conditions. For example, when a user is tracking the cooldown of a spell as their core trigger while tracking the spell overlay glow or a buff (or both) to determine when to show a glow.
The current solution of setting up a custom activation function just to do a basic
return trigger[1]
seems unfriendly to those unfamiliar with custom code, and may limit those users' ability to design what they want.My ideal would be to add an entry to the "Required for Activation" drop-down for all existing triggers, allowing the user to select "Trigger 1" etc.
I do understand that this may lead to additional feature requests down the line asking for GUI options for more complicated trigger combinations but I think selecting a single trigger is a good middle-ground.
Thanks for reading.