Hey folks! I’ve got a small update here to help quell some of the rumors and let you know where we are at for WoW Classic. We recently began a phase of internal employee alpha testing. The new build data that many of you have been discussing over the last few days is simply part of this process. Phases like this allow us to test out the game content along with other functionality that will be used in the live game, like logging in through the Blizzard Battle.net 175 App.
FYI: If you’re returning to WoW after an extended absence prior to patch 5.0.1, it’s possible that you’ll have more than the maximum pet limit and/or more than 3 of a kind. However, this will be the only time that you’re allowed to surpass these limits. You will have to pare down your collection, eliminating your duplicates, in order to add new pets.
The first stress test began earlier today, and as such Bornakk added that Blizzard has already finished sending out invites for it. If you’re not aware, Blizzard has made it known a few days ago that players may be opted into the stress test even if they’re not officially part of the beta, as the developer is looking to really push some load into the servers. The community manager then went on to clear some specifics with regards to how they choose people for the beta and stress test. 

In player vs. player designated zones, you will still be viewable and attackable by players, but you are not left completely defenseless. While engaged in a Pet Battle, any attack from another player will break you out of the battle. You will receive a 3 second damage shield that will absorb 50% of incoming attacks. The same exact wild pet that you were previously battling will respawn after you come out of combat with the other player. However, if you defeated the primary pet in battle prior to leaving the match, the pet and its team will not respawn.
Dec 28, 2016 Better Living through Technology!(new2macros) *note: this guide is for people who haven't used macros or advanced keybinds and want to try. Macros are basically 'super buttons' that you can create in order to use multiple abilities and spells from the same button. This means even if you have 15 different abilities, you can key them all to 3-5 buttons. With macros you can do things like: 1) have all your buff spells on one button 2) 'hide' abilities that you don't use very often so they only show when you need them 3) 'group' similar abilities so that, for example, all your commonly used melee skills are on one button 4) maximize your rotation so that you're always one step ahead of the GCD Macros are great, but there are a few limitations: 1) complicated! -learning macros takes a good chunk of time. It's only something I've been able to do since my work gives me some 'free time' to cruise the UI/macro forum. 2) software limited -While very powerful, there is potential to abuse macros so that, for example, you could hit one button and your character would kill every mob in range (eventually). This potential for abuse has cause blizzard to put some powerful limitations on macros. More about this later. 3) the One Button rule -each macro button can use only one ability each time you press the button. You can code this so that it will use a different ability each and every time you press it (and on a different target!), but you can't press the button once and, for example, have it cast all 5 self buffs on you. I don't even know where to start?! To get started with macros, it's very simple. Just log on WoW and type /m. This brings up your macro box, where you just have to hit 'new' and the game will prompt for a name and an icon. I recommend that you leave the icon as a question mark. (?) The question mark means the game will automatically pick up the picture of the ability that the macro will use. My First Macro For your first macro lets just replace a normal ability you use on your bar in combat. I'm going to use paladin abilities here, but you can replace them with whatever ability you like. So to make my first macro, I went to the /m menu in game, picked a new macro, and gave it the question mark icon. Then I click on the icon, click on the empty box, and type: /cast This is the basic core of every macro. It's basically like the verb in a sentence. You can use different 'verbs' (called slash commands) but this is probably the most popular. Since I want this macro to cast Hammer of the Righteous, I simple type that in after the /cast. /cast Hammer of the Righteous And pow! I'm done! If you drag this onto your bar and hit it a million times, you basically have the paladin protection spec in a nutshell (lol). However this doesn't really give you any extra functionality over a normal keybind. The next thing I'm going to do is make the macro heal a friendly if I have a friendly targeted, or if it's an enemy it will use SotR (shield of the righteous). To do this you add a conditional. This says 'only cast this spell if 'X' is true.' It looks like this (with a breakdown of the macro underneath): /cast [help] Word of Glory; [harm] Shield of the Righteous \__/ \____/\__________/\/ \____/\__________________/ verb-conditional---|---separator|----------------| -------------------ability---------conditional----Ability What this macro will do is check the status of your current target. A 'friendly'(help) value will cause my paladin to heal the target. An 'enemy'(harm) value will trigger the attack ability. If you can grasp macros thus far, you've already learned enough to make macros useful for you. Putting this on your bar will basically cut the number of keybinds you need by 1. Modifier macro commands Another handy feature you can use with macros is called a Modifier. This may sound familiar but it's possible to set a macro so that it will use a different ability or spell if you hold down control, alt, or shift. Here's a basic example: /cast [mod:alt] Seal of Truth;[mod:ctrl] Blessing of Kings;[mod:shift] Righteous Fury; Seal of Insight If you had this macro bound to 1, and you press 1, it would cast Seal of truth (and the seal picture would be on the keybind). Pressin ctrl would change the icon to blessing of kings and would cast blessing of kings if you pressed ctrl-1, etc....Raygecow149 Dec 28, 2016
One player said in a comment posted in response to the list, “Yeah people don’t realize the sheer enormity of game system evolution WoW has gone through since release. I’m not the biggest fan of BoA by any stretch, but I’ve played since closed beta vanilla, and I doubt I’ll be going back to classic. Leveling was painful. Experiencing these old systems once was enough.”
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.
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.
Workaround as a player is simply to skip forward past that step in the guide, at which point it has steps for the other quests. I'm still on Bleakrock as that character, so I don't know if a duplicate "begin the evacuation" step exists after you've found all the missing people. In either case, just don't talk to Captain Rana about evacuating until you've completed all the other main/sidequests on Bleakrock, which are listed at the UESP link above.
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 far my favorite take is, of all things, this forum thread where the sheer volume of people reporting things as bugs that aren’t bugs, but just the way the game worked back then. I think I laughed the hardest at Warrior health regeneration is working at the expected rate, which is a very nice way of saying Yes, you’re dying a lot, that’s how it was for Warriors back then. I’ve said it before and I know I’ll say it again, but guys, all those supposed ‘dumbing down’ changes that got made between then and now were for a reason, and in a lot of cases? That reason was because it’s awful. Much of WoW Classic is going to feel like getting a sandpaper massage compared to the game as it is now — a whole host of conveniences and improvements have been made over the years. 
×