However, that’s not the full extent of Blizzard’s announcement. The developer behind World of Warcraft Classic has also announced that it will release a closed beta test for chosen (note this word) players to participate in. The closed beta is meant to test Blizzard’s servers, which I’m guessing will be pretty full once the game actually releases. Blizzard hopes that this beta can prepare them for a smooth launch, since this is pretty big for World of Warcraft players.
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.
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:
One of my favorite features is the Smart Injection System, which automatically determines the optimal place for your character to get started with the guides, based on your level and quest history. In other words, it doesn’t matter what level you are currently, you can jump right in and continue seamlessly with the guides. It also means that you don’t have to be a slave to the guides, they work perfectly even if you’re also leveling in instances, battlegrounds, using heirlooms or rested EXP. If your level ever gets ahead of the guide, just use the built-in feature to skip to the right place again. Very cool.
Learned this today: posted a comment, came back later to see if there was any feedback, reloaded the page: the page posted a copy of my comment. That was not what I wanted. I just wanted to check if my comment was posted and if there were some responses. I did not want to post a copy of my comment from 5 hours ago. And, a humble guess, I think the majority of the users are not expecting such behavior either.