Violation + LoggerHead = missing combat log?
Posted 13 September 2007 - 02:25 PM
Apparently Violation now has an option to turn combat logging on and off in various situations. One of them is "Any PvE instance". By the looks of it it will actually turn it off all the time if it's not checked. And this seems to interfere with LoggerHead.
For obvious reasons I don't want/need logs from normal instances or heroics, hence my LoggerHead is configured to only activate logging in "real" raid instances.
So I guess what happened is this: when we entered Karazhan, LoggerHead activated logging, but at the same time Violation turned it off again because "Any PvE instance" wasn't checked. But LoggerHead didn't notice that some other addon has switched it off and was still happily displaying it's green flag.
Now my question is: has anyone else encountered such a problem recently? If yes, have you found a solution for it? Or is there something else fishy?
Posted 13 September 2007 - 04:49 PM
Posted 14 September 2007 - 09:41 AM
I've been turning off Loggerhead and letting the Violation combatlog module handle the log activation up until now. :-/
Posted 14 September 2007 - 10:58 AM
Is there a good reason why I should use Violation instead of Recount?
Posted 18 September 2007 - 06:34 AM
(Blackpatch) the theoretical weekly profit of hypersynaptic fibers in ISK is only 0.004% off of the speed of light in meters per second
(@ZYla) dammit steam
(@ZYla) i already own all these gays
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users