We’ll be performing our first stress test for WoW Classic on Wednesday, May 22, from 4–6pm PDT. During this time, the closed beta test realm will be unavailable. Those who are currently in the beta test will only be able to login to the stress test realm during this time and beta testers can participate using their existing installation. We’ll also be adding a significant number of players to the stress test from the pool of people who have already opted in for the beta but have not yet been selected.

When hovering over an ability, the tooltip will tell you whether or not that attack is weak or strong against certain pet types. Additionally, you can hover over the opposing team's pets and view their attacks during combat. This will be important since it’s a good idea to pit a pet that's strong against the opponent's pet who's vulnerable to that type.

The World of Warcraft is going back to its roots with WoW Classic. Giving players the chance to return to the game as it was around the time of its launch, WoW Classic is set to launch worldwide on August 27. However, ahead of its imminent release, the team at Blizzard are offering a closed beta test for WoW Classic, and we’ve got all the details players need to jump in on the action.


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.
Combat is turn-based and there is no time limit on each round in a PVE Pet Battle. You can take your time to determine which spell to use next. Some pet abilities have multiple round cooldowns, while others can do extra damage if certain conditions are met. Be creative and have fun testing which combination of attacks works best against different wild pets!
1 All expansion guides are written in the Battle for Azeroth beta in order to have them ready on launch day. It's important to note that betas can be buggy and unstable and may delay and even halt our progress on the guides. Furthermore, the time between the start of beta and the announced release of Battle for Azeroth is much shorter (by about 2-3 months) than past betas. As a result, our primary focus is to have the Leveling guides updated by the launch, and only if those are complete and time remains will we work on updating the remaining guides. All guides not finished in beta will be updated post launch. You can read more about this here.
So committed, in fact, that modern WoW players are trying the beta and reporting what seem like bugs today but what were actually intended functionality 13 years ago. This became such a common occurrence that Blizzard publicly posted a list of known non-issues called the "WoW Classic 'Not a Bug' List." For example, hitboxes for the Tauren player race are much larger than those of other races. In a modern game, this would be seen as a serious balance issue (see: Apex Legends). But it's what vanilla WoW was like, so it has been faithfully reproduced.
I used Zygor for legion and BFA, used AA on an alt for BFA. Personally i like Zygors format more. I like being able to target things like achievements. I used Zygor to get my Mindworm and my Lucid Nightmare as well as finish the Rep grinds for the allied races. I have zero complaints. My experience was great. I also used Zygor for some professions, recipe acquisition, a couple mounts, all of the Suramar quest line. Thank God for that. And for the last zone of Draenor on my Demon Hunter.. i forget the name.. Whatever the big daily hub thing was called.
To actually get access to the beta, which has already started and continue to add more players, you need to sign up via your Blizzard account management page. Under Games & Subscriptions, scroll down to Beta Access and visit the Beta Profile Settings page. Once there, you’ll see a grid of available betas you can opt into. Once you’ve checked WoW Classic, hit Update Preferences and you’re set.
Bonz, Sid, and Zygor are then seen right before the Battle City finals. The three reside in a nearby cemetery and trick people into giving up their Locator Cards. However, Yami Bakura is not intimidated by their act and challenges them to a Duel in which the winner gets all the Locator Cards, and thus goes directly to the Battle City Finals. Bakura wins in just a few moves, and then banishes them to Hell (the Shadow Realm in the dub).
Allied Races Overview Everything about Allied Races, new playable races in World of Warcraft: Battle for Azeroth, including unlock requirements for each race, Heritage Armor, customization options, and speculation when they are playable. Battle for Azeroth (110-120) Leveling Tips and Consumables How to level from 110 to 120 as quickly as possible in WoW Battle for Azeroth, including recommended zone order, best consumables, general leveling tips, and best addons. Azerite Armor Overview and FAQ Everything known about Azerite Armor and Azerite Traits in Battle for Azeroth including what Heart of Azeroth Level they unlock and how to respec them using an Azerite Reforger. The Battle for Lordaeron - Introductory Battle for Azeroth Quests This guide is an overview of the Battle for Lordaeron scenario, including a walkthrough from both Alliance and Horde points of view. Wowhead's Guide on How to Play World of Warcraft The basics of getting started in World of Warcraft as a brand-new player. Game installation, character creation, how to move, and complete your first quest.
We’ll be performing our first stress test for WoW Classic on Wednesday, May 22, from 4–6pm PDT. During this time, the closed beta test realm will be unavailable. Those who are currently in the beta test will only be able to login to the stress test realm during this time and beta testers can participate using their existing installation. We’ll also be adding a significant number of players to the stress test from the pool of people who have already opted in for the beta but have not yet been selected.
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?
Thanks for bringing this question to our attention. Addons and their availability are a large part of what makes WoW great. Any addon that enhances your User Interface [UI] is totally okay, however, anything that automates your character's play [you can walk away from your computer and your character is still leveling, in combat, etc] is decidedly not okay and falls under exploitation and botting. If you are concerned at all or think the particular addon/guide may fall under that second category, for your safety, I recommend you just stay away from that one as violations of the Botting/Exploitation aspect of the Terms of Use is a bannable offense. If you have any questions about what might be considered automated play, I recommend you refer to the Terms of Use and follow them to the letter. You may find those Terms here: http://us.blizzard.com/en-us/company/legal/wow_tou.html.

Some players have been surprised by these apparent flaws—even players who have been eagerly awaiting WoW Classic's release based on fond memories of vanilla WoW. In truth, it has been so long since WoW first released, players' memories may not always be accurate. Some details might be fresh, but others might be lost in time, and it's those lost details that could surprise players revisiting the original experience in WoW Classic.


Beginning May 15, select WoW players will be invited to participate in a small-scale, focused closed beta test. Players will also get a chance to help put our servers and technology through their paces in a series of stress tests running from May through July—you can opt in now through Account Management and select the WoW Classic beta. Subsequent stress tests will extend the opportunity to even more players. Level caps will also be in place to ensure we’re emphasizing the “stress” in “stress test”
World of Warcraft Classic is currently in beta, which means some players are getting a chance to experience a much older version of the MMO ahead of its release. WoW Classic is based on how WoW played in August 2006, back around update 1.12. Back then, things were different. Tauren hitboxes were much larger, sitting could cause certain combat effects to not trigger and completed quests were marked with dots and not question marks. Strange days.
Much like an encounter with a wild pet team, PVP Pet Battles are turn-based. However, unlike the PVE version, the PVP combat system is timed and any ability for each round must be chosen within that time limit otherwise it will assume you have passed a turn. A time penalty is applied if you take more than 15 seconds to choose an action, resulting in progressively shorter round timers for you.
I made some route changes to the Horde levels 43-44 sections.  I have swapped 44 Dustwallow Marsh with 44 Desolace (the entire sections). This allowed me to do Deadmire (at lvl 43 instead of 38) and then go stop at TB to turn in Deadmire + The Black Shield at the same time, then fly quickly to do the Desolace stuff.  Doing 44 Desolace is now mandatory because I think its faster with the new routes. This will also make the level 53 grind much shorter.  I think these were great changes.
To me, certain character limits tend to be problematic not because of the length of actual content, but because of formatting tags and embedding taking up a lot of characters. This is something I experience on most of websites, not just this one, but the most aggravating issue over here is linking to user profiiles and other sources of strategies, which could be alleviated with internalisation of link paths and @mentions.

WoW Classic seeks to recreate the "vanilla WoW" experience—that is, WoW as it existed before a series of seven game-altering major expansion packs from 2007's The Burning Crusade to 2018's Battle for Azeroth. To achieve this, Blizzard has rebuilt the game based on archived data from back in 2005 and 2006 (patch 1.12 is the goalpost—the current game is on patch 8.1.5). The company has committed to meticulously presenting the experience exactly as it was back then—warts and all—with only a small number of unavoidable or critical changes.


Some players have been surprised by these apparent flaws—even players who have been eagerly awaiting WoW Classic's release based on fond memories of vanilla WoW. In truth, it has been so long since WoW first released, players' memories may not always be accurate. Some details might be fresh, but others might be lost in time, and it's those lost details that could surprise players revisiting the original experience in WoW Classic. 

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.
Along with revealing the WoW Classic release date, Blizzard also listed plans for both a beta and stress test of the game. Players who opt-in for the testing on their account manager page and have an active subscription will be randomly selected for the beta starting May 15. Then the developer will have three stress tests where players can log in to play the game for a short period of time on the following dates:
×