Nov 7, 2017 Welcome - Please Read! Welcome to the Classic Discussion forum! This forum is here to provide you with a friendly environment where you can discuss all aspects of World of Warcraft: Classic with your fellow players. Community forums work best when participants treat their fellow posters with respect and courtesy, so we ask that you take the time to read through the forum Code of Conduct and guidelines before posting. Code of Conduct: http://us.battle.net/en/community/conduct Getting the Most Out of the Forums: http://us.battle.net/wow/en/forum/topic/2016792409 Important Reminders: Search The search function at the top of the World of Warcraft community site is extremely effective and robust. Before you create a new forum topic, please be use it to search for similar topics, blog posts, or web pages that may contain the answer for which you are looking. Making a new thread on an existing subject can result in your thread being deleted or, if you continue to re-post the same content, the loss of your forum privileges for spamming. Rating The forum rating system can be used to promote positive discussion and even report posts that violate the forum Code of Conduct. By hovering over a post you'll be presented with several options, including a "thumbs up" (Like) icon. Clicking the "thumbs up" icon will rate the post up. If enough people like a post, it will gain a Highly Rated status and appear at the top of related search results. Highly Rated posts will also have a highlighted background. You can also quickly report a post as trolling or spam, or use the report function to fill out a more comprehensive description of a violation. Please note that you can only rate each post once. Use your power wisely to help foster a positive and helpful forum community.Ornyx1 Nov 7, 2017
To avoid this, the team “taught” our tools some new tricks so that we could update WoW Classic without affecting the current version of the game. We copied the 1.12 data into a new project, taught the tools to distinguish between them, and now as the WoW Classic team makes patches, any changes stay within the Classic chain without ever interacting with the current game’s data. This might seem simple—like copying a directory—but the tricky part is teaching all our tools how to understand this so that they can make edits automatically. Being able to use our internal tools is a huge benefit, and we wanted to make sure Classic had access to all of WoW’s infrastructure and data.
Where to get materials and reagents you may ask? Buy for cheap off farmers in bulk or track Auction House lots. Get in touch with most big sellers. Communication is important here, send a whisper or write them a letter. It would be good for both of you to establish business relationships. Constant suppliers and buyers is convenient for both parties to save the time and effort.
Nov 15 We ordered vanilla not vanilla with sprinkles 1. Sharding/Phasing was not a part of the classic experience. The launch surge and often times overwhleming population fighting over quest mobs and loot was impactful on a human level which brought people together to make parties so they weren't fighting or made people bitter rivals. And that ten minutes you spent competing with people to loot that bucket before it despawned for another few minutes was intense. 2. Loot trading was not a part of the classic experience. Ninja looting was a real thing, a crime you could commit which united the community up in arms against you, blacklisting you. That's a feature for modern WoW, not genuine classic. This is a recreation. Not a remaster. Not reforged. We ordered vanilla, not vanilla with sprinkles on it with modern hand holding baby coddling streamlined bogus. That's more suited to your modern WoW playerbase, not the millions waiting patiently for the game they knew and loved over a decade ago. I don't want to sound like an entitled brat, but when you advertise a product, don't change it behind the scenes. Please Blizzard, don't add these things. They kill aspects of what made classic wow such a special phenomenon that rallied people to make private servers in its honor. I'll go play one if this isn't authentic, because those unofficial servers would be more authentic.Rhystael95 Nov 15
At BlizzCon 2018, the WoW community got their first chance to experience World of Warcraft Classic for themselves. To help players understand what goes into bringing a Blizzard-quality experience like this to life, software engineers Brian Birmingham and Omar Gonzalez along with Game Director Ion Hazzikostas took the stage Saturday afternoon to share their insights.
Our initial runs exposed a few (expected) issues: the game sometimes crashed, didn’t recognize our modern video cards, and was incompatible with our current login system. That first pass also couldn’t support any of our modern security and anti-cheating capabilities. Clearly we had a lot of work to do to make WoW Classic live up to the Blizzard standard of quality, and deliver the experience players want.
It is also worth noting that World of Warcraft Classic isn't exactly an archive from 2006. It has been rebuilt from patch 1.12, using modern data architecture and reaps the benefits of the modern engine. This means a lot of non-controversial quality-of-life features will still be present and it is possible to run WoW Classic servers on modern server architecture. As you can imagine, much has changed in the last 13 years in the tech space. That's before smartphones were even a thing. The modern engine no longer allows certain behaviours that could be used to get out of bounds, also adds widescreen monitor support and accessibility options! However, it does have the disadvantage of not being able to run on 32-bit systems which isn't that kind to older systems considering the game is from 2006.
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.