# Logs not parsing correctly?

**URL:** <https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917>\
**Category:** Warcraft Logs\
**Created:** [November 13, 2024, 11:59pm UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917 "2024-11-13T23:59:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Glibgork](https://avatars.discourse-cdn.com/v4/letter/g/fbc32d/32.png) [@Glibgork](https://forums.combatlogforums.com/u/Glibgork)\
**Post date:** [November 13, 2024, 11:59pm UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917/1 "2024-11-13T23:59:17Z")

</div>

For some reason, whenever I run a dungeon, the logs will mark everything as trash mobs, except for the last pull. I’ve ensured that “Advanced Combat Logging” is enabled, and ran through everything to ensure its configured correctly.  
I’ve tried manually starting the logs myself, as well as ensuring that “Auto Combat Logger” starts logging as soon as I enter the dungeon.  
Here are a couple of my previous logs that I have run that marks everything as trash. Any help on how to resolve this would be greatly appreciated.

[https://www.warcraftlogs.com/reports/rG46qRtAvCH7LYQz](https://www.warcraftlogs.com/reports/rG46qRtAvCH7LYQz)  
[https://www.warcraftlogs.com/reports/9kfh3JxHnPjXc7CL](https://www.warcraftlogs.com/reports/9kfh3JxHnPjXc7CL)

---

<div class="post-metadata">

**Author:** ![Azrael](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@Azrael](https://forums.combatlogforums.com/u/Azrael)\
**Post date:** [November 14, 2024, 10:59am UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917/2 "2024-11-14T10:59:41Z")

</div>

Hello,

Some AddOn is interfering with the logging process, that’s the problem here.

Look at these tweets by one of our engineers, it should cover how to fix the issue you’re encountering:

[https://vxtwitter.com/gerrit\_alex/status/1613931501405585409](https://vxtwitter.com/gerrit_alex/status/1613931501405585409)

[https://vxtwitter.com/gerrit\_alex/status/1613931995750436871?t=jqa-0rVQU7hMXCWtIfky1Q&s=19](https://vxtwitter.com/gerrit_alex/status/1613931995750436871?t=jqa-0rVQU7hMXCWtIfky1Q&s=19)

Hope this helps!

---

<div class="post-metadata">

**Author:** ![Glibgork](https://avatars.discourse-cdn.com/v4/letter/g/fbc32d/32.png) [@Glibgork](https://forums.combatlogforums.com/u/Glibgork)\
**Post date:** [November 14, 2024, 3:09pm UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917/3 "2024-11-14T15:09:19Z")

</div>

Thanks for the reply! I will try using RaiderIO to see if that might be able to overwrite the interference, otherwise, I will have to try disabling add-ons one by one, since I am uncertain what could be causing it.  
The only thing that I could think of would be one of Deadly Boss Mods’ extensions from the base. Do you know if Warcraft Logs generate logs of their own when starting and finishing a logging session? I suspect that I might be able to find additional information there, if so.

---

<div class="post-metadata">

**Author:** ![Glibgork](https://avatars.discourse-cdn.com/v4/letter/g/fbc32d/32.png) [@Glibgork](https://forums.combatlogforums.com/u/Glibgork)\
**Post date:** [November 14, 2024, 3:50pm UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917/4 "2024-11-14T15:50:26Z")

</div>

Looks like I had to completely remove Auto Combat Logger and replace it with RaiderIO. The new log is looking much better. Thank you for the assistance!

[https://www.warcraftlogs.com/reports/NfvDaFrBypR17Ktg](https://www.warcraftlogs.com/reports/NfvDaFrBypR17Ktg)

---

<div class="post-metadata">

**Author:** ![Azrael](https://avatars.discourse-cdn.com/v4/letter/a/f6c823/32.png) [@Azrael](https://forums.combatlogforums.com/u/Azrael)\
**Post date:** [November 15, 2024, 4:29pm UTC](https://forums.combatlogforums.com/t/logs-not-parsing-correctly/15917/5 "2024-11-15T16:29:15Z")

</div>

Yay. glad to hear! Let me know if you need anything else please.

Have a great weekend!

Azrael.