Thanks for your help, my issue seems to be fixed, took me 8 hours of testing, guessing and goggleing (is that an english word?) :/
The thing is, I don't know what exactly caused it.
I've been using my own UI since 2008 and there is a lot of code from back then. I only changed/updated everything that appeared in the taint log that looked like it could lead to errors (like directly replacing blizzard functions with my own, not checking for InCombatLockdown() and stuff like that) and also changed some variables that were accidentially declared as globals.
Originally Posted by Torhal
If the blocked action is easily reproducible, that's definitely a way to go.
|
The problem is, that the error didn't always occur. It had something do to with getting in combat/out of combat and joining/leaving groups. Sometimes it happened after being AFK for a minute and getting in combat after that time.
Originally Posted by Seerah
/console taintLog 11
(Note: this is only available on test servers, and will FLOOD your log.) |
Haha
Well, I'm happy it's gone and I hope it stays like that. The good thing is I switched to using Git 2 years ago, so whenever it occurs again, it should be easy to track down #beingoptimistic.
PS: Sorry for my crappy english.
