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.
I received a beta invite for Classic, and had also been an alpha and beta tester for the original game 15 years ago. That isn't unique; plenty of people in Northshire Valley had had the same experience, suggesting to me that active players who were Day 1 WoW gamers or had participated in the original tests might have gotten priority invitations to this one.
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.
This is for those who want to own a piece of Vanilla WoW history! This tier requires your physical mailing address so I can mail you the printed paperback binded mini leveling guide/book. By default I will sign "Joana" on each book! If you wish for me to write something else out (such as my real name) you can request that as well. And finally, thank you for the support and I will continue to make the best leveling guides for WoW!
":" - Any time a step ends in a ":" instead of a "." means that the next step is part of the current step you are on. This generally means the next step should be done while working on the current step. This means every "start working on" or "continue working on" will end in a ":". But this is used with other occasions as well, so keep this in mind.
You are right here. The Rematch string is part of the Info box, and as such it should be parsed correctly. (The string that contains the correct and breed/damage-specific min health requirements). This should be enough, but, I think there are also folks that aren’t using Rematch. They also should know of the type-specific min health requirements. Unfortunatly the default forms of the page don’t offer any detailed entries for the min health. They only offer one entry (for all damage types), and I always put the worst-case min health there (for pets that are weak against the expected damage type)