Thursday, September 18, 2008

Cloning > Transfers

So, evidently, Mythic's approach for dealing with server overpopulation is :

  1. Notice a problem
  2. A short time later, clone the server, which is much better than allowing server transfers because nobody has to deal with character transfers -- or missing the character transfer if they were away for a week or their guild decided to move at the last minute.
Contrast this with Blizzard's approach :

  1. Notice a problem
  2. For about three to six months, deny there is a problem
  3. Allow server transfers. Note that if you happen to be away for a week or your guild decides to move at the last minute you may be screwed. Also note that for a long time WoW did not allow at-will transfers either, so if you missed the window to move -- hey, guess who gets to roll a new character?
I don't remember Mythic even mentioning the server cloning. I have to say I'm quite impressed. Although the CoW destruction guild had already moved from one of the cloned servers because of overpop, I wonder if they'll stick with the new server or go back.

2 comments:

Crofe said...

I hope you guys go back. I was planning on rolling a Destruction Alt on the same server just to play around and be on the same server (Figured I wouldn't actually join the guild because it would be an alt). Sadly their new home is Thorgrim which is the server my Order main is on. :(

archmagery said...

also...Mythic offered us the cloned servers at no additional charge. ALL of our characters in one shot.

Blizzard charged us per-CHARACTER to *transfer*, from which there is no save if where you go sux.