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.
Druid is one of the most versatile classes across all of World of Warcraft Classic. By picking Druid you will have plenty of options to choose from while leveling. However, in the end-game, most groups will expect you to heal, though, Feral and Balance druids are also very desirable for their Innervate and Rebirth abilities. Additionally, various animal forms will make traversing the world into quite an uncomplicated task.
Players will be selected for beta based on a range of criteria, including having an active WoW subscription. Opting into beta via the WoW Account Management page is the primary way to register, but other factors, like how long you’ve played the game, may also be taken into account. There will be three stress test periods: May 22-23, June 19-20, and July 18-19. Players will be able to reserve character names beginning on August 13 (or slightly ahead of that time, if you live in the Americas) with up to three reservations per WoW account.
This was a good start, but there were issues with how the developers used to handle updates to the database data. Unlike the source code, for which Blizzard had archives for multiple branches of the game that could be worked on and developed as separate pieces, early database data was overwritten with each commensurate update. Thankfully, that problem was fixed very quickly after launch, and when we looked, we found data going back to version 1.12—and even earlier.
One thing they told me when I dabbled into computer science back at university was that 80% of the bugs only take 20% of your time to fix. That's why sometimes you see issues persisting for very long times, not because the devs are lazy or incompetent, but because there is usually a priority list of problems, with the severe-but-easy-to-fix ones always taking precedent and the not-game-breaking-but-difficult-to-solve problems being last line.