Nov 15 Classic is too easy for 2019 playerbase I'm not big on gameplay changes, really I'm not but... The game is just too easy for today's standards. I really think some of these raids and instances need a serious increase in difficulty. MC is a joke, most of the tier sets are unbalanced, and a lot of seasoned players agree but fear the toxic Classic community to speak up on this issue.Hopera237 Nov 15
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. Players started at level 15, and the only available zones were Westfall and the Barrens. 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. The debuff was removed on the second day of BlizzCon 2018.
Blizzard has put out a ‘not a bug’ list that covers many commonly-reported features that seem strange to players, such as players and NPCs that are feared running faster, and quest objectives not being tracked on the map or minimap. Respawn rates for creatures is much slower than it is in Battle for Azeroth, and this is intentional – it reflects the respawn rate in the World of Warcraft version 1.12.
In the past, if someone accidentally looted something they didn’t mean to in a group, players would have to contact customer support to trade it. In the modern system, players are given a period of time in which they can still exchange loot with others. This is a convenience we felt was worth retaining for Classic rather than making people go through customer support. (Sorry ninja looters!)
Rogue combo points posed another challenge, because the game’s modern resource system knows how to gain and spend combo points, but not how to lose them when changing targets. There are also the older combat formulas to consider, so we had to bring back the code for the prior combat formulas including critical hits and crushing blows. Their chance to occur is also modified by the difference between the defender’s defense and the attacker’s weapon skill. Yes—weapon skill is back. We had the data for this aspect of the classic game, but we also needed to restore the code that increased your skills when you used them and made your skill level affect your chance to hit or get a glancing blow.
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.
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.
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.