Know Your Lore: Lore summed up part 3 - Wrath of the Lich King
The World of Warcraft is an expansive universe. You're playing the game, you're fighting the bosses, you know the how -- but do you know the why? Each week, Matthew Rossi and Anne Stickney make sure you Know Your Lore by covering the history of the story behind World of Warcraft.
Part one covered the original launch game, and part two covered the Burning Crusade expansion. Part three is about Corgis Unleashed.
No, no, I kid. Part three is of course about Wrath of the Lich King, when our titular king of the liches gets upset. Miffed. Irate. Angry, even. This one is going to be long - even longer than the BC recap, so long that I see no choice but to split it into two parts. The Lich King was a long time in coming - players were clamoring for him from the moment World of Warcraft launched, and when the expansion bearing his name finally hit, it changed everything.
Like The Burning Crusade, WotLK started with an event. But unlike TBC, this particular event, the Scourge Invasion, was leaps and bounds more dramatic than expected. This time, the monsters were the players, so to speak.
It began with mysterious boxes appearing in Booty Bay and other cities and towns, spreading across Azeroth slowly. The boxes appeared in capital cities, shipped from unknown locales... and slowly, all over the world, the curse of undeath began taking root. At first members of the Argent Dawn could keep ahead of the tide of plague, but as it continued, more and more of Azeroth's heroes succumbed. Soon an irresistible tide of undead threatened Orgrimmar, Stormwind, Ironforge, Undercity (yes, even the forsaken were not immune) and other locations. Some ran and hid in the countryside, avoiding major cities, because these undead seemed to possess a sadistic enjoyment and sought to infect as many as possible.
Filed under: Analysis / Opinion, Lore, Know your Lore, Wrath of the Lich King












Alexstrasza does, however, show even more skin than Sylvanas does, so from some peoples' perspectives this might be a feature rather than a bug.





