Logging not working as intended

WoW Classic WoW Classic General Discussion
1

On November 19 blizzard decided to reduce the range that game logging works in the world for classic wow, but in the announcement it specifically said that
“This fix does not affect text logs that the game outputs for raid parses.”

However when we are doing BWL and we are logging our raids and upload them to warcraftlogs, this statement seems not to be true.
Lets take an example:
Last time we did nefarian we decided that mages should run away quite far and hide to not polymorph our tank. Getting out of range of our tanks also means that since I am a mage and I am the one logging the raids, I get out of range from seeing what the tank does in the game. As stated above, this should not matter with regards to the logs, but if that is the case, how do you explain this:

classic (dot) warcraftlogs (dot) com/reports/k4wm9hrpA37GaVc1#fight=33&type=damage-taken

At 3 min in to the fight mages run away and suddenly the dmg taken on the tank drops to 0 until mages are back in range.

This needs to be fixed (or explained how to get around) because its quite annoying to not be able do specific tactics in raids if you still want to analyze the raids afterwards.

Thanks in advance!

3 Likes
2

Bumping, a valid concern.
Increase combat log range within instances pls just like the drawdistance in bgs are further than 50 yards.

3

Good find.

The damage continues though, as shown in the link below.
https://classic.warcraftlogs.com/reports/k4wm9hrpA37GaVc1#fight=33&type=damage-done&source=17

4

They simply don’t care about us trying to log things. There’s absolutely 0 reason for the combat log range nerf to be active inside PvE instances like 5mans and raids anyway.
But they just don’t care.

5 
classic.warcraftlogs.com/reports/k4wm9hrpA37GaVc1#fight=33&type=damage-taken
6

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.