Classic /eventtrace spamming GET_ITEM_INFO_RECEIVED
When I am logged in with my Warlock on classic, I get one GET_ITEM_INFO_RECEIVED in the /eventtrace per every frame!!
All addons are disabled. This seems to be independent of the zone I am in and I could not reproduce this with any other character... Anybody seen something like this? |
The same thing occurs in retail. Something happens, either addon or UI, that causes that event to constantly spam with an item ID payload of 0. What I now realize is that I didn't see that on my classic, so it may be an addon I have on retail but not on classic.
|
That's interesting!
I have never noticed this in retail. Only now in classic. As I said, I disabled all addons and it still occurs. And it is only there for one of my characters. |
I know you said you have no add-ons, but it could be some sort of server side bug triggered by addons that sticks to the character across logins. The important question here is has your Warlock ever had an addon active? My retail main is constantly bombarded with this event, but if a "pure" character gets it, that proves an addon isn't responsible.
|
Hm, now I understand what you mean.
My character has of course already had several different addons running previously. Didn't know that such a server bug that persists over logins is even possible. |
You can try reseting your cvars. Sure there is no reference to the addon calling the event in the trace?
|
Code:
/console cvar_reset I get 3 lines of "You do not have permission to perform that function". But the cvars get reset allright as far as I can tell. The events have no arguments attached to them. |
Something to do with non-castable(?) spells in a castsequence macro on an actionbar, from http://infobot.rikers.org/%23wowuidev/20190401.html.gzThis should be added to https://github.com/Stanzilla/WoWUIBugs/issues
|
That's absolutely fascinating. I believe I have just one castsequence macro I rarely use. Next time I'm in retail, I'll check that out. The weird part is that all my retail macros are in classic. I'll look into that part as well.
|
Quote:
In my case it is this macro here: Code:
/castsequence !Shoot,!Shoot So is this a mistake on my side or how else could one achieve this macro behaviour? |
How is that different than this?
Code:
/cast !Shoot |
Quote:
|
I don't have a wand yet on my Mage and can't recall how it used to work.
Code:
/cast Shoot Code:
/cast !Shoot I have no idea what they think they're accomplishing with the cast sequence. |
Quote:
|
Quote:
Maybe that's why Icy-Vains suggests to use the double !Shoot, because it will always (re-)enable the auto shoot when you spam the button. |
Quote:
|
All times are GMT -6. The time now is 05:37 AM. |
vBulletin © 2024, Jelsoft Enterprises Ltd
© 2004 - 2022 MMOUI