#How to make 2 triggers work at the same time?

5 messages · Page 1 of 1 (latest)

fossil ravine
#

I have an indication in the form of a debuff over the enemy nameplate, the aura is responsible for the debuff itself, and the second trigger is responsible for the aura being displayed only over players, but they don't want to work both at the same time. Only the one that is higher always works. Please tell me how can I make them work at the same time so that my debuff is displayed only on the nameplates of only players?

fossil arrow
#

You can filter by hostility in the buff trigger so in this case you don't need 2 triggers.

If you ever did need to do this kind of thing, the issue is that Activation doesn't see across triggers in the way you want. Activation for each trigger is only on or off. Conditions, though, do see each matching cloneID and work across triggers. So you could use Conditions to hide (alpha = 0) the ones that don't meet the other criteria.

fossil ravine
# fossil arrow You can filter by hostility in the buff trigger so in this case you don't need 2...

There is hostility, it just didn't fit on the screenshot. The point is that now auras are displayed on all hostile nameplates (including totems, pets, etc.), and I only need them to be displayed exclusively for players and that's it. I need to somehow remove the display of the debuff over totems and pets, but I don't understand how, because the second trigger with the checkbox Character Type: Player Character set does not react at all. I didn't find the function I needed in the conditions, maybe someone will tell me how to do it, I can't call myself an expert in this area, I'm an ordinary user, I wouldn't mind step-by-step instructions. The thing is that I made it so that these debuffs, or rather icons of their absence, are always displayed, but for pets and totems they are unnecessary

fossil arrow
#

You would tick the Combine Matches checkbox in the buff trigger, then you can make a Condition for [if trigger2 active = false then alpha = 0]

#

This is a workaround which we generally try to avoid advising people to use, but the alternative is coding a "Watched Trigger" so the shortcut is worth it if it does what you need.