Siege is live, the raid doors are open, and the spreadsheets have unsheathed their weapons. Warcraft Logs has now released its official parsing and speedrun rules for Mists of Pandaria Classic’s Siege of Orgrimmar, which means the second raid has begun: the one where everyone argues about what counts.
Welcome to endgame. Please keep your cooldowns, trash pulls, and emotional damage within approved limits.
The Rules Are Here Before the Parse Drama Gets Worse
According to Wowhead’s coverage, Warcraft Logs has outlined how Siege of Orgrimmar will be handled for parsing, speedruns, and complete raid rankings.
This matters because Siege is not a tiny little boss corridor. It is a 14-boss raid full of adds, transition phases, special damage situations, and enough weird edge cases to turn every ranking into a courtroom hearing if nobody sets rules early.
Warcraft Logs is trying to avoid that by defining what counts, what gets excluded, and what can disqualify a run before players turn “but technically” into a raid strategy.
Trash Dragging Is Not Your Friend
One of the big speedrun warnings is simple: do not drag trash into boss fights.
That kind of trick can invalidate logs for the boss and the full raid speedrun. Which is exactly the sort of sentence that makes speedrun teams suddenly look at their tanks with deep suspicion.
It also makes sense. If trash damage gets mixed into boss encounters, rankings become messy fast. Suddenly the competition is not just about execution, damage, and routing, but about who can weaponize nearby garbage mobs without the logs noticing.
Warcraft Logs has noticed. The garbage goblin strategy is on thin ice.
Some Boss Damage Gets Special Treatment
Several Siege encounters have specific rules around damage that will not count toward certain rankings or All Star Points.
That includes fights where extra adds, spawned enemies, or unusual encounter mechanics could inflate numbers in ways that are not really representative of boss performance. Heroic Dark Shaman, Malkorok, and other encounters have special handling listed in the rules.
This is the eternal parsing problem: players want clean comparisons, but raid bosses keep bringing friends, gimmicks, shields, blobs, adds, and nonsense into the room like they are hosting a terrible dinner party.
Parsing Is Useful, Until It Becomes a Disease
Logs are genuinely valuable. They help guilds review wipes, spot missed cooldowns, compare strategies, and find out who stood in the bad with the confidence of a man signing a lease.
But Siege of Orgrimmar is also where parse culture can get beautifully stupid. Some players will play better because they are chasing numbers. Others will treat mechanics like optional decoration because a purple number told them to.
That is why clear rules matter. Without them, every ranked pull becomes an argument. With them, players can at least argue from the same sacred scroll of nerd law.
Garrosh Dies, The Logs Live Forever
For most players, Siege of Orgrimmar is about clearing the raid, getting loot, finishing progression, and maybe finally watching Garrosh get what he has been aggressively earning for an entire expansion.
For parse chasers, the raid does not truly end when the boss dies. It ends when the log uploads, the ranking appears, and someone in Discord says, “Wait, why was that invalid?”
So yes, learn the fights. Bring the consumes. Respect the mechanics.
But also read the rules, because in MoP Classic’s Siege of Orgrimmar, Warcraft Logs may be the only boss that keeps killing people after raid night is over.
For more Classic raid drama, parsing chaos, and useful Azeroth nonsense, keep an eye on Master of Warcraft.
Post a Comment