#Issues with aura_env.state.destName
46 messages · Page 1 of 1 (latest)
!linkit @cosmic vector
WeakAuras doesn't show anything by default, it's just the framework that lets you import or create "Auras" to display things. If you're having an issue with an Aura, and/or want opinions on it, then you need to share the specific Aura. The best way to do this is to link it through https://wago.io/.
If you only imported the aura, you may right click the aura in-game and select Copy URL and paste it here. If you have modified the aura or created your own, you may instead select Export to string... and upload the string to https://wago.io/. This does not require an account.
You can now paste the import string directly into Discord (with no other text, only the string) and a bot will import it for you and link the wago.
If you are having errors we need a copy of the entire error's text to be able to help.
See this message for details on getting detailed Lua errors:
https://discordapp.com/channels/172440238717665280/413380679410384896/722189624579194973
hmm, could u explain more? he casted raise ally on me so it obv worked, was on me, im confused
SPELL_CAST_START does not contain information about the spell's destination it's just how blizzard decided to do things. They don't want you to know the target for a spell before it is completed casting.
So the idea of my br information WA is doomed?
You can use SPELL_CAST_SUCESS as it has destination information
but isnt it what im using? it was my plan all along bc i knew aura firing on cast start would be clunky o.o
the mass resses i just want to fire info that it was casted, BRs i want to give info on who and by who
then you might just be trying to do it with spells that dont technically have destination targets ie- ground targeted spells
yeah there is 6 triggers for crs and 6 conditions for them to give a general info it was casted, without destination
and 4 triggers for BRs and 4 conditions to give the info with destination
I recommend looking at those variables in ViragDevTools. Especially the state of that trigger
!vdt
https://github.com/brittyazel/ViragDevTool
Dump tables there with ViragDevTool:AddData(table, "title")
i guess im being stubborn but i cant see why this is not working, some of them worked when i used a simple formula in action tab - %sourceName used %spellName on %destName :/ Also actual formula with sendmessage works when i cast soulstone on my warlock
sometimes blizzard doesn't do things the way you would expect them to be done. Even if there is a clear pattern
yeah and even more limitations are coming next patch
which is good, i tried to do it just for fun
i might make it without the destination then, but hmm, mass ress didnt work even if no destination, lol.
well since im using conditions anyway, i turned it into a simplified version, i will see if it works once i get some friend online
It May be cleaner If you Just do a custom Trigger instead of Like 10triggers / conditions imo aswell
@wary orchid it worked the easier way around, also destination works too
but sendchatmsg with the WA fetch doesnt
:/
I think it might be that aura_env.state doesn't exist in condition context not sure though
well at least i got my WA to work ^^ the only downside is that the spell is not linked, meh
imo you're gonna annoy people with that kinda of aura.
There also already is elvui Windtools which annoys people enough with Messages including resses
dont think so it will be super annoying, im raid leading and its good to keep track of things and i dont like elvui or raid leading tool addons, it would be annoying if it was whispering people haha
but in my pugs people often decline resses and wait for free kills, it at least puts some pressure on them when it points out
also its just for mass ress and battle resses, so in one fight it will show up maybe 2-3 times max
but yeah, i think i can remove mass ress callouts as its useless and leave only combat ress + limit it to combat only ^^
then you can delete all the conditions and use actions -> on show
most of the megapacks on wago io i just find ugly and disturbing, wow community tends to like having 1000 useless icons on the screen