Here’s something a little different: Usually, before I write a World of Warcraft column (or any column), my assumptions and data are pretty firm before I put them down on paper, else I wouldn’t be writing it in the first place. This is one of the reasons that, for example, I spent so much time showing my work when trying to predict the launch date for Battle for Azeroth; that was all about hard numbers, so it was easy to check math and assumptions in an obvious fashion.
But in this particular case I’m exploring a concept that I’m still playing with and researching, something that may turn out to be somewhat erroneous. To wit: I suspect World of Warcraft expansions have switched from selling to existing customers and into reclaiming old customers as a primary design focus.
It might seem like an odd assertion, but I think it’s an interesting thing to consider and may help shed light on a number of design decisions, several of which I think are pretty bad ones. But for this particular column I’m not interested in analyzing the merits of design choices; I’m interested in presenting the evidence and showing how it lines up in a more neutral fashion. Because I think it can shape some interesting thinking.
There’s a lot to be upset about with the World of Warcraft Battle for Azeroth prepatch. There’s stuff that just doesn’t feel good any more (and yes, go ahead and make your own jokes there about the implications of that statement, it’s justified). There are bugs and issues that weren’t adequately tested. There’s the fact that this expansion is really doing a grand job of screwing up lots of characterization.
But with the pre-expansion event, we can look at a whole list of incredibly dumb things done just in this bit of the story.
We only have the first half of the event live right now, of course, and there are lots of dumb choices surrounding this (the fact that the story is in this order, for example), but for today we’re going to be confining this solely to in-universe criticism. And there’s still a column’s worth of intensely dumb decisions being made by someone who is supposed to be a capable military commander, based on all of the military commanding she did for ages.
It took me a long time to identify what felt off about World of Warcraft’s upcoming expansion. Something was definitely bothering me, but the thing was is that we know exactly what an expansion with the bare minimum effort looks like now, and it sure as heck didn’t feel like Battle for Azeroth was Warlords of Draenor But Again. Yet something kept nudging at me, some comparison that was just slightly eluding me as I dutifully tested new quests, new system revisions, and so forth.
Then I realized that the whole thing was basically Cataclysm and it clicked.
Mind you, I say this not as an indication that the expansion is nearly as bad as Cataclysm was. (There’s still far too much of the actual game to see, for example.) But far from my own optimistic excitement, it feels like the expansion is making a lot of the same missteps as that particular black mark, and it doesn’t exactly fill me with confidence.
If you have a dormant World of Warcraft account, best give it a check: Redditors are reporting that their accounts are currently activated without subbing.
While some gamers are expecting it’s a bug that’ll soon be fixed, it’s also possible that Blizzard’s simply reactivating old accounts in conjunction with summer sale hoopla and summer vacation, all in prep for the expansion launch later this season. Given that WoWhead noticed old accounts have apparently been bequeathed Warlords of Draenor too, that might be a more likely scenario.
Chime in if you’ve found your account alive for no reason – mine has been off a few years and isn’t blessed today, apparently.
The Battle for Azeroth beta is here, at long last, and it feels like it might have come a little early in the process. Usually beta testing is mostly for when you have all of the core stuff in place, but this feels like it’s just officially being called a beta when some of the pieces are still being moved into the right direction. That might be more nitpicky than anything, so I’m not going to spend too much time on it; World of Warcraft has had a tricky relationship with “alpha” and “beta” terminology, but it’s still not even in the list of the worst offenders.
I got my beta invite (at the same time the official changeover happened, even), but I haven’t yet gotten a chance to actually play around in it. However, I think now is as good a time as any to talk about the things that I am actually nervous about when it comes to Battle for Azeroth. Yes, I’ve been a pretty big advocate for the expansion and what we’re hearing so far, but there are things about the expansion that still make me nervous now that we’re moving into the beta phase. So let’s talk about that.
If Allied Races show us anything, it’s that World of Warcraft is really in no danger of running out of new races to throw at us. This particular system is adding nearly twice as many new races in one expansion as we’ve had added during the entirety of the game’s lifespan thus far, there’s another one that looks to be set up for this as well (hello there, Vulpera), and there’s a deep roster of other options that people have asked to have for ages. Yes, it would take some work to retrofit Vrykul and Ogres, but considering the work going into new male orc poses, Zandalari Trolls, and Kul Tiran Humans, it is definitely not insurmountable work.
Of course, as I alluded to a while back, we sort of have a disconnect right now where we’ve got far more race options than class options. And while we’re awash in races, we seem to be in danger of running out of classes that can’t be pretty cleanly modeled by what’s already in the game. That doesn’t mean we can’t get any new classes, of course, but it’s hard to justify the inclusion of a Pirate class when we already have a Rogue spec doing everything such a class would theoretically offer. The inclusion of mechanical Hunter pets alone basically short-circuited talk about “Engineer” as a class.
Not that this means we’re out of options, of course; in fact, there’s still plenty of things left in the bank of known or reasoned class options that we can’t play just yet. So let’s talk about some of those options, and along the way I’m sure we can fit in some fun discussions about the difference between classes and hero classes.
Hooray, we have a release date for World of Warcraft: Battle for Azeroth instead of just a release window! And contrary to what many skeptics (myself included) expected to get, it is actually quite a bit faster than other releases. But as you all have no doubt noticed by now, my love of math means that I’m hardly sore about this. It just means that there’s another data point to consider when we look to the future.
So let’s talk about this new piece of information while using the same information from the column in which I made a reasonable estimate, based on this new information. Again, I think it’s important to note how much faster this expansion is actually releasing compared to prior expansions; it’s significant, even if it means that the people predicting things like June were being wildly wrong about “optimistic” predictions. (After all, pessimistic predictions were equally wrong, just in the other direction; my own estimates were off by 2-3 months.)
Last week, we got confirmation that Kul Tiran Humans and Mag’har Orcs are coming to the Allied Race roster for World of Warcraft: Battle for Azeroth. We don’t know when, but I have a bit of a theory about that as it is; from what we know, it’d make sense to have Dark Iron Dwarves and Mag’har Orcs brought in at the start of the expansion, while the Kul Tiran Humans and Zandalari Trolls are brought in after you’ve finished the leveling story for the respective factions. The former are more solidly members than the latter, after a fashion.
But we don’t know for certain when they’re getting added, just that they will be. And that’s interesting, because it means that both factions have significantly increased their race options within one expansion. And that becomes kind of relevant when you look at how many choices individual players have in terms of having something for all of these different races to do.
One of the important things to note about World of Warcraft lore is that it’s never been static. It will retcon itself six ways from Sunday letting you know that the stuff you thought was true was never actually true, and it’s something the franchise has been doing since the second installment of the series was launched. (Remember when Azeroth was the name of the human nation, not the freaking planet?) This is not a game where the lore has been carefully planned out so that you can make reasonable predictions much of the time, this is where the lore repeatedly changes as new installments come out.
This is fine. I really like games where all of the lore is written out and planned well in advance (obviously) but I also have appreciation for the way that WoW’s backstory does change with the tides. It rarely outright invalidates the past, but the past is not static as we learn more about it.
Enter the speculation about Druids in Kul Tiras, speculation that seems to be getting backed up with increasing amounts of evidence. And as I look at all of this, I can’t help but note that even a moment’s consideration reveals that this is an enormous mess for the game’s overall lore.
Last week, we looked at the composition of the Alliance in World of Warcraft. This week, we’re looking at the Horde. Makes sense, doesn’t it? If you missed the prior column, catch up and get back to us here.
One of the things that’s always been true about the Horde in World of Warcraft is that it is, by and large, a more heterogeneous collective of races and nations. This is partly by design, and partly because the Horde just seems to have a different way of handling its membership and its populace. If the Alliance needs a group of skilled trackers in a new landscape, it’ll find its best scouts and train them; the Horde, meanwhile, will just befriend a local group of existing trackers and welcome them into the Horde.
Does that sound a bit off the mark? Well, let’s take a look.
Watching as speculation and mining swirls around the Mag’har as a future allied race, I can’t help but start thinking about the bigger picture in World of Warcraft. Because soon we’ll be able to make another couple of allied races, and we’ll have more on top of that, and it brings up a pretty good question: what, exactly is the Alliance at this point?
You might think that’s a silly question, but both the Alliance and the Horde are kind of nebulous political groupings, and their extant members are a pretty big deal when you’re speculating about who’s going to be next to sign on board. Plus, I think it helps a bit to consider what could be coming in the future, both for future customization options and further development.
So, then, let’s start with the Alliance, because it’s first alphabetically and a bit simpler to put together. What actually comprises the Alliance?
In our third part of this five-part countdown of World of Warcraft’s best music (at least, you know, in my opinion), we’ll be heading into the teens and some of the most iconic music of the MMORPG to date.
I think we’re getting a bit of everything in today’s list, from vintage Vanilla WoW to the Legion era, from silly to serious. One of the more difficult aspects of putting together this countdown is considering the “old” and “new” versions of songs, especially when Blizzard has remade or revisited areas, characters, and themes. I find that some people are heavily biased depending on which era they played the most, and thus that music means more to them than the others.
I’d like to hold myself up above that bias horizon, but alas, none of us can escape it. So I’ll endeavor instead to be as fair-handed as is gnomingly possible.
It’s funny to me that people had such an aggressive reaction to the changes coming to Hunter pets and damage formulas in Battle for Azeroth. The latter in particular should be both invisible and completely immaterial for actual play; the only real change is that they now use weapon damage on abilities which were previously disconnected from weapon damage, but these formulas have always taken into account, say, the difference between two-handers and dual-wielding options. The former is, at its core, an opportunity to make pet families relevant again after most of the pets of Legion were more or less difference in appearance only, which is a far cry from the days when your choice of pet was significant.
To make it clear if it’s remotely ambiguous: Yes, these are changes I support and ones I think are good for the game on a whole.
And yet all of this does prompt a pretty salient question about World of Warcraft because even if these are intelligent choices, the weapon damage issue has existed for ages now. The time for fussing about with Hunter pets was also ages ago. It’s a big change to functionality being tossed into the mix more or less out of the blue with no other prompting, and that raises the question that’s been relevant ever since Cataclysm rolled around: Why is it that Blizzard can’t stop messing with everything?