Warlock Bugs - Page 19

whi · 05/09/09, 11:05 AM

Its not that simple im afraid. I never had any problems with demonic pact in 25 mans(or I or any other caster never noticed them), i do in 10s though. Luckily, clicking off mass spirit buff and asking for a single one for myself seems to work for me. As can be seen here:

Wow Web Stats
Wow Web Stats

Although im looking through hodir tries, which im sure i clicked spirit of as we were having fun with the hardmode and it seems that it totally fails to proc? Same on freya... Some kind of wws error i guess as it was fine a week ago.

Scrufola · 05/11/09, 6:40 PM

The Immolate bug is always explained with the fact that you cannot renew Immolate if a stronger Immolate is already on the target. I don't think that that is always the reason.

I was doing the tournament daily today and that happened:

I have enough hit for a normal Icecrown mob. I killed a Scourge War Engineer and switched to the next Scourge War Engineer (which was a fresh mob and therefore was not already affected by Immolate). The interesting lines are:

Scourge War Engineer is afflicted by Scrufola's Immolate.
Scrufola's Immolate dissipates from Scourge War Engineer.
Scrufola's Immolate hits Scourge War Engineer for 1693 Fire.

The Immolate hits.
The mob is afflicted by Immolate.
The Immolate effect dissipates before even the initial direct damage is done.

I do use the glyph of Conflagrate, Life Tap and Incinerate. I'm skilled 3/13/55 as you can see in my profile.
I did not cast Conflagrate after Immolate because that's not possible with my latency or the latency of my server. I always cast a Chaos Bolt or Incinerate after the Immolate. Therefore it cannot be a malfunction of the Conflagrate glyph. (Also, you don't see a Conflagrate in the combat log.)

Lephturn · 05/12/09, 1:59 PM

Is it possible the dissipate message is for the dead one? It would be much easier to tell if you had 2 different types of mobs, because they are the same exact mob name, lag may just mean that the "dissipate" message finally reached you based on the first one that you killed.

Scrufola · 05/12/09, 3:32 PM

Originally Posted by Lephturn

Is it possible the dissipate message is for the dead one? It would be much easier to tell if you had 2 different types of mobs, because they are the same exact mob name, lag may just mean that the "dissipate" message finally reached you based on the first one that you killed.

I cannot say for sure that the message was from this mob but I checked the combat log because I could not cast conflagrate because the Immolate did not stick to the mob. The "bug" was definitely there.

Warlocomotif · 05/14/09, 12:59 PM

Here's another interesting thing that may or may not be related; you can have divine spirit rank 5 and 6 at the same time. The effect (+spirit) doesn't stack, however this does suggest that there's something out of whack with the debuff category of the spirit buff.

Turboteckel · 05/16/09, 8:45 AM

Has anyone here ever noticed Corruption falling off too fast? I've seen it drop off the target around the last 3-2 seconds of the debuff a few times now. Surely the end of the last second has the last tick of it?

Paroxys · 05/17/09, 12:40 AM

This has been answered before - because of the way Haunt refreshes Corruption, it's possible for the last tick of your Corruption to be at 2.9sec remaining on the debuff. When this happens, the Corruption debuff drops off since it's not going to deal any more damage for the remaining duration.

Scrufola · 05/21/09, 6:17 PM

That's probably known but just to summarize to make a clearer description of the bug:

The Imp can buff it's fire shield on any raid member but itself.
If the fire shield is set to autocast, the imp automatically casts the shield on everybody upon taking damage (at least upon taking melee damage).
The casting of the fire shield has a hinger priority than the casting of its firebolt.

Here comes the bug:

If the fire shield is set to autocast, the imp casts it only on party members and raid members in the same party but not on raid members in another party. It is possible to cast a fire shield on raid members in another party but the imp doesn't do it automatically.

I verified this with a feral druid. When the druid was in another group, the imp did not cast the fire shield. As soon as I moved the druid in my group (in combat), the imp did cast the shield.

I have a European account, if someone with a US account thinks this bug is worth reporting, please go ahead.

______________________________________________________________________

Originally Posted by Lephturn

Is it possible the dissipate message is for the dead one? It would be much easier to tell if you had 2 different types of mobs, because they are the same exact mob name, lag may just mean that the "dissipate" message finally reached you based on the first one that you killed.

I had the same thing happen while killing the same mobs. And of course, it happened while killing two of the same kind of mob in a row. This time, there are 6 replenishment ticks between the death of the first mob and the bug on the next one. Could still be a combat log lag error. (But at that time, my latency was great and the server in a healthy condition. I could not feel any server lag.)

And, I noticed something else. I did some tests on the "Ranged Target" target dummy in icecrown. Immolate does stick on the melee dummy but not on the ranged dummy.

Now, I wouldn't care, because dummy are irrelevant. But the interesting thing is: The combat log looks exactly the same as the combat log of the other mob.

Last, the Scourge War Engineer, the mob I noticed the bug now twice, doesn't drop any loot. But in most cases, the Immolate does stick on the Engineer but never on the Ranged Target dummy.

Evyle · 05/23/09, 1:54 AM

