Raid Difficulty Tiers and Why Parses Don't Compare
A 99 on one difficulty and a 70 on another can represent the exact same skill — or wildly different skill. Here is why the tiers are ranked separately.
World of Warcraft raids come in four difficulties — Looking For Raid, Normal, Heroic, and Mythic — and Warcraftlogs ranks each one in a completely separate population. People constantly compare parses across them anyway, which produces nonsense conclusions. Understanding what actually changes between tiers explains why the separation exists and why cross-tier comparisons are meaningless.
It is not just bigger numbers
The lazy mental model is that higher difficulties just have more boss health and harder-hitting abilities. That is the least important difference. The real differences are mechanical: higher difficulties add entirely new abilities, add extra phases or soak/spread requirements, tighten enrage timers, and turn mechanics that were ignorable on Normal into instant death on Mythic. The fight is not the same fight scaled up — it is a meaningfully different encounter with the same name.
Why a high LFR parse means little
On the lowest difficulty, mechanics rarely punish you, so the fight degenerates into a damage race with almost no constraints. That sounds like it should make parsing easy, and it does — which is exactly why a top parse there is not impressive. Everyone is free to stand still and do their full rotation, so the field is packed and the skill ceiling is low. A high parse on the lowest difficulty mostly means you out-geared the content, not that you played exceptionally.
Why a Mythic parse is a different sport
On the hardest difficulty, mechanics dictate everything: forced movement, target swaps, soak rotations, and survival cooldown planning all eat into the damage you can do. Two players with identical rotational skill can have very different parses based purely on which mechanic assignment they were given. A modest parse on the hardest difficulty can represent far more skill than a perfect parse on the easiest, because the player was executing a complex job while still doing damage. This is the core reason raw parse numbers should never be compared across difficulties — and why Warcraftlogs ranks them in separate pools in the first place.
The gearing and timing effect, per tier
Each difficulty also has its own gear curve and its own maturity over a tier. Early Mythic parses are inflated relative to later ones because the field is small and under-geared; late-tier Heroic parses are deflated because everyone is over-gearing it on farm. The bracketed item-level parse, covered in percentile vs. all-star vs. bracket, exists partly to control for this within a difficulty. It does nothing to make cross-difficulty comparisons valid — those remain meaningless no matter how you slice them.
How to actually use difficulty when reading parses
Always check which difficulty a parse came from before forming any opinion about it. A guild recruit linking a string of high parses on the easiest difficulty has told you very little about how they perform under mechanical pressure. A recruit with mid parses on the hardest difficulty has told you a great deal. When you review your own progress, only compare like with like: your Heroic parses against your Heroic parses, over time. The most common parse argument in the game is two people quoting numbers from different difficulties at each other. Now you can be the person who points that out. For the broader picture of what a parse does and does not measure, see What Counts as a Good Parse.