To get past these hurdles, the team looked at what we liked (art and data) of what we had and what we didn’t like (the code). We wanted to see if we could utilize classic art assets and data within our modern code and get things to play nicely together. Things didn’t quite work right out of the gate, but with some trial and error, we were able to pull together a proof of concept of how to get things to work together and have something playable. This built our confidence that we could deliver a Blizzard-quality experience with the modern platform.
Nov 15 Loot sharing. Fools How stupid is the community about loot sharing? You know there is master loot right? Stop being dumb guys like holy crap. You also know that if you're the guy setting up a group or joining a group you have a option not to run or you can pick player's of different armor types... If you're a cloth wearer you just don't run or set up a group with other cloth wearers. Like this is something so simple and the community can't graps anything. I feel bad for blizzard sometimes with having to deal with brain power of this community. The community: "Oh, I didn't think about that. Derp, I'm an idiot."Plewtoe23 Nov 15
You're absolutely right! I've changed the opening—I hope it gives you and your list the credit you deserve. As for those other tools, I didn't include them originally because I didn't consider them to be class specific. I'll include the Base Stats Calculator here, plus add a message at the top directing people to your list if they want a more comprehensive index!
After this past year of working on this project and forging our way through the various bugs and challenges, one consistent theme that’s emerged is that the difference between what we have and what we want is clearly visible. When we look at today’s World of Warcraft, we can see the differences between the modern game and the classic one. If we tried to update the reference client, we would have instead been tracking down a lot of “invisible” changes such as exploits waiting to be abused, crashes that don’t show up until you have millions of players online at once, and more. We chose to approach the problem in a way that makes our job clear and obvious instead of difficult and hard to see.
Nov 15 NO CHANGES. Change it, we won't play. NO server cap above 2500 NO further restrictions towards addon APIs NO sharding NO increased/decreased XP rate NO loot trading NO CRZ NO phasing NO connected realms NO dynamic respawn NO LFD/LFR NO new models NO dual talents NO wow token NO character boost NO shop NO transmog NO achievement NO heirlooms NO arena NO bfa character customization NO esports NO rated BG NO raid re-tuning NO class re-balancing NO personal loot NO flying NO mythic keystone dungeon NO multiple difficulties NO aoe-looting NO Death Knight NO Monk NO Demon Hunter NO blood elf NO draenei NO playable worgen/goblin NO allied races NO pandas No anti-cheat that blocks wall climbing (I want to see mount hyjal) YES to CRBG in the final patch. NO to any other cross realm technology These changes are unacceptable. Sorry I am speaking the truth. BTW. NO "NO CHANGES, BUT ..."Castradys254 Nov 15
Who is Joana? Joana, (AKA Mancow, or FuriousPaul) speedran 1-60 vanilla WoW from 2005 - 2007. I have been server first to level 60 seven times in a row, along with winning Blizzard's "First to level 50" contest they held back in 2006. I also have the fastest time through original vanilla 1-60 WoW in 4 days 20 hours. I have produced a very useful 1-60 horde speed leveling guide along with a 1-60 speedrun video.
Things like Tauren melee reach being bigger, which is something I experienced going away live during Black Temple Illidan progression (at least for that particular encounter), is confusing to players as it's a significant advantage over other races in some instances. No quest tracking is another apparently confusing issue, as many Mankirk's WIfe seekers well know, and there's a whole lot more where that came from: