Once we had our starting point, we began taking stock of what we had in the source code and what we could make available, which included restoring the original development database from archival backups. After stitching various key pieces together, we had a locally rebuilt version of Patch 1.12 running internally. The team could create characters and do basic questing and leveling—and dying, which we did many times. For testing purposes. Obviously.
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. 

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.
Before work began on World of Warcraft: Classic, it was only possible for players to experience the original World of Warcraft by using private servers, which are illegal, often have stability or corruption problems, and generally are very imperfect recreations of the authentic World of Warcraft experience. As much as Blizzard has been aware of the desires of their community, until recently it seemed impossible for them to emulate Classic servers due to the technical hurdles of essentially having to run two massively multiplayer online games side-by-side. A breakthrough was then achieved that made it possible to run Classic servers on the modern architecture of current World of Warcraft servers.
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
Nov 15 Classic Box Cost Disappointed in the decision to bundle the subs and (at least for now) not have a separate Classic sub option. That said, can we at least get a separate box cost for access to classic? It would: - help alleviate temporary bloat and subsequent dead realms - servers would be more stable population-wise over time - remove the bulk of the need for sharding - give a solid idea of how many servers will be needed - allow blizzard to set up a separate classic forum for those with a monetary commitment - with a separate forum group, feedback would be limited to those with a vested interest The subs would still be bundled, but there would be a box cost, akin to what one would have to pay for BFA access. A very good to-the-point post from later on in this thread:... Another good post about how the current setup would necessitate sharding:... A decent (albeit short-term) alternative:...Brokenwind314 Nov 15
Use (“V”) to show all the patients status on screen. You will have special triage bandages (add them to your action bar/hot key) which should be applied to Critically injured, then Badly injured, and then injured. Once you started treating a patient do not interupt, just finish treating that patient before moving on to another patient. You should select your next patient before your are finished with the first one, then all you have to do is hit you hot key to start the next one.

A demo of the game was available at BlizzCon 2018, and was downloadable on home computers for anyone who purchased a BlizzCon ticket or virtual ticket. The servers became available when Opening Ceremony started at BlizzCon 2018 and was set to end on November 8, but was extended until November 12.[4] Players started at level 15, and the only available zones were Westfall and the Barrens.[5] It was based on patch 1.13.0, essentially patch 1.12.0 ported to a modern infrastructure. The first day of the demo, there was a playtime limit of a cumulative 60 minutes with a cooldown of 90 minutes, applied through the BlizzCon Exhaustion debuff.[6] The debuff was removed on the second day of BlizzCon 2018.[7]
×