Nov 15 Dual Boxing in Classic I was seriously thinking about being a masochist and playing a paladin in classic but then I wondered if dual boxing will still be possible in classic with the change in engines running the game. I've never dual boxed so will have to research how it works. However, it hit me that I can dual box a warrior and a priest then transfer the priest to my main account at 60 so I will have the best tank and best healer in the game to play around with. Anyone else planning on doing this and have any good resources to start learning about it?Twiinkedd6 Nov 15
Nov 15 Classic hit me like a truck I had no interest in it what so ever. After watching the blizzcon demo - I can’t stop thinking about it. The combat it’s so visceral. The world is so much bigger and so much more dangerous. Each fight reminded me of dark souls. I’ve been watching only classic and vanilla vids since blizzcon, it’s actually ruined retail for me. I was actually enjoying raiding in BFA but now I don’t want anything but to play classic and immerse myself in it. What is this sorcery? I heard vanilla wow was addictive, but really? I feel like I’m in withdrawal and I haven’t even played it yet. I think I’m in trouble once it releases. I don’t want to log into retail anymore :(Gripp204 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.
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.
With the Classic beta now out it seems every related article somehow manages to spark the eternal war of "Vanilla was the best WoW sucks now" and "lol nostalgia goggles, Vanilla sucked, enjoy your two weeks of Classic". I have to say, even though I understand the principles behind the battle and the reasons people behave and talk this way... I actually REALLY don't get it on a deeper level.
Other methods have been discussed. For example, mods could be crippled. DBM didn't exist back then, and the other boss that did that I don't remember the name of, didn't do as much back then as DBM does now. If our goal is to recreate the experience as it was, then obviously not having DBM would be a reasonable way to accomplish that. DBM simply existing, makes the game today easier than it was. So disallow it. Again, this is completely consistent with the spirit of vanilla. Remember one-button-decursing? That was nerfed. They crippled the capabilities of the modding API to disallow that because it made the game too easy. So what if they cripple it a little bit more to once again make the game less easy?
The Horde levels 50-60 guide has been rewritten and revamped. My 1-60 Horde leveling guide is now completely updated for the 1.12 Drums of War patch. As you can see it is about 15% larger than the 40-50 guide (single largest guide page yet). There is also a lot of route changes. I moved the entire Silithus section from level 55 to level 58, which allowed me to include a lot more quests for that zone. There is also a lot of other improvement to the route, including adding a lot more quests into the guide, mostly from Moonglade, Silithus and Eastern Plaguelands. This will make the final level 59 grind much shorter.
"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."
While our initial effort helped us determine the experience we wanted to provide, this second prototype really defined how we’d get there. Starting from a modern architecture—with all its security and stability changes—means the team’s efforts can be focused on pursuing an authentic classic experience. Any differences in behavior between our development builds and the patch 1.12 reference can be systematically cataloged and corrected, while still operating from a foundation that’s stable and secure.
The system is automated, meaning that once slots are available, beta testers will be chosen, without any beta key to speak of. Kaivax then goes to stress the importance of your account security, stating that, “any third-party e-mail messages, websites, or in-game whispers that offer beta keys or access to the WoW Classic Beta should be considered illegitimate and ignored or reported.”