Get it? It’s a demonology warlock raid parse comparison but also an example warlock comparison using Warcraft Logs? It’s a demo warlock raid parse comparison!
Puns aside, I see Warcraft Logs introductions, and they usually show how to upload a log and then “hey, it makes pretty graphs and is a pretty powerful tool,” and then never goes any further. Perhaps it shows off the tools — look, you can make pins! and here are all the things you can do with pins! — but the guides I’ve seen that aren’t actual walkthroughs of a raid parse specifically meant to improve a specific person often just stop with the abilities of Warcraft Logs rather than what you should do with them.
Handing someone a full toolbox doesn’t automatically make them a skilled carpenter. The information sitting in the powerful & useful tool that is Warcraft Logs is still overwhelming to the casual raid parse reader, because they don’t know what to do with all of it.
However, I haven’t quite figured out how to generally write or make a guide that explains why to use a pin or a graph or a table or the replay to judge J Random General DPS Concept. Why? — It’s very specific per spec and per fight, even per attempt depending on what you’re doing, and even per question depending on what you want from it all. Trying to anticipate all the questions is just overwhelming by itself and hardly solves any of the overwhelming feeling.
The only part I’ve been able to figure out is that reading a parse is not so much about bringing a checklist of frequent problems to see if any apply to you. Reading a raid parse efficiently is more about bringing your knowledge about your spec, your class, and the specific encounter to the raid parse and critically applying that knowledge to the various results you have in the graph/table/chart/replay.
You have to already have questions or possible reasons why you didn’t do so great when you come to the parse, and the parse will help you answer those. The parse doesn’t magically conjure answers for you — you have to already be looking for them.
To start figuring out how to write a guide for reading a raid parse in order to better yourself, I recorded my own, where I compare myself as a demonology warlock to another demonology warlock who did better DPS on this one fight than I did.
First off — I’m sorry, I didn’t realize the resolution was that terrible until it was already uploaded & processed on Youtube. Which took multiple hours (because, well, it’s an hour-long video itself). And I didn’t feel like redoing it. Sorry. It’s probably actually because I recorded it at some low setting. It’s clearest to read in the smallest player, but I think it’s fine, since it’s mostly the graph shapes/animations that I’m focusing on, not the text.
My video is actually uncut as well as unscripted. I figure this is better so you can see me meander through all the different tabs, discovering new information and arriving at new conclusions organically rather than me telling you what to look for. I use myself as the worse warlock, so I’m only embarrassing myself in particular, not anyone else. And it’s also part of my after-raid homework to log-dive my own logs like this.
I was very, very tired when I recorded it — insomnia is never fun, and you’ll hear me yawn a couple times — so I actually make quite a few obvious knowledge mistakes. I usually catch myself, but there are others that are there that I now facepalm myself at. Sorry! When I’m writing articles, I am actually awake and actually remember things like Grimoire of Service is 2-minutes not 1-minute, and realize that the guy has higher DPS overall instead of just having a higher opener. The intent of the video is less to show off how bad I am at demonology and more that, hey, look, I’m imperfect at this spec and even I can get some ways I can improve out of a raid parse. (It’s also easier to show the differences between a not-great warlock and a good warlock than it is between a good warlock .and a slightly-worse warlock!)
This is not meant as a be-all end-all to Warcraft Logs guides. It doesn’t even cover everything there is to use — I don’t look at how tanks or healers could use the parse information, because, well, I’m not playing one right now. I’ve done a tank or healer parse comparison as part of being a veteran raider rank in my guild, in order to pinpoint why or how a guildmate needs to improve, but I don’t normally play a tank or healer, so I won’t pretend to know 100% how to read those parses. I can certainly open up a 101 guide to a guildmate’s class & spec & figure out the really obvious ways they are screwing up, but let me be clear, the only class I can possibly be an expert in is warlock, and even that I’m, well I’m good, but I’m not perfect.
This is meant as something to help get you started at reading a Warcraft Logs parse, especially if you play a warlock (or maybe even a DPS in general). So hopefully it helps you logdive on to figure out why you may or may not be doing things incorrectly and how you could do better.