Originally Posted by Xrystal
Yeah, etrace is a nightmare to unravel. But you can *remove* events you don't want to see - at least I remember doing that when I last played with it an expansion or two back. And it will stop showing them allowing you to narrow it down to events that triggered just after you logged in that you weren't tracking in your addon. Until you see which events were first firing after the PLAYER_LOGIN and PLAYER_ENTERING_WORLD ( which triggers on any reload ) events you won't know which ones to check on.
|
I actually don't mind the unraveling part, and I did notice the ability to filter unwanted events, which is good. What is not good is that early events like PLAYER_LOGIN and PLAYER_ENTERING_WORLD are never showing up in the event log, because it doesn't start tracing events until /etrace is executed. What I'm hoping for is a way to start /etrace and open the trace window via a .lua call of some sort, so it's already open at the earliest possible event. The first few events that fire are listed in wowpedia, so I can trigger opening the /etrace window programmatically on the first event in the login chain. I just need to find the .lua method for opening /etrace.