I made some route changes to the Horde levels 43-44 sections.  I have swapped 44 Dustwallow Marsh with 44 Desolace (the entire sections). This allowed me to do Deadmire (at lvl 43 instead of 38) and then go stop at TB to turn in Deadmire + The Black Shield at the same time, then fly quickly to do the Desolace stuff.  Doing 44 Desolace is now mandatory because I think its faster with the new routes. This will also make the level 53 grind much shorter.  I think these were great changes.
When it comes to levelling the Priest Class from 1-60 fast, XP grinding locations is only half the battle. You will need to make sure your weapon does enough DPS so that you can clear these mobs fast enough, it should also be noted that monster should be around your level to make sure to gain the 100% XP Reward. The Level your character should be before you start that specific location will be indicated to left in a Blue Color for Alliance [Lvl 35-39] and the Orange Color for Horde [Lvl 35-39]. The Mobs you are looking for in that specific area names are Bolded [Mob Name].
I consider myself a purist in that I would prefer classic to be released as close as possible to the original. Where that is on the spectrum of patch content will be up to blizz. I'm also not vane enough to believe that any single state of the game is the "Ideal" location we should be aiming for. There is common ground that we can agree on, and I would welcome more than a few changes as long as they are made in the spirit of keeping classic on the vanilla rails. 

All of this is keeping with the spirit of vanilla, which I think is more important than that a specific number be 11 instead of 12. And it would help to "resize the swing" by making the game harder to the more experienced community, and forcing people to re-discover the game rather than simply looking up whatever they want to know on a spreadsheet somewhere.
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.

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.
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.
The Horde levels 50-60 guide has been rewritten and revamped.  My 1-60 Horde leveling guide is now completely updated for the 1.12 Drums of War patch.  As you can see it is about 15% larger than the 40-50 guide (single largest guide page yet).  There is also a lot of route changes.  I moved the entire Silithus section from level 55 to level 58, which allowed me to include a lot more quests for that zone.  There is also a lot of other improvement to the route, including adding a lot more quests into the guide, mostly from Moonglade, Silithus and Eastern Plaguelands.  This will make the final level 59 grind much shorter.
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.
Good news, Warcraft fans – WoW Classic‘s release date has been revealed as August 27, and an invite-only closed beta test will begin tomorrow, May 15. Current World of Warcraft subscribers can opt-in to an invite-only closed beta test. This is the first firm info we have been given on World of Warcraft Classic since we first reported on it back in March of this year.
 ":"  -  Any time a step ends in a ":" instead of a "." means that the next step is part of the current step you are on.  This generally means the next step should be done while working on the current step.  This means every "start working on" or "continue working on" will end in a ":".  But this is used with other occasions as well, so keep this in mind.
2. the only gear that was easily attainable sort of was the old level 60 pvp sets. if the classic servers stay locked in progression of any expansions then grinding the PvP gear for both pvp and raiding would be the top choice in casual play. "IF" they implement the LFG and LFR tools for the 16-40 man raids, heh it would be very interesting, otherwise get use to Trade chat being filled with PuG raid groups looking for people, because that was the norm back in the day.

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.
“To fill our pool of beta and stress test participants, we’ll be choosing dedicated players who meet select criteria from both the WoW Classic beta opt-in and the standard Warcraft beta opt-in. Participants will also need to have an active subscription or active game time on their Battle.net Account. While opting-in to the beta is the primary way to make sure you’re in the running to join the test it doesn’t guarantee an invitation to the closed beta test. We may also consider additional factors such as how long a player has been subscribed to the game so that we have the right mix of players to ensure great feedback toward making WoW Classic the very best experience for the community.”
All of this is keeping with the spirit of vanilla, which I think is more important than that a specific number be 11 instead of 12. And it would help to "resize the swing" by making the game harder to the more experienced community, and forcing people to re-discover the game rather than simply looking up whatever they want to know on a spreadsheet somewhere.
×