Why not register and interact with one of the most knowledgeable and helpful communities in Warcraft?


  #1  
Old 08-05-2008, 04:12 PM
New Registrant
 
Join Date: Aug 2008
Posts: 2
the phantom death

ok, something very strange has been happening to me the last few week. Thought I'd get some of you guys opinions since blizzard doesn't seem to have one on this case. Recenty, on two separate kara runs and one ZA run, I've been dieing a very strange death. For example, last night again fighting prince ( I'm main tank of course) we get him down to about 40% or so and BAM! I die. And I mean I went from nearly full heath to being dead. This happened twice on consecutive trys. Each time I'm checking the combat log and it goes something like this--take 2.5k dam (435 blocked) / heal for 2k/ lifebloom yada yada / 2.5k dam ( 435 blocked)/ parry/ dodge/ heal 4k/ parry/ heal 3.5k/ 2.5k dam (435 blocked) BAM! ARMOR TAKES 10% DURABILITY DAM
what in the world is going on here??
Again this twice on the same kara run against prince, once against prince a few weeks before and a few times in ZA about a week ago.
I'm completely clueless and so is blizzard. Am I bugged or something?
If anyone has any thoughts , it would be appreciated.
Reply With Quote
  #2  
Old 08-05-2008, 04:16 PM
Sponsor
WoW Characters
 
Join Date: Feb 2008
Location: texas
Posts: 1,258
Blog Entries: 1
I have had a few similar deaths as a fury warrior, once on VR and once on Gruul....going along fine, full on health, 1/2 second lag spike than somehow I am dead, somehow even though I am dps'ing from behind I am getting hit by some kind of frontal cleave and getting 1 shot.
Reply With Quote
  #3  
Old 08-05-2008, 04:25 PM
Established Registrant
 
Join Date: Jan 2008
Location: Pennsylvania
Posts: 1,028
If this is happening around 40% on prince, there's a possible explanation:

I'm sure you know that Prince can enfeeble people, which lowers their HP to 1. He targets 5 people with this ability. Normally he doesn't target the tank, but there are two cases in which he might:

1) It's not that he doesn't target the tank, it's that he doesn't target the person who has accrued the most threat. There's a threat buffer of 10% for melee and 30% for ranged DPS. If the rogue passed you in threat, he may not pull aggro, but that means that you can be enfeebled. If the tank gets enfeebled, he's one-shot. The solution is to make sure all your DPS are watching the threat-meters closely and DO NOT PASS YOU

2) During the transition from Phase2 to Phase3, Prince throws his axes out. At this moment, it's rumored that he ignores his threat completely and can enfeeble the tank. The solution is to make sure he's already recently enfeebled the rest of the raid when you force this transition. It's best to do this right after enfeeble wears off, because you don't want him to throw his axes while an enfeeble is still going.

I have no idea what could have happened in ZA, though. What did the logs say here? If it was on the bear or the lynx, it's possible that your offtank wasn't in rage of the cleave and you took full damage from them, but without more data it's hard to say.
Reply With Quote
  #4  
Old 08-05-2008, 11:00 PM
New Registrant
 
Join Date: Aug 2008
Posts: 2
both of the replies give a good possibily of what may be going on and I thank you for them.
As for Tats reply, I do know that if I were to say hit the X button to sit down I can get crit hit , just like you sit down when logging out, but I'm not sure if a lag spike constitutes a (log out and sit down) . I'm going to continue my research on this one.
As for Ebs, what you say about the prince fight is so very true, but what throws me for a loop is the ZA senario, yes it was going into the bear fight but that fight went fine. What didnt go fine is the pull at the bear fight. It was my first time there so forgive me if I'm mixing up some of the details, but I'm talking about the mob with the two guys on mounts along with some other trash. The other tank and I split the mobs to each side of the platform and began our tanking duties. It was during this fight that I had the same thing happen that has been happening in the prince fight the last few times. Full health, then Bam! dead. And each time combat log showed the same thing, which was nothing to indicate me getting hit enough to die. And just like the prince fights, it happened not once but twice in a row.
Since you guys are tanks you probually can feel my frustraition when an entire raid is wanting to know why we wiped the way we did. These kinds of things don't get you invited to future raids if you know what I'm saying.

Anyway, if anyone else has any idea's I'd love to listen to them.
Reply With Quote
  #5  
Old 08-06-2008, 01:09 AM
of the large shoulders.
WoW Characters
 
Join Date: Jun 2008
Posts: 382
Enfeeble should show up on the combat log.

Here's my example:




My thoughts on this are:

A) A GM is pissed at me
B) There's some sort of unknown bug.

I recall when it happened and I was well over the 30% buffer for threat and i don't recall ever turning purple and glowy. So I'm guessing a bug of death is going around.
__________________
Tanks: We like it rough.
Reply With Quote
  #6  
Old 08-06-2008, 07:40 AM
Horacio's Avatar
Sponsor
 
Join Date: Aug 2007
Posts: 1,467
Blog Entries: 104
You must have crit him in his junk and he became enraged and squashed you. blizz thought it would be funny, first off, to be tanking him with your face in his crotch and then expanded on the implications of such a situation.

I've never seen this myself but I haven't tanked Prince but once in the past few months, preferring to run my mage through Kara instead. That's seriously messed up though.

Enfeeble is the most logical explanation but if you say you had plenty of threat, that's impossible. Still, it may be an error in how things are reported to the combat log. There are all kinds of quirks associated with it. /shrug
Reply With Quote
  #7  
Old 08-06-2008, 08:43 AM
kolben's Avatar
Heavy Hoof
WoW Characters
 
Join Date: Jul 2007
Location: Kuna, Idaho
Posts: 393
Being crit in the junk tends to make them go full on berserk

Get recount (pictured in Krashtork's post) and use the deaths view to find out.
You were probably lower than 40% and took a top-end crush, or some possibly what others have said. In ZA on a boss like Bear or Lynx it's usually because you took all of the cleave/Saber Lash. It's been a while since I did ZA, but I recall eating a Saber Lash
for ~17k once in my high avoidance gear when the pally tank had a lag spike going in. ... it happens

We have a druid that lives in the Netherlands and doesn't get to raid with us often.
I sorely miss her when she's not there, you can not die with the way that girl heals.

Last edited by kolben; 08-06-2008 at 09:03 AM.
Reply With Quote
  #8  
Old 08-06-2008, 10:22 AM
Alent's Avatar
Fuzzy 6d100 Druid
WoW Characters
 
Join Date: Dec 2007
Posts: 595
Blog Entries: 77
Frequently, combat logs are misordered. Take for example, the way the killing blow always shows up in your combat log:

So and so has killed mob
So and so hits mob for X damage.

I believe the same thing is happening with prince. He's slamming for some obscene amount of damage with his "flurry" attack (read: windfury) and the damage is spewing out AFTER you die.

So it looks something like

Krashtork has been killed by prince
Prince hits krashtork for ^8,590^ damage.
Prince hits Krashtork for ^8,900^ damage.

It's simple as that, really. >_>;
__________________
Reply With Quote
  #9  
Old 08-06-2008, 10:58 AM
Established Registrant
 
Join Date: Jan 2008
Location: Pennsylvania
Posts: 1,028
I don't think that enfeeble does show up in the combat log, actually. I know that I never saw it, but that was before 2.4 and it may have changed. Your post actually insinuates that he was enfeebled...the heal hit for 0, so he was at max HP. Either he was at 19k hp and died, or he was enfeebled and at 1hp (still max), and then died.

As for the pull right before Nalorekk, I'm stumped, but I don't think there's enough information posted to say it was a bug. We'd have to see the combat log to know for sure
Reply With Quote
  #10  
Old 08-06-2008, 11:45 AM
of the large shoulders.
WoW Characters
 
Join Date: Jun 2008
Posts: 382
If you look at the combat log it shows that i have 100% of 19184hp when getting healed for 0 (because i'm full) and then I die.

I honestly do not think it was enfeeble, and when i dug through the combat log i didn't see any lag hits after i died such as what Alent said. That's what i had thought at first but it certainly wasn't the case.

We were in Phase 3 with prince at around 18% when this occured, so the suggested

"Krashtork has been killed by prince
Prince hits krashtork for ^8,590^ damage.
Prince hits Krashtork for ^8,900^ damage."

Is unlikely due to the much slower rate of incoming damage which greatly lessens the chance that shield block would be down and i'd take crushes. Not to mention even if prince were to crush, 8k hits are highly unlikely.
__________________
Tanks: We like it rough.
Reply With Quote
  #11  
Old 08-06-2008, 11:56 AM
kolben's Avatar
Heavy Hoof
WoW Characters
 
Join Date: Jul 2007
Location: Kuna, Idaho
Posts: 393
To the OP

I'd like to know some things like what your typical latency is, what unit frames (if any) you use, what combat log mods you use (if any).

On the Amani Warbringers, that crunch armor debuff is fairly hardcore. Healers that are reacting to damage instead of proactive healing can help cause these kinds of deaths because the damage comes in bursts.
I'd really say you should also take a close look at what debuffs are on the mob, for example does it have Thunderclap and Demoralizing Shout/Roar on him at all times?
Reply With Quote
Reply

Bookmarks


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are On

World of Warcraft™ and Blizzard Entertainment® are all trademarks or registered trademarks of Blizzard Entertainment in the United States and/or other countries. These terms and all related materials, logos, and images are copyright © Blizzard Entertainment. This site is in no way associated with or endorsed by Blizzard Entertainment®.