Saturday, February 19, 2011
Hotfix Rodeo: Two Nineteen Eleven
Posted by Dustin Thomas
In totally unrelated news I finally got my camel mount from Ramkahen. That faction was very low on my exalted priority list (only the mount was even of interest to me) so it took me this long. I personally think the mount looks great; they handled model scaling very well and the mount looks regal as hell.
The first thing I want to cover are the changes to the dungeon finder and specifically the vote kick feature. Even in it's earliest inception, the vote kick feature seemed like a necessary function that wielded unimaginable power (well for dps only thought, tanks / healers were like lawlz insta-queue) for the players involved. I have some serious issues with the vote kick feature as a whole, however for the sake of addressing the hotfixes I'll operate under the impression that it's here to stay. You do have to admit, just deleting vote kick would remove the need to hotfix it. Now it's also important to remember that these dungeon finder hotfixes are in place but some require a server restart before we'll see them in action.
Players who are outside a dungeon for more than a few minutes are now immediately able to be kicked. This change seems to be an overall positive one. There really isn't a need to be outside the instance for any extended period of time and being able to vote kick those people who AFK is one of the positives of the vote kick feature. I'm sure people will complain "well I had to repair and my hearth was on cooldown blah blah blah". Get real. I assume if that is the case you can (gasp!) communicate that with your group. This is geared more toward phantom AFKer's and I like the change.
If queuing as a group with a tank or healer, and the tank or healer drops group (or is kicked) soon after joining, those that queued with them will also be removed from the dungeon. This hotfix is confusing to me. The only situation where I can see this would happen is when someone queues as a tank to speed up his groupmates queues, the drops leaving a full group minus one and a significantly shorter wait time. Ideally it's a great work around (if you have an alt that can eat a Deserter buff) but in the practical sense I don't think I've ever noticed this. I have noticed a tank drop right away but I always just assumed it was because it was SFK or Stonecore. This fix has the potential for some serious issues if not implemented correctly. By correctly, I mean taking the term "soon after joining" and really doing some research on it. I'm in a huge guild, with over 600 toons and I often group with people I don't know that well. It's a great way to get to know them and get a sense of their abilities. There are times when people have to leave, for whatever reason, and to punish other people in that group is hardly a fair thing to do. If "soon after joining" means 2 minutes or less, I think this is a reasonable change. If "soon after joining" means 20 minutes or less, Blizzard and I are gonna go "rounin' roun to re ro".
The penalty for using the Vote Kick feature too often is not issued to a player who kicks someone with whom they queued for a dungeon (i.e. the party member being selected for removal is not a player randomly selected via the Dungeon Finder). So this makes me wonder about that other part of this hotfix. It says if you vote kick a tank or healer you queue with soon after joining, the whole queued group is removed. How is it possible to be removed but not penalized for doing so? Blizzard is getting too technical in their attempt to help us understand the intricacies system of vote kick. I can't see the back end system of the game and nor do I care. In it's current inception the ONLY penalty is being removed from the group, so to say you can be removed but not penalized is consolation at best. If they had some king of rating system (like Arena rating) that was assigned for running instances it would be possible to separate the idea of removal and penalty but that seems unduly complicated.
Mangle (Bear) and Maul (Bear) damage has been increased by approximately 10%. Wait, what was I saying about flip flopping? Oh yeah, DON'T DO IT! So let me get this right, bear damage (not threat, but damage) is too high so you nerf it 20%. Then bear threat (with no glyphs or talents that increase expertise) is too low so you give us back 10%? Seriously. Stop. Run the numbers, test it out, then drop a patch. You are making yourself looks awful, simply awful.
Well that about sums up what mattered most to me in the recent (and we're talking like daily here) slue of hotfixes. I know there are a ton more (include some obvious changes to Paladins and Priests) but I'm not an expert on those classes and how the changes will effect them overall. Until next time remember: follow your kill order, don't drop your CC, and hug your tanks!