Highmaul Raid Logs

[Eisengrad]

Yes, Anju has that effect on people.

[TheCrankyTank]

Noooo, I don't want to see my power outage-enhanced 0.3k DPS on Tectus!

[Werehamster]

Yes. Although I think I managed to mess this up by not deleting the previous logs, it looks like this report has the last two weeks in it.

12/30/14 ..ish
https://www.warcraftlogs.com/reports/vgHKN8M3LQVAcWYy

[Werehamster]

12/1/15
https://www.warcraftlogs.com/reports/7GyNx6Zcr1gJVtaq/

[Chamomile]

Mmm... Absorb calculation: Fail

[Chamomile]

1/6/2015 - http://www.worldoflogs.com/reports/2g5j00anum8fnle7/

[Werehamster]

Also 1/6/2015
https://www.warcraftlogs.com/reports/t3qCcHFXQDypbar9/

[Eisengrad]

It is interesting to me how the two logging mods/systems can deviate so much. Any idea why that is?

[Chamomile]

No clue. With the detail from Andy's, I'm presuming there's an interface mod that tracks a larger set of data. Mine's the parsed output from the built-in /combatlog output.

[Werehamster]

The larger set of data is actually a built in Blizzard thing, it's something like "save detailed log information" somewhere in the interface settings.

I don't think it has to do with the website, it has to do with the underlying data. The main reason why data differs has to do with placement in the fight... events are only passed between server and client if your character is within a certain distance of the event. Since we can be spread out, we see a different subset of events. This is also the reason why people in pugs will often try to say "but I'm #1 on my recount" because you always see all the damage you do, but aren't guaranteed to see 100% of other people's.

This is why Recount tries to sync (and people get that "Character-Uldum is not found" error) to try and get the most complete set of data it can for the most "true" report.