#Multi Target Trigger question

53 messages · Page 1 of 1 (latest)

small axle
#

Im trying to make a WA group that tracks how many thirsty patrons that are still active on the first boss in cinderbrew meadery. Since they have no nameplate i tried the multi target option, which works, but after 1 minute the wa stops being triggered even tho the buff is still active on targets. How can i make it stay triggered until all the buffs are gone? 🙂

lucid onyx
#

Multi-target uses combat log events to guess at the status of things.
The trouble is that combat log events alone can often be missing important updates. Like a buff application occurs in your combat log, but you never get the removal. IIRC WA works around this by removing states that haven't updated for a minute.

If combat log events really are good for this use case then you'd need to recreate the trigger in code.

small axle
small axle
lucid onyx
#

There might be a way to enable the nameplates too. Could look in to that.
Otherwise, it's not that complex but depends on your level of experience.

#

!starterkit

trail radishBOT
lucid onyx
#

!cleu

trail radishBOT
#

https://warcraft.wiki.gg/wiki/COMBAT_LOG_EVENT

function(event, timestamp, subEvent, hideCaster, sourceGUID, sourceName, sourceFlags, sourceRaidFlags, destGUID, destName, destFlags, destRaidFlags, ...)

You can use this Aura, https://wago.io/CLEU-IN-ETRACE (works fine in all game versions, not just retail), to add the detailed info into the Etrace tool.
For more info on Events and Etrace see #pins message

full zodiac
#

they do have nameplates, but they're hidden by default

#

they pop up for a ms when they do their throw stuff

#

so yeah, you can probably look into forcing them to always show

small axle
full zodiac
#

no clue what's special about these nameplates there

small axle
full zodiac
#

it fires FORBIDDEN_NAME_PLATE_UNIT_ADDED for them

#

which explains why showing them won't work I guess

#

works just fine

small axle
#

Just trying to understand the code and learn abit, in function u have "(a,e,n,s)", im assuming a = allstates and e = event but what does n and s stand for?

full zodiac
#

!watched

full zodiac
#

Trigger number and triggerstate, since I'm watching 2 combat log Triggers there (spell aura applied and removed of that thing)

small axle
full zodiac
#

Well if you rename the rest appropriately as well then yeah

#

How you call the parameters is up to you

#

Could be poop, doggy, piechart, mikerussel

small axle
#

ah so even if my code would look like this, it's still does the same, but my question then is how does n / doggy for example know that it is a trigger number?

full zodiac
#

well piechart here would be the trigger number

small axle
#

ah yee

#

wrote wrong

#

Im thinking it goes on the position in the function, so function(1,2,3,4) 3 is the trigger number and can be called anything

full zodiac
#

yes

small axle
#

Makes sense

#

oh and one final question, when u do a[" "] and s[" "] what does that mean?

full zodiac
#

!vdt

trail radishBOT
full zodiac
#

a and s are tables

#

in Lua that's a way to refer to an entry in the table

#

in trigger state tables provided by WA (so here: s): if they only have one subtable (a non-cloning trigger), that ones key is always just an empty string ("")

#

so it means nothing specific, that's just how the place where the data I'm looking at is called

#

and I got into the habit of keying my own tables like this as well, hence why the allstate table entry I create is also just an empty string ("")

#

but again, it could also similarly be

if not a["SuperCoolTableEntry"] then
a["SuperCoolTableEntry"] = {
  stacks = 1,
  show = true,
  changed = true,
}
return true
end
small axle
full zodiac
#

!tsu

trail radishBOT
full zodiac
#

This wiki article explains TSUs very well

small axle
#

Are my notes somewhat correct?

full zodiac
#

yes