Realm Remixes: Stumbling Blocks

Looks like Round 6 has been announced to go off on Monday, November 4th, but there are a couple of changes:

  • Gul’dan getting hooked to Black Dragonflight/Skullcrusher has been pushed to Round 7.
  • Lightning’s Blade getting linked with Burning Blade/Onyxia and the new Winterhoof/Kilrogg connection have been pushed to Round 8.
  • Daggerspine is getting added to Aegwynn/Gurubashi/Hakkar in Round 6, which was previously unannounced.
  • Dentarg and Whisperwind, neither of which were connected before, are also being hooked up in Round 6.

So Round 6 will now look like this:

  • Haomarush + Detheroc/Dethecus/Blackwing Lair
  • Stonemaul + Bloodscalp/Maiev/Boulderfist/Dunemaul
  • Daggerspine + Aegwynn/Gurubashi/Hakkar
  • Tortheldrin and Frostmane
  • Dentarg and Whisperwind

More analysis on those connections to come, but let’s also sound off the complete lists for Rounds 7 & 8. I think it highly unlikely that these rounds will take place before BlizzCon on the 8th/9th, so there’s certainly a good amount of time for stuff to change.

Round 7:

  • Scilla and Ursin
  • Undermine and Anvilmar
  • Malorne + Firetree/Rivendare/Drak’Tharon
  • Quel’dorei and Sen’jin
  • Echo Isles and Draenor
  • Fizzcrank and Aggramar
  • Gul’dan + Black Dragonflight/Skullcrusher (pushed from Round 6)

Round 8:

  • Lethon + Detheroc/Dethecus/Blackwing Lair/Haomarush
  • Smolderthorn + Chromaggus/Garithos/Anub’arak
  • Gorgonnash + Balnazzar/Warsong
  • Lightning’s Blade + Burning Blade/Onyxia (pushed from Round 6)
  • Cairne and Perenolde
  • Winterhoof and Kilrogg (pushed from Round 6)
BLOW IT UP

BLOW IT UP

Conclusions:

  • The trend of CRs only gaining one realm at a time continues; as I asserted in the previous post, it doesn’t look like Blizzard plans to take CRs and connect them together. Instead, CRs will get incremented with a new realm in successive rounds. Probably less possibility of bugs in the process.
  • Kilrogg/Winterhoof getting pushed back to Round 8 leaves Nesingwary/Vek’nilash as the only PVE CR, but Rounds 7 & 8 both end up adding a lot of PVE realms into the mix. It’s notable that Nesingwary/Vek’nilash isn’t getting a realm added to it in these rounds, despite having an altogether low population compared to other 2-realm CRs; compared to all of the other PVE CRs from these new rounds, it’s at the bottom of the pack in terms of raiding population. However, with the exception of Dentarg/Whisperwind, all of the PVE realms look primed to get more connections down the line.
  • There doesn’t seem to be any significance to the number of realms being connected into single CRs; the Dethecus/Detheroc CR, with five realms, has still only got a small fraction of the populations on the larger CRs. There’s no way to tell what Blizzard thinks is an upper limit on the number of realms that CAN be connected to one another, but with both the Dethecus/Detheroc CR and the Boulderfist CR at five realms each at the end of Round 8, there’s no sign of really stopping.
  • Rank 35 Whisperwind picks up Dentarg, one of the lowest-ranking PVE realms, and consequently takes the prize for largest population in a CR yet. It’s ahead by a mile over the three other largest CRs, and again resets the goalposts in terms of what Blizzard might consider to be a healthy population. Unless the numbers of the two realms are somehow grossly exaggerated, this might presage even more additions coming to the Boulderfist CR, which is lagging in 4th place for raiding population amongst CRs at this point. It’s notable that the 5-6k range for raiders boosts these CRs to within the top 30 realms for raiding population.
  • The seven connections taking place in Round 7, followed by six in Round 8, signals that Blizzard is going full-steam ahead with the connection process. Granted, those numbers might be inflated from what was initially going to be a six-realm push in Round 6, but given that Blizzard backfilled with Daggerspine and Dentarg/Whisperwind, it seems like they’re not letting anything really stop the inexorable progress. It’s still possible that they might be keeping things light while priming up for BlizzCon and we’ll see stuff go fast and furious after Veteran’s Day.
  • As a follow-up note from my write-up last week on faction imbalances, the data for these rounds clearly demonstrates that tendency in action: all of the PVE realms have a notable Alliance bias, while all of the PVP realms have a notable Horde bias.
    • I think it’s significant that realms like Anvilmar, which had a dramatic Alliance advantage, saw the ratio brought down dramatically with the addition of Undermine; again, this appears to be done more to give the disadvantaged faction a larger playerbase to draw from simply so that play can take place, as opposed to attempting to balance the factions on the server.
    • However, for some of the super-high-pop mega-realms that have 99:1 ratios, I don’t see CRs being a solution, but Blizzard might ultimately be okay with certain realms being hugely biased to one side if there are enough players able to participate. If you’re Alliance on Illidan or Mal’Ganis or Horde on Sargeras, you just might be out of luck.

Growing Pains

The last week has seen some more dramatic bugs crop up in the connection process. The issue where all but one realm in a CR group has an issue where character avatars aren’t appearing properly on the forums hasn’t been resolved. After Rivendare’s connection in Round 4, several players reported losing mail attachments after the realm restarts. And worst of all, players on Nesingwary started seeing all manner of wackiness happening with their characters lists after Patch 5.4.1 was applied: active characters had disappeared or were locked, preventing them from being accessed, and long-deleted characters appeared unexpectedly. The issue has at this point been resolved after a bunch of intensive work by the tech teams, but it’s certainly a sobering reminder that this is still a new process and there’s still a lot of risk to all of the existing CRs and the realms being added to them as the operation continues.

I feel like I should stress that problems like this aren’t really possible to anticipate, and that Blizzard only has a handful of testing realms that have virtually nonexistent populations compared to live realms. As such, Blizzard hasn’t got any testbed big enough to really ensure that these problems can’t occur when they push it live. Bugs happen. Unexpected code interactions cause unexpected reactions. I think the management of the Rivendare and Nesingwary events demonstrates that Blizzard is taking the process very seriously and has all hands on deck to make sure players are able to get back into play without too much disruption.

But some disruption is almost certain to take place. We just need to be patient and be confident that at the other end of this process, everyone is going to be on realms with playerbases large enough to participate in any content, and that’s on the whole going to be better for the game.

I expect this coming week might be light on CR news with BlizzCon taking place, but I’m confident we’ll get some commentary from the devs on how they think the procedure is going, and maybe how things are going to play out in the future.

And hell, there’s just going to be a lot to talk about during and after BlizzCon. Stay tuned. ^_^

Advertisements

4 thoughts on “Realm Remixes: Stumbling Blocks

  1. Minor correction, Nesingwary is NOT resolved yet, though they seem to have come up with a solution. Many players are still without access to their characters or guilds, and their tickets have not been answered. It’s largely a slogging process for the people in charge of restoration and data correction, and it’s en route to being fixed, but yeah… not resolved :T

    (Then again this is information you likely already knew but I am the most pedantic of pedants so :x)

    • I actually did not know that Nesingwary was still having issues; I assumed that when Blizzard provided a code for players to include in tickets that that meant there was a fast lane to success, but then I remembered it was predicated on players reporting the problem. After years in helpdesk I should have remembered that users rarely know where or how to report a problem, much less what to do when there’s a known procedure to fix the issue.

      So thanks for letting me know. ^_^

  2. There’s a possibility worth exploring, that somebody else came up with in yesterday’s connection sticky post in the general discussion forum:
    Blizz may be using connected realms as an opportunity to consolidate datacenters. Every realm from the Phoenix dc (datacenter) that has been connected, has been connected to a realm in the LA dc, and the poster said the servers were moved, too. I checked the entire list of connected realms, and it’s true (about the connections, anyway, don’t know about the server moves). Also, every realm from the NY dc that has been connected, has been connected to a realm in the Chicago dc. This is also true for the 2 upcoming batches, too. There are some LA to LA and Chi to Chi connections, but Phoenix and NY connections all go to LA and Chi.
    This may show at some of which realms will be connected in the future; any in the Phoenix and NY dc’s.

    I don’t know how to check for a server move, other than having a character on that realm and log into it and check the IP.

    • That’s a correlation I hadn’t noticed before…

      It does feed into the theory that Blizzard is doing the connected realms process, with all of its complications and delicacy, just to mask the cost-saving measure of eliminating one or more datacenters. It would certainly be less overt than announcing “server merges, deal with it.” But it would have the desired business effect of cutting costs while also being far less impactful on the players.

      However, it’s also possible that they won’t do that before an expansion when the population could spike again.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s