Through out the game, the quest log will be capped to 20 many times.  The guide makes use of maximizing the total amount of quests you can accept at once.  Because of this it is important to follow the guide exactly and only accept quests if the guide tells you to so you won't run into issues not being able to accept a quest.  If you do accept a quest that is not listed in the guide, write it down because you may need to abandon it in order to keep following the guide if your quest log is full. 

So committed, in fact, that modern WoW players are trying the beta and reporting what seem like bugs today but what were actually intended functionality 13 years ago. This became such a common occurrence that Blizzard publicly posted a list of known non-issues called the "WoW Classic 'Not a Bug' List." For example, hitboxes for the Tauren player race are much larger than those of other races. In a modern game, this would be seen as a serious balance issue (see: Apex Legends). But it's what vanilla WoW was like, so it has been faithfully reproduced.
But how do you proportionally resize the swing? Even if you did, it wouldn’t give you the same type of joy as when you were a kid, because you have grown up and changed. Even if that wasn’t the case for you, you have to consider that the swing has become a place that is sacred for many other adults. When they visit, they aren’t visiting to try out the new adult-swing. They want to try the old swing. The one that brings back the joyful memories of distant past. They know that the experience isn’t the same, but if they close their eyes ... even for a brief moment ... they just might get that nostalgic thrill that brings them back to a time where things seemed so much simpler.

The argument for this is simple: what makes classic WoW great to one player might be different from what makes it great for another. And who are Blizzard's designers to say which old features were just good or bad design for each player? It's an approach that shows Blizzard believes (at least to some degree) that WoW doesn't just belong to its creators but to its fans. That struggle between authorial intent or game design orthodoxy and "the player is always right" is at the heart of many of gaming's big contemporary controversies. But so far, Blizzard seems committed to its plan with regard to WoW Classic.
Most people who have spent years playing massively multiplayer online games will tell you that there's something special about the first one you played, too—and WoW was the first for many people. You can become so swept up in the uniqueness of your first experience that you overlook many flaws. It's likely many look at WoW Classic with rose-colored glasses, just as many simply forgot which features were added when. And some of today's WoW players may be too young to have even played vanilla WoW as it once was.
Even though the guide was developed with a hunter, the guide can be followed by any class.  Except you have to do your class's quests which aren't a whole lot.  I do have full intention to make my guide friendly with all classes in the future by listing all of their steps as well.  There will be a toggle that allows you to show which class's steps you want to see in the guide.  But this is coming later.
Kaivax, a WoW forum community manager, revealed that WoW Classic's class design, battleground mechanics and stats on existing items will be set to their 1.12 state, despite the game releasing content that expands beyond that. This removes "progressive itemization," so if the stats on a specific piece of equipment was changed during the original updates, that won't take effect in this version.
It was the experience of the game that brought pleasure and joy, and that's what a lot of us want again. Not the numbers. When I play Classic I want to go through the deadmines with people I like and overcome a challenge together and see myself become stronger as a result. I don't want to play Classic so I can say "booyah! That number is exactly the same as it was 13 years ago!"
It was the experience of the game that brought pleasure and joy, and that's what a lot of us want again. Not the numbers. When I play Classic I want to go through the deadmines with people I like and overcome a challenge together and see myself become stronger as a result. I don't want to play Classic so I can say "booyah! That number is exactly the same as it was 13 years ago!"
Even though the guide was developed with a hunter, the guide can be followed by any class.  Except you have to do your class's quests which aren't a whole lot.  I do have full intention to make my guide friendly with all classes in the future by listing all of their steps as well.  There will be a toggle that allows you to show which class's steps you want to see in the guide.  But this is coming later.
Most people who have spent years playing massively multiplayer online games will tell you that there's something special about the first one you played, too—and WoW was the first for many people. You can become so swept up in the uniqueness of your first experience that you overlook many flaws. It's likely many look at WoW Classic with rose-colored glasses, just as many simply forgot which features were added when. And some of today's WoW players may be too young to have even played vanilla WoW as it once was.
So committed, in fact, that modern WoW players are trying the beta and reporting what seem like bugs today but what were actually intended functionality 13 years ago. This became such a common occurrence that Blizzard publicly posted a list of known non-issues called the "WoW Classic 'Not a Bug' List." For example, hitboxes for the Tauren player race are much larger than those of other races. In a modern game, this would be seen as a serious balance issue (see: Apex Legends). But it's what vanilla WoW was like, so it has been faithfully reproduced.
Some players have been surprised by these apparent flaws—even players who have been eagerly awaiting WoW Classic's release based on fond memories of vanilla WoW. In truth, it has been so long since WoW first released, players' memories may not always be accurate. Some details might be fresh, but others might be lost in time, and it's those lost details that could surprise players revisiting the original experience in WoW Classic.
The fact that Cookie's Tenderizer from the Deadmines had +3 instead of +2 strength. The fact that the Stormwind south bank had one instead of two mailboxes. The fact that Jaina's Proudmore's name was "Jaina Proudmore" instead of "Jaina Proudless." Stuff like this isn't what mattered. It was arbitrary. If Cookie had dropped a shield instead of a mace and Jaina had been named Susan, nobody would have cared. It wasn't specific details like these that caused us to enjoy the game.

© 2019 Condé Nast. All rights reserved. Use of and/or registration on any portion of this site constitutes acceptance of our User Agreement (updated 5/25/18) and Privacy Policy and Cookie Statement (updated 5/25/18) and Ars Technica Addendum (effective 8/21/2018). Ars may earn compensation on sales from links on this site. Read our affiliate link policy.

So committed, in fact, that modern WoW players are trying the beta and reporting what seem like bugs today but what were actually intended functionality 13 years ago. This became such a common occurrence that Blizzard publicly posted a list of known non-issues called the "WoW Classic 'Not a Bug' List." For example, hitboxes for the Tauren player race are much larger than those of other races. In a modern game, this would be seen as a serious balance issue (see: Apex Legends). But it's what vanilla WoW was like, so it has been faithfully reproduced.
×