To get past these hurdles, the team looked at what we liked (art and data) of what we had and what we didn’t like (the code). We wanted to see if we could utilize classic art assets and data within our modern code and get things to play nicely together. Things didn’t quite work right out of the gate, but with some trial and error, we were able to pull together a proof of concept of how to get things to work together and have something playable. This built our confidence that we could deliver a Blizzard-quality experience with the modern platform.
This was a good start, but there were issues with how the developers used to handle updates to the database data. Unlike the source code, for which Blizzard had archives for multiple branches of the game that could be worked on and developed as separate pieces, early database data was overwritten with each commensurate update. Thankfully, that problem was fixed very quickly after launch, and when we looked, we found data going back to version 1.12—and even earlier.
What add-ons can do has changed over the years and have become much more sophisticated as authors have gained years of experience and savvy. We’re not 100% on a concrete solution to what this means for WoW Classic yet, but one thing we know is that we’re not going to roll all the way back to the 1.12 add-on API. Doing so would open the way for nearly complete automation of combat decision making allowing for “bot” behavior that is counter to the core WoW gameplay experience. This is one thing we know we don’t want. On the other end of the spectrum, the modern API offers some additional functionality for creating social features that could also undermine the authentic classic experience. We’re still figuring out the details and looking for a good middle ground. We’ll be keeping a close eye on feedback from the community and add-on authors on where we should be setting those boundaries.
Nov 15 How to fix paladin dps Just make holy wrath & exorcism work on all types of enemy but not affect player characters. It's an easy fix that will make pally dps better in pve but stay the same as they were in vanilla in pvp. Put this thing into a deep ret talent so it will require people to spec deep in ret to be able to dps. A good spot is add it with two-hand weapon specialization making it so that by putting talents into it all hostile aside from players and undeads(since they are already affected by the default version) to be affected by the dmg and effects of the spells effectiveness by 33%/66%/100%. I doubt they would even do this so im just throwing out ideas since too many of you dont actually read the forum and only read the OP here you go to explain a bit of my reasoning because this change wont make ret stronger than pure dps; clearly most of you people didnt play vanilla nor know anything about naxx. ...Toushin260	Nov 15 

Some class systems from the original game simply don’t have a modern equivalent. The class probably most affected by this is the hunter. The pet happiness and loyalty systems were removed a long time ago, as well as pet training and the ability to use both a ranged weapon and a melee weapon. In these cases, converting the old data to the new system wouldn’t work, simply because there is no new system to match. In this instance, we had to bring back the old code—and we did. Fortunately, the restoration went smoothly, though the reality of having to buy arrows or feed their pets again took a few people in our internal tests by surprise.
Nov 15 Article Explains Why No Communication So this is why we aren't getting updates, communication, customer service, etc, that Blizzard has provided in the past: https://www.influencerupdate.biz/news/67499/blizzards-saralyn-smith-the-power-is-with-the-influencers-we-all-know-that-its-the-age-of-influencers/ A youtuber actually breaks it down here for analysis: https://www.youtube.com/watch?v=NEaIAPoCDPc What an absurd joke. If this is going to be a successful game in ~8 months, we need the communication to be open, flowing back and forth, as it was in 2004-2006. Telling yourself otherwise is a lie. There's absolutely no reason third parties should be filters between Blizzard and the Players/Customers.Bynisarron31 Nov 15

What add-ons can do has changed over the years and have become much more sophisticated as authors have gained years of experience and savvy. We’re not 100% on a concrete solution to what this means for WoW Classic yet, but one thing we know is that we’re not going to roll all the way back to the 1.12 add-on API. Doing so would open the way for nearly complete automation of combat decision making allowing for “bot” behavior that is counter to the core WoW gameplay experience. This is one thing we know we don’t want. On the other end of the spectrum, the modern API offers some additional functionality for creating social features that could also undermine the authentic classic experience. We’re still figuring out the details and looking for a good middle ground. We’ll be keeping a close eye on feedback from the community and add-on authors on where we should be setting those boundaries.
Most profitable professions are considered to be Herbalism and Enchanting in pair. You can have Enchanting only for Disenchanting skill, it will bring decent gold. Consider the fact of disenchanting all soulbound armor, not just selling them to a vendor, but I do not recommend to disenchant any kind of weapons, it is more profitable to sell it to a merchant if it is a soulbound item, or sell it on auction house if it is BoE (bind on equip).
World of Warcraft Classic is currently in beta, which means some players are getting a chance to experience a much older version of the MMO ahead of its release. WoW Classic is based on how WoW played in August 2006, back around update 1.12. Back then, things were different. Tauren hitboxes were much larger, sitting could cause certain combat effects to not trigger and completed quests were marked with dots and not question marks. Strange days.
×