The meaning of a Realm in World of Warcraft has become incredibly blurred. It’s no longer a distinct cluster of servers, or even a static circle of characters.Over time, patches and expansions have added cross realm LFG tools, shared cities and a sharded open world. Battle for Azeroth will even change how PvP servers work, giving players the freedom to toggle which version of Azeroth they’d like to adventure in.
If anything, the choice of where you create your character is having less meaning with every update. But is there a way for players to take advantage of this ‘tearing-down’ of old realm restrictions? Depending on how it’s implemented and how it evolves, World of Warcraft’s upcoming Communities feature might be just the thing.
Another Blizzcon has happened, and another World of Warcraft expansion has been announced. Recent expansions have focused on defeating external threats, but Battle for Azeroth aims to reignite the classic conflict between the Alliance and Horde. Only this time, it feels a little more… balanced. I’ll admit, I did cheer slightly when I realised Lordaeron was finally being taken back from the Forsaken.
I’ll cheer even more when the Gnomes take back Gnomeregan, but I digress…
Anyhow, the Anaheim convention also saw plenty of announcements about the expansion. Although, the focus was less on the story, and more about the technical details and content implementation. I could see the impact it had on other players, left deflated without having a big bad menace to rally the flag against. Instead, this feels more as if it’s the start of an intricate tale of personal conflict and malicious intrigue, in a way that’s best left shrouded for now.
Even so, I was satisfied with the WoW expansion information available, and with the Blizzcon Virtual Ticket (which I’ll come back to in a separate post). Some of it gets a thumbs up, while others I’m undecided on or will wait-and-see once beta rolls around. For now, however, here’s my initial take on the main topics we heard about.
Vanilla – it’s a flavour of Warcraft that veterans remember fondly. Class raids to Stratholme, 40-player raids through Molten Core, and camping general chat to find dungeon groups. It was a time before transmogs, flying mounts, or pet battles. And now, in the form of Warcraft Classic, it’s making a return.
The WoW community was very different back then. Players chose a server and stuck to it, earning a reputation amongst their peers that would last for years. I even have my own memories – both good and bad – of what WoW was like back then. For some, overcoming the struggles of Vanilla WoW made a different type of player, and built a different type of community – one which some have clamoured to bring back.
But why has the concept been hard for Blizzard to implement? And what might have changed in order to persuade the studio to rethink? In essence, it’s likely taken a gradual overhaul of how WoW actually works, from a simple server setup, to a flexible landscape where the modern server engine and game content are completely seperate. How would it work? Read on…
On Tuesday 24th October, Destiny 2 finally launched on PC. One of the most anticipated releases of the year, Bungie’s platform debut became gained even more interest following an incredibly successful beta test. By all accounts, the open-world FPS performed brilliantly and looked gorgeous on a wide range of hardware.
Unfortunately, much of that goodwill came crashing down with reports of a rapid and reactionary banwave. According to a statement from Bungie, roughly 400 players had their accounts forcibly revoked after that first day, some after only playing for a few hours. The developer stated that its actions were necessary to remove those “who were using tools that pose a threat to the shared ecosystem of the game.”
I appreciate that Bungie wants to protect the integrity of its game, but there are several problems that I have with the way they carried out this action.
Previously, I was cautiously optimistic about the Destiny 2 beta on PC. Unsurprisingly, after hitting it for a few hours yesterday, I’m much more enthusiastic. I’ve always felt that good first-person shooters are played best with a mouse and keyboard, and Bungie’s latest served to reaffirm that opinion. Even so, I can’t help but think that this was less of a beta, and more of a teaser for the full game.
It wouldn’t be a launch without some kind of mishap, and Destiny 2 managed to throw up a few errors when the horde of players tried to log in. I got caught by the ‘saxophone’ error message myself, but kudos to the teams at Blizzard, Activision and Bungie for crushing it quickly. I’d barely lost 30 minutes to the issue before the announcement came across Twitter that the problem had been resolved.
Ultimately, it ended up being an evening of highs and lows as I chewed through the single-player scenario/mission, and teamed up with friends to stomp through the Strike. At the end of it, we all agreed that the beta was more of an advert for the classic FPS crowd than a lure for MMO players. However, with Destiny 2 securing a spot next to World of Warcraft on the Battle.net Launcher, gamers may be lured to the sci-fi magnum opus purely out of curiosity.