Which was one of the reasons

"Among the advantages the approach that we chose, of using our modern technologies, was just that," Omar describes. "We integrate the exact same security systems and tracking methods, across both Classic and Fight for Azeroth. Systems that wow classic gold for sale are anti-exploit and all our anti-cheat we need them are constant and the same. We would like to be certain we're providing a reasonable environment for all players. Thus, of course we were going to get to leverage that for Classic and that side of this was a big win for us.

"Especially early on because at the time we were developing in 2006, what the team wanted to spend their time was delivering excellent gameplay experiences and not so much on thoroughly archiving each version of their information. That was not quite as high of a priority back then."

In the past decade Blizzard's internal processes have gotten a lot better in regards to retaining data and model control, but in creating World of Warcraft: Classic monitoring some of this stuff down was a lot like Omar's memory of this midnight launch -- trying to find something in a warehouse-sized building filled, and overflowing, together with people.

The hard part? The stuff that the group spent months was ensuring that it looked and played just like World of Warcraft circa 2006. Along the way that you meet from quests, items, to characters, and the story beats fans remember. According to Brian and Omar, this was the easy part. The hard part? The stuff that the team spent months working on was making sure that it looked and played exactly like World of Warcraft circa 2006. Which was one of the reasons Blizzard treated access and all Beta for a opportunity to get feedback that is critical.

Where World of Warcraft: Classic's community will continue to play a significant role in all updates and cheap classic wow gold patches. "We've got an excellent QA staff who found a tonne of germs," Brian supports. "But we also gathered a great deal of comments from our community coverage bugs and inconsistencies. There were situations where they had been like,'Hey, I think that is broken' when it wasn't. And that has been great feedback to be able to document something that individuals will think is busted but is the authentic 2006 behavior.