We spoke with two Blizzard developers who have been working on WoW Classic, and as they explained, recreating World of Warcraft 1.12 involved reintroducing bugs that have long since been patched out of the game. But even they have had to check their work against WoW’s long update history, since the time at which certain features were introduced or bugs removed has gotten a bit fuzzy.
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.
 ":"  -  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.
×