brittyazel/DevTool

[BUG] Added events can not be monitored

Closed this issue · 9 comments

Issue description:

Going to Events tab and adding any Event and starting monitoring, will result in no monitoring despite a message being printed that says "Start event monitoring: EventName"

Technical info:

  • Addon Version:* 1.0.4
  • Client: Retail
  • Client Patch Version: 10.1.7

Hrm mine are working just fine. Can I get an example of an event that you are having this issue with? And is it all events? Please test with a very verbose event such as COMBAT_LOG_EVENT_UNFILTERED

Any i add don't work, the ones that were already in the list form the start do work. Reloading after adding a event doesn't help, so when i add something like UPDATE_UI_WIDGET etc there is just nothing going on at all.

COMBAT_LOG_EVENT_UNFILTERED will work and it was already there by default for me.

Hmm interesting, some events do actually work? weird, only PLAYER_STARTED_MOVING that appears to work from the events i added here.
image
image

Hrm, interesting. I'll look into replicating these the next time I'm on. Perhaps Blizz changed/broke something without announcing it, and/or they're throttling addon access to view events. This is very peculiar though, so thank you for reporting it.

hey, still no luck fixing? having the same behaviour on hc servers atm 😦

Haven't had any free time to dig into it unfortunately. Once I get a moment I can jump in and see what Blizzard changed, no eta though. For now you can use the in-game event tool, which should be a good alternative until I can patch Dev Tool.

https://github.com/brittyazel/DevTool/blob/main/Modules/Events.lua#L157

elseif thisEvent.event == event and (not unit or not thisEvent.unit) then

something like this, maybe not all the cases will work, but it does for me :P

Nice, perfect. I'll test that and release a new version if it seems stable

Ok, please test this latest fix. If it works for y'all I'll push a new release. The issue was a dumb assumption I made about the payload values from events, and I believe this should correct it.