Closed deftanksfault closed 1 year ago
Is that bugsack? Because it reports the completely wrong line number for the bug. Bugsack caches similar bugs up and messes up the line numbers. It makes the bug very hard to track. For a developer like me, bugsack is actually inferior to the default wow error window.
I don't know bugsack, but I may have sent you the error I got with AzeriteUI 4, my bad. That would explain the wrong line number. I had the same error with AzeriteUI 5 though, do you want me to try to reproduce the error the next time I play and post a screenshot here? So you can get the correct line number.
Seems fixed with latest version (5.0.22-Beta)
Is this issue for AzeriteUI for Dragonflight?
Is there an existing issue for this?
Describe the bug
I had the following error when I clicked on the unit frame of any boss from legacy raids (here The Nighthold). Reloading the UI didn't fix the issue.
To reproduce
Enter The Nighthold raid and go to the first boss, then click on its unit frame.
Expected behavior
No response
Screenshots
Additional context
/