Some quests in my guide are marked as "SKIP" and colored in red.  These quests are simply either too hard to solo or not worth the XP/time and are skipped.  My guide will only list SKIPPED quests if the quest is a direct follow up after completing a quest, not one that you have to click the NPC again to get it.  If you hover over the skipped quests, it will give info on why it is skipped in the guide (unless that info is already listed directly in the guide text).
Step-by-step class guides are on the way!  The 1-12 Mulgore Guide is the first guide to get all the individual class steps.  At the top of the guide, simply select which class you are playing and the page will dynamically update all the steps in the guide for that class (both text and images).  The rest of the guides will be slowly updated overtime to include all the class steps, but you can see how it's going to work with the 1-12 Mulgore.  I want to thank crazyK and his Placeholderguild for helping me out with the individual class content.  They are allowing me to get the 1-60 Alliance guide done while also getting all the class steps done at the same time, so everything can be ready for Classic launch (hopefully). 

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.
Other methods have been discussed. For example, mods could be crippled. DBM didn't exist back then, and the other boss that did that I don't remember the name of, didn't do as much back then as DBM does now. If our goal is to recreate the experience as it was, then obviously not having DBM would be a reasonable way to accomplish that. DBM simply existing, makes the game today easier than it was. So disallow it. Again, this is completely consistent with the spirit of vanilla. Remember one-button-decursing? That was nerfed. They crippled the capabilities of the modding API to disallow that because it made the game too easy. So what if they cripple it a little bit more to once again make the game less easy?
I joined twitch in 2013 with the gamer name of FuriousPaul and I streamed speedruns of the classic Castlevania games from 2013 - 2017. Lately my streams have died down quite a bit due to working on Classic WoW leveling guides every day.  Although I may come on occasionally and play a random game for fun on my Twitch stream.  I talk a lot about WoW speedrunning on my channel, so feel free to follow and hang out to discuss vanilla WoW if you like.  Classic WoW will be my main focus for a long time.  Unfortunately I will have to wait until Classic WoW comes out before I start streaming it.
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.
Along with revealing the WoW Classic release date, Blizzard also listed plans for both a beta and stress test of the game. Players who opt-in for the testing on their account manager page and have an active subscription will be randomly selected for the beta starting May 15. Then the developer will have three stress tests where players can log in to play the game for a short period of time on the following dates:
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.
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.
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.
×