Abilitys not aggregated

For every log i upload abilitys in “damage done” section is not aggregated. Example - https://www.warcraftlogs.com/reports/gCQa7GtfpFndzVLH#fight=25&type=damage-done&source=2&translate=true
so i have several line for Annihilation, Chaos Strike etc…
when same fight uploaded by another person abilitys aggregated as intended - https://www.warcraftlogs.com/reports/8KvdtRTr42wy6hzj#fight=20&type=damage-done&source=28&translate=true

how can i fix this so my logs also upload with aggregated abilitys?

several friends have same problem. several don’t have… would be happy to know on what it depens…

It’s a bug of some kind, but I’m not sure what is causing it. I don’t aggregate abilities for pre-Legion logs, so it’s possible (but would be very odd) that the uploader thinks the log is pre-Legion. I will probably need an original log file to investigate, since the uploader makes the version determination from parsing the original file.

for example i take random few days old log and upload it - https://www.warcraftlogs.com/reports/HTkXVCvrNLYxQaRg/
original log file - https://www.dropbox.com/s/gh2xnafeyplhx53/WoWCombatLog-archive-2018-01-07T19-33-07.328Z.rar?dl=0

out of ideas… i try windows 10,7,xp. try new wcl account - nothing helps.

I’m sure it’s a bug on my end. Will investigate when I get a chance.

another observation - may be it helps to detect problem. in this log https://www.warcraftlogs.com/reports/JWxNBg3zKT7drthw#fight=2&type=damage-done&translate=true
for monks abilitys aggregated, for all others - not.

still no progress with this bug…

It’s a very confusing bug. I did manage to verify that the uploader mistakenly believes your log files predate Legion. Something about the format is preventing it from thinking it’s a modern log.

Can you make that BFA log available (raw)?


todays log (v5.13 uploader) - still same bug https://www.warcraftlogs.com/reports/Tqf7kvaRzQypmBJK/#fight=13&type=damage-done&source=6&translate=true

raw log - https://puu.sh/AWNkw/7bcdaaec72.rar

Oh I know what this is and can fix, since I patched it last time.