Nov 13 WoW Classic BlizzCon Demo Pre-Download Hi everyone! We’re incredibly excited for you all to get your hands on the WoW Classic BlizzCon demo next week, and to help make things as smooth as possible, we’re making the client available to download for Virtual Ticket holders starting today. Over the next 24 hours, we’ll be enabling the ability to download the WoW Classic demo through the Battle.net app for players who have purchased the BlizzCon Virtual Ticket, as well as standard BlizzCon ticket holders who have added their Virtual Goodies code to their Battle.net account. If you don’t see the option to install the demo right away, don’t worry – you’ll still have plenty of time to download the client before the demo goes live during BlizzCon next week. We can’t wait for you to get a peek at what we’ve been working on, and hope you enjoy this preview of what’s to come!Ythisens156 Nov 13
Nov 15 5 reasons I'm doubtful of WoW Classic I played WoW from patch 1.4 until Sunwell. And I'm not convinced on Classic. 1. I understand nostalgia for the gameplay, and it was a great game, by I don't get why people would want the old graphics when it looked outdated back then. Someone will level a warrior or rogue at snail pace and those 2004 boring graphics will reinforce his perception that the game is bad because it looks bad. 2. The lack of a second talent tree. This was the most demanded feature and I don't see people sticking with the game without it. 3. This has always been in the game, but weekly resets, I never got it, let people able to reset raids. Maybe have a 2 hours cooldown, but if a guild wants to farm a raid every night, or twice on a sunday, or farm the first 3 bosses of MC, let them. Gearing 40-60 people with weekly resets, in this day and age, good luck. 4. Dungeon finder, not sure people will like that, again bad decision. 5. The graphics, no seriously, this is bad on every level of game design, it just make the game look worse, a straight negative with no benefit.Pekuakami24 Nov 15
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.
Even though the guide was developed with a hunter, the guide can be followed by any class. Except you have to do your class's quests which aren't a whole lot. I do have full intention to make my guide friendly with all classes in the future by listing all of their steps as well. There will be a toggle that allows you to show which class's steps you want to see in the guide. But this is coming later.
“To fill our pool of beta and stress test participants, we’ll be choosing dedicated players who meet select criteria from both the WoW Classic beta opt-in and the standard Warcraft beta opt-in. Participants will also need to have an active subscription or active game time on their Battle.net Account. While opting-in to the beta is the primary way to make sure you’re in the running to join the test it doesn’t guarantee an invitation to the closed beta test. We may also consider additional factors such as how long a player has been subscribed to the game so that we have the right mix of players to ensure great feedback toward making WoW Classic the very best experience for the community.”
The most important thing you should note is that there are no official beta keys. Blizzard opens the gates to their betas by granting access to your account — not sending you a beta key. If you’re in the beta, you’ll be able to download and play the WoW Classic client from your Battle.net launcher. If not, you aren’t in the beta. It’s easy to be tricked into thinking you’ll get a beta key from an email that looks like it’s from an official Blizzard address, but don’t believe their lies — they’re all fake.
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.
So we asked ourselves, would it still be possible to deliver an authentic classic experience if we took our modern code, with all its back-end improvements and changes, and used it to process the Patch 1.12 game data? While that might seem counterintuitive, this would inherently include classic systems like skill ranks, old quests and terrain, talents, and so on, while later features like Transmog and Achievements would effectively not exist because they were entirely absent from the data. After weeks of R&D, experimentation, and prototyping, we were confident we could deliver the classic WoW content and gameplay without sacrificing the literally millions of hours put in to back-end development over the past 13 years.