Skip to Content
3-16-2009 @ 3:09PM
LESS QQ MOAR PEW PEW.I agree wholeheartedly with GC...idiots should learn to not suck and actually execute on mundane things like dodging flame walls.
3-16-2009 @ 3:15PM
When someone gets caught in AoE things like fire, either one of two things. The member is getting distracted by something else (ie Real Life Issues or Computer Acting Up) or the person is that dumb or is not paying attention enough to dodge the fire. If the person seldom gets caught and says he is having issues thats okay with me, however if he gets caught every single time and then blames other people for not healing him or not warning him, then he will get swift kick.
3-16-2009 @ 3:24PM
Lag does play in here too. It's not always poor ability to dodge AoE. This isn't a boss-encounter example, but I have had times where I've run frogger and not had a slime anywhere near me (on my screen) and have still died.If Blizz wants to cut into that 'buffer for screw-ups', they need to work on making their encounters lag-less (this, of course, refers to server-side lag and not client-side lag).
3-16-2009 @ 3:27PM
One of the problems is that healers going OOM can be from things that aren't easy to place. Now typically people who can't get out of the fire are the same people who have really bad dps/tanking/healing, but sometimes it's the case where that's their only issue. How do you tell someone they're bad dps if their dps is fine? Some peole aren't going to get that. Even though raiding has gotten rather easy, I'm not sure it's set into the minds of people that raiding in WoW is also very much about coordination and movement.
3-16-2009 @ 3:54PM
DPS that doesn't get out of the fire is bad DPS, regardless of their output. Dead players do zero DPS.
3-16-2009 @ 5:05PM
I am definitely a proponent of getting out of the fire. However, it'd sure be nice if there were fewer boss fights that involve some kind of fire/spit/shadow poop that is so huge that melee DPS often have to choose between getting out of the fire and actually being able to hit the boss.If Blizzard tunes the fights so that it's a viable option to either choose lower DPS/less damage taken or more DPS/more damage taken, then it's all cool. But Blizzard doesn't have a good track record of remembering that some of us have to stand next to the boss in order to damage it, and thus certain "mobility" challenges unfairly punish melee DPS.
3-16-2009 @ 5:35PM
@Shardrell If this happens, then you likely have a newer tank. If there are environmental hazards that are cutting down melee DPS, the tank should reposition the boss so that melee DPS can get back on it ASAP. Back in vanilla, when Rogues and Shammys were much more powerful, this was widely understood. Not repositioning the boss means less melee DPS, which means the healers have to heal the tank longer... which strains their mana. If a melee-heavy raid is having trouble downing a boss that has close-range environmental effects the tank may be killing themselves by not helping melee DPS as much as they can. I've also found tanks will often not provide enough room for melee players to get in behind mobs in instances... many times making melee DPS choose between pushing parries on the tank and losing DPS, or possibly aggroing another group. I think in general the tanking shortage is pretty much gone... but there is now a question of tanking quality. There are tanks that have been playing since vanilla that know how much a tank affects the party/raid in ways other than just taking hits to the face and have tanked very hard bosses, and those that have been tanking for 2 months that haven't had a chance to experience a lot. I've run a lot of instances and raids with a lot of tanks, and out of all of them, I'd say that two of them are great tanks. Not just that they stayed alive and held aggro, but they were aware of and did the double-dozen things that a tank can do to make an instance/raid go even better.
3-16-2009 @ 5:48PM
Huh? The hell?You stand in the fire, it's your fault period. There's no excuses to it period, l2p or GTFO. I prefer the latter.
3-17-2009 @ 10:58PM
Blaming lag is silly because it is predictable for the most part. If your latency is 500 ms, you only need to anticipate future placement by 1/2 of a second, which isn't exactly difficult. Retard Frogger is a perfect example of a situation where pretty much every death is due to player error, they either aren't anticipating their lag, or they just are paying attention.In fights with lots of AoE, there is a large margin of error for moving. If "lag" is killing you, you're trying to move within a fraction of a second of the effect going off, which we can all agree isn't Blizzards problem.The exception to this is real server lag, which is all but unheard of on my server (Scarlet Crusade). In short, lag gets blamed all the time (kind of like bad luck) but is only rarely the real problem.
3-21-2009 @ 10:57AM
1. On a server like Aggramar, server side lag is a real danger. It's certainly not an every day thing, but it is far from unheard of.2. Dodging a targeted instakill aoe like void zones with 800ms+ latency or 6 fps is not trivial.
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.