# M+ log not tracking spec change correctly

**URL:** <https://forums.combatlogforums.com/t/m-log-not-tracking-spec-change-correctly/16284>\
**Category:** Warcraft Logs\
**Created:** [August 31, 2025, 2:23am UTC](https://forums.combatlogforums.com/t/m-log-not-tracking-spec-change-correctly/16284 "2025-08-31T02:23:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Suzushiiro](https://yyz1.discourse-cdn.com/flex029/user_avatar/forums.combatlogforums.com/suzushiiro/32/2475_2.png) [@Suzushiiro](https://forums.combatlogforums.com/u/Suzushiiro)\
**Post date:** [August 31, 2025, 2:23am UTC](https://forums.combatlogforums.com/t/m-log-not-tracking-spec-change-correctly/16284/1 "2025-08-31T02:23:40Z")

</div>

So I ran a +11 Halls of Atonement just now where our tank had to pop out of the instance for a second after the start to change specs due to forgetting to switch out of Mistweaver before the run started. This has resulted in this log: [Summary - Last Pull - Report: Mythic+ Season 3 | Warcraft Logs](https://www.warcraftlogs.com/reports/2dvxK3t7HYqwgkLD?fight=last&type=summary) which says that we ran it with zero tanks but two healers, one of which did the best damage any Mistweaver had ever done for that key level but absolute _dogshit_ hps.

I get that dungeon logs/parses will always get weird with a mid-run spec change, but I think it makes sense that if a character was clearly the same spec for every single combat encounter of a run but not that spec at the very start the system should count them as the spec they fought as, not the one that they started as.

---

<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:** [September 1, 2025, 3:56pm UTC](https://forums.combatlogforums.com/t/m-log-not-tracking-spec-change-correctly/16284/2 "2025-09-01T15:56:07Z")

</div>

We look at the event at the start to determine the spec of a character in the log (There’s an event that pops up when you insert the key in the log file). And that’s what determines the spec, sadly we cannot mutate that manually. But I can blacklist the parse if it is affecting rankings.

Let me know,

Azrael.