Tagged With battle for azeroth


Next week’s World of Warcraft 8.1.5 update gives both the Alliance and Horde factions centralised portal hubs, which is good. At the same time, Blizzard is removing a bunch of existing portals, making it harder to get around the game. It’s an odd change that has players asking Blizzard why, and they aren’t satisfied with the answer.


The first major content update for World of Warcraft’s Battle for Azeroth expansion is upon us. Tides of Vengeance bring the fight between the Alliance and Horde to Darkshore, advances the war campaign, adds heritage armour for blood elves and dwarves and turns Gnomeregan into a pet battle dungeon, because gnomes get no respect.


Having spent the past decade reviewing World of Warcraft expansions, I’ve gotten into a certain rhythm. The expansion launches, I play for a month or so, post a review, and then I move on.

Yet I’ve logged into WoW every day since my review of the Battle for Azeroth went live. What can I say? The game tells a great story, and it’s super easy to play when you’re paralysed from the chest down.


Introduced in last week’s update, Warfronts are a new feature in World of Warcraft’s Battle for Azeroth expansion. They’re large-scale battles reminiscent of the original Warcraft series’ real-time strategy battles. They’re only exciting for about an hour, but look at my new horse and armour. So good.


Further demonstrating Blizzard’s obvious Horde bias, within an hour of beginning questing in Battle for Azeroth’s new Horde-centric Nazmir region I’ve ridden in a wagon pulled by the fluffiest alpaca ever, while an adorable little fox creature sang a song about them. I just can’t even.


After a week and a half of leisurely quest grinding, my diminutive Warlock has reached World of Warcraft’s new level cap of 120. Now it’s time to explore dungeons, hunt for treasure, and power up my equipment. Or I could just wait for the next expansion to come along and render all that extra effort moot.


On the far western side of Tiragarde Sound in World of Warcraft Battle for Azeroth’s island nation of Kul Tiras, surrounded by tiresome rolling green hills, lies a gold and amber treasure trove of discarded tech garbage. It’s a beautiful place, as long as you don’t mind the vicious robot dogs.


There’s only so much punishment a gnome Warlock can take, and I can’t take no more. World of Warcraft’s Battle for Azeroth expansion is live, and the Horde is going to pay for their grievous trespasses. Once I finish finding a little girl some seashells, hunt for some treasure, and some other stuff. But after that—WAR.


There's a lot of war flying around this week: Azeroth gets set alight with the newest World of Warcraft expansion, Phantom Doctrine brings a touch of XCOM to the Cold War, Keep Talking and Nobody Explodes hits the Switch, and the Bard's Tale franchise gets its newest title in seemingly forever.


Last week a fire rocked World of Warcraft. It was an epic act of petulance, strategically foolish. It seemed bizarrely out of character for a beloved anti-hero, and damaged the honour of half the game's player population.

In the heat of the moment, it's been hard for many players and fans to accept. The game has thrived on nuanced reasoning that keeps the Horde and Alliance opposed while both feel justified in their animosity. But this was pure aggression and murder. How do you maintain your faction pride in the face of an evil act?