You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there are multiple spells with the same effect. different id's are used for different difficulties, the spells id can be different from the buffs id.
its extremely unlikely that the exact spellid doesnt work for only that spell.
there is also no reason to use the exact spell id function here. you can enter any spellid in the name field instead, then it isnt important if its the correct one.
Is there an existing issue for this?
Description
I have a simple text weakaura that shows when Queen Ansurek (Nerubar Palace raid) goes immune at the end of the intermission.
It has one trigger Aura | Target | Buff | Exact Spell ID = 448505
I expect it to activate when my current target (the boss) gets this buff but it doesn't.
If I use the Spell Name field instead it activates, so the rest of the weakaura (load conditions, etc.) seems ok.
The spell id is correct according to my local log file and any warcraftlogs log.
1/9/2025 17:37:56.8580 SPELL_AURA_APPLIED,Creature-0-3767-2657-12560-223318-0000000971,"Devoted Worshipper",0xa48,0x0,Creature-0-3767-2657-12560-218370-00000008B2,"Queen Ansurek",0x10a48,0x0,448505,"Worshipper's Protection",0x20,BUFF
1/9/2025 17:37:57.1030 SPELL_AURA_APPLIED,Creature-0-3767-2657-12560-223318-0000000972,"Devoted Worshipper",0xa48,0x0,Creature-0-3767-2657-12560-218370-00000008B2,"Queen Ansurek",0x10a48,0x0,448505,"Worshipper's Protection",0x20,BUFF
https://www.warcraftlogs.com/reports/k3Nyq7tnGbLmrDWR?fight=60&hostility=1&source=25&type=auras&ability=448505&view=events
WeakAuras Version
WeakAuras 5.18.1
World of Warcraft Flavor
Retail (Default)
World of Warcraft Region
EU
Tested with only WeakAuras
I got this issue with only WeakAuras enabled
Lua Error
Reproduction Steps
Last Good Version
No response
Screenshots
No response
Export String
Bisector Report
No response
The text was updated successfully, but these errors were encountered: