Combat Log Fix

Fixes the combat log break bugs that have existed since 2.4. Credit goes to Imbad on ArenaJunkies for finding this. It works by clearing your combat log essentially, but it does it a little bit more automatically:

Slash commands: /logfix

On zone type change (pvp -> none, raid -> none, etc) it will clear the combat log
If no combat log events are found for 2 seconds after you cast a spell, it'll clear the log. It will also report how many combat log messages you had when it broke, if you can report these numbers in comments that would be great, might help narrow the bug down.

The above are enabled by default, you can disable them with /logfix.

Author: Shadowed <[email protected]>
Date: Wed Feb 17 16:34:43 2010 -0800
- Changed logic, now based off of when the spell with a cost (mana/health/rage/etc) is cast and checks if any combat log messages fired within the last 1 second
- Fixed events not being unregistered
- Reduced timeout to 2 seconds
- Initial commit (/logfix), auto fixes the combat log by clearing it

Originally posted by Pseudopod I've noticed a tendency to have the "combat log broke" report appear when I cast Fel Armor after some time of not having it on. Whether I was afk or active, doesn't seem to matter. Maybe it's related to buffing in general, I don't know. Can the addon have some sort of an issue with that and is unnecessarily clearing the log?

under high latency yes. the mod compares combat log events to UNIT_SPELLCAST events, basically, it time stamps when yu casted it on your local UI frst, then after x amount of time if it hasn't gotten a combat log event for it from server side, it assumes combat log broke and resets log. i believe this delay is like .5 or something, so basically, if your latency is higher then that delay, it's gonna clear log a lot for no reason cause your latency is affecting your cast start to cast result.

I've noticed a tendency to have the "combat log broke" report appear when I cast Fel Armor after some time of not having it on. Whether I was afk or active, doesn't seem to matter. Maybe it's related to buffing in general, I don't know. Can the addon have some sort of an issue with that and is unnecessarily clearing the log?

It reports that it is still clearing stuff but i'm not sure if it actually needs to be clearing anything. It seems to randomly clear stuff like it should but I haven't seen my combat log actually stop working yet.

Originally posted by MysticalOS i don't think he meant to report it to him, but to blizzard. it's been a blizzard bug since BC, and maybe if more people continue reporting it to blizzard they will eventually fix it.

if you can report these numbers in comments that would be great, might help narrow the bug down.

Originally posted by coani One evening when I had been going through 10+ disconnects...

I'm just mostly irritated that game doesn't spit out any form of debug log or anything that can provide us with any sort of hint about what the problems are, or where they occur (is it actual network issue, or is something blowing up in the game).

I get these disconnects too and it's not our connection. There are quite a few threads about this in the tech support forums. One "fix" was to set your multicore processor to use certain cores. Some people swear it works, but unfortunately I didn't notice any difference. But some blues have decided to recommend that fix since it works for some:

Keep in mind the auto fixing will trigger within 1 second of a cast by you, so if you're using a lot of abilities you can have it clear the log before you notice it's broken.

There's not that much I can do at a certain point. I don't play a melee class, if you notice it breaks you can try /script CombatLogClearEntries() to see if it fixes it. If it does I can try and look into it more.

Originally posted by Shadowed I presume the combat log has broken and you've not noticed any messages? I just checked and most Warrior abilities (eg, Heroic Strike) trigger the necessary events, so no reason it wouldn't work.

Check /logfix status to make sure auto clearing and reporting are enabled.

I just had the message trigger for the first time on my hunter alt though I did not notice the combat log was broken. This was using whatever the default settings are on initial install.

For the warrior (and as mentioned earlier, the DK and the rogue), I tried whatever the default is and then tried turning on the "Wait on clear" since that was the only disabled one by default but i've yet to see anything trigger on those 3 characters though I have noticed the combat log breaking.

Support AddOn Development!

You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.