Skip to Content
4-16-2008 @ 9:53AM
"Blizz wouldn't be stupid enough to give a dev an unfair advantage in a community contest."Really? So it also wouldn't have a Warlock complaining about other classes being able to trounce them help the direction of nerfs? Nor would it let those Warlocks have info that isn't even in the PTR, would it? Nor would it delete those posts after people pointed out that someone's guild mate being bad was causing major nerfs to other classes, right?This company made a mistake hiring someone that had openly declared that hybrids were horrible and didn't deserve to be able to do more than one thing and putting him in charge of a game where 1/3rd the classes were "hybrids". They then gave all the cool tricks the Paladin had to the warrior, gave the warrior a role besides tanking (thus making it a hybrid) and made it more powerful than it had any right to be. PVP nerfs coming into PVE have horribly hurt this game. Some classes get PVP nerfs that don't even make sense. I think the easiest way to fix this game is fire him, get someone who plays one of the harder classes to be in charge and put 2 people below them to make sure the Devs classes aren't able to dominate.Would Blizz let a developer win the Tourney? Nope. Probably against the standard rules. Would one of their guildmates win? Most likely. They have info no one else has about how those classes work and "class balance tweaks" might happen.
First time? A confirmation email will be sent to you after submitting.
Members enter your username and password.
Enter your AOL or AIM screenname and password.
Please keep your comments relevant to this blog entry. Email addresses are never displayed, but they are required to confirm your comments.
When you enter your name and email address, you'll be sent a link to confirm your comment, and a password. To leave another comment, just use that password.
To create a live link, simply type the URL (including http://) or email address and we will make it a live link for you. You can put up to 3 URLs in your comments. Line breaks and paragraphs are automatically converted — no need to use <p> or <br /> tags.