I am using mainly a 0/13/58 spec (moved 2 points but got the basics). I am seeing a horrible crit rate to my Conflag... well not horrible but its equal to my other abilities. I have 5/5 Fire and Brimstone that is susposed to give me +25% crit to the conflag. Last week I was pushing 65% crit of so with conflag and this week closer to 40%. Anyone else seen a problem with low conflag crit rate?

Bergtau · 05/23/09, 10:15 PM

Originally Posted by Evyle

I am using mainly a 0/13/58 spec (moved 2 points but got the basics). I am seeing a horrible crit rate to my Conflag... well not horrible but its equal to my other abilities. I have 5/5 Fire and Brimstone that is susposed to give me +25% crit to the conflag. Last week I was pushing 65% crit of so with conflag and this week closer to 40%. Anyone else seen a problem with low conflag crit rate?

Likely just RNG, if you really think that it's a bug, go test it on the dummies in a city and get a parse of a large sample of Conflags.

krosz · 05/25/09, 5:16 AM

Originally Posted by Biondo

my imp suddenly just stopped auto attacking, he just goes into phaseshift and does nothing even when i shift it to aggressive mode. anyone has this problem?

Just in three situations: 1. Target is immune to fire. 2. Firebolt is off autocast. 3. Terrain glitch keeps it out of range

epiccollision · 05/26/09, 10:10 AM

Originally Posted by Evyle

I am using mainly a 0/13/58 spec (moved 2 points but got the basics). I am seeing a horrible crit rate to my Conflag... well not horrible but its equal to my other abilities. I have 5/5 Fire and Brimstone that is susposed to give me +25% crit to the conflag. Last week I was pushing 65% crit of so with conflag and this week closer to 40%. Anyone else seen a problem with low conflag crit rate?

I seem to be having a similar problem but with chaos bolt, raid buffed i'm well into 30% crit rate(disregarding empowered imp and any other proc buffs) but for an entire 10 man ulduar run CB only had a 22% crit rate on over 100 casts

maybe i'm seeing something that isn;t there but its has seemed kinda low ever since 3.1.2

http://wowwebstats.com/f2t6o3ekuhivc?a=x3000000034dbbec

Indaria · 05/26/09, 11:29 AM

I could not find it mentioned in the thread while using the search function, so here goes:

Demonic circle: Teleport has a tendency to not work on the General Vezax encounter. I've heard one way to avoid the bug is to make sure not to put up your circle prior to engaging, and suggestions about the 'rough' terrain in the middle causing some 'evade' like behaviour (ie, porting would put you below ground level, and thus fall through the floor).

I also had this behaviour happen once on Freya, presumably due to placing circle on an unfortunate spot, but I haven't been able to reproduce it on this encounter.

Darkmantle · 05/26/09, 8:59 PM

Originally Posted by epiccollision

I seem to be having a similar problem but with chaos bolt, raid buffed i'm well into 30% crit rate(disregarding empowered imp and any other proc buffs) but for an entire 10 man ulduar run CB only had a 22% crit rate on over 100 casts

maybe i'm seeing something that isn;t there but its has seemed kinda low ever since 3.1.2

Wow Web Stats

Looking at all the boss fights which is the most likely place for you to have full raid buffs your incinerate has 23% crit and your chaosbolt 20% crit. The t7 2 set bonus Demonic soul is presumably the reason for the higher crit rate on incinerate. Immolate at 27% and conflagrate at 53% are both closer to what you would expect with 30% raid buffed.

However looking at your buffs your uptime on Elemental Oath is extremely low, you only had it for 2 minutes and 52 seconds for all boss fights compared to 16 minutes 21 seconds for lightweave or 3 minutes 4 seconds for empowered imp. Your mage is also arcane and you don't have imp shadowbolt so there isn't any 5% crit debuff on the mob either.

My main guess would be you were out of range of your raid crit buffs most of the time and that is why you have such low crit overall. I'm not 100% sure but I think the mages demonstrated that bosses are also crit less by spells just like melee crit is affected. Looking closer your shaman was switching from elemental to resto between fights so that probably accounts for the low elemental oath uptime.

So overall I don't think there is a strong case that chaosbolt is bugged. Looking at my own logs World of Logs - Real Time Raid Analysis for a similar 10 man group I have a similar crit range for most of it.

Bergtau · 06/04/09, 3:46 PM

So Haunt seems to be buggy as all hell.

Bugs I've noticed:

1 - When you cast Haunt on a mob, sometimes you get the heal instantly, rather than having to wait for the duration to end.
2 - When you cast Haunt on a mob and don't get bug #1, the mob will stop to 'cast' the Haunt at you briefly if it's moving. Useful for kiting.
3 - Only ever had this happen once that I noticed and was too stupid to get a screenshot, but Haunt sometimes heals twice. When I noticed it, it was when the Haunt was the killing blow on a mob, so it might have been a mixture of what Haunt is supposed to do, and bug #1. I know that it was the same Haunt that caused it because I had not cast any Haunts recently, and it was the exact same amount healed. (already posted by somebody else, so leaving this in to confirm the bug is there)