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?

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.

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.

______________________________________________________________________

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.

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.

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

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.

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.

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)

If you cast a haunt on a target with haunt already, you get it back. That's probably #1 unless you are seeing this on the first haunt. #3 is just the same thing except the mob is also dying. You get the first haunt heal that just expired and the second one simultaneously since 2 haunts are returning to you.

Both Haunts for #1 and #3 are the first Haunts cast, it was not renewing any debuff.

felguard is still coming back at half health after dismount into battle.

Yes, my Imp did not attack for an entire day despite deleting my WTF folder and re-summoning several times. As I was raiding both Naxx 10 and in an Uld 25 that day I put in a ticket. When it was finally answered the GM checked around and told me that several warlocks had been reporting the same issue and that Blizzard was looking into the matter. Her suggestion for the time being was to completely wipe my UI (delete my cache and Interface folders as well as the WTF folder). This fixed the problem.

One of the most obvious bugs out there is the drain soul/life/mana and health funnel visual glitch. Unlike other channeled spells, for example arcane missiles, when any of these spells end they simply disappear from midair, rather than finishing their course towards the target. I assume this is just lazy coding on Blizzard's part, but I find it obscenely ugly and cannot think of a single other spell that behaves the same way.

Being a drain, you would think that they would finish their course toward the character not toward the target mob. Regardless, this isn't really a bug, just an aesthetic annoyance.

You sure autocast was enabled on his firebolt?

It seems that warlock and hunter pets will no longer attack the heart on XT (albeit only some of the time).

I finally got a screenshot of this issue with Immolate that I am having.
Fairly often I am not able to use Conflagrate even though Immolate is on the target.

Link: http://img24.imageshack.us/img24/4977/immolate.png

I know I am in the middle of an Incinerate cast which may look like it causes the message "You can't do that yet".
But the screenshot was taken before i started to cast Incinerate and i chose to move on with my
rotation, just to have that clear. The message for trying to cast a spell during a cast is "Spell is not ready yet."
I can't say that I know what is causing this issue. Is it possible that an addon is causing this or
is it just an another annoying bug?

Editet the link, did not work before.

If you have enough haste, you will cast immolate but still have ~0.2 seconds before the GC expires and you can conflag - this is especially noticeable at the start of a fight. You only need 15% haste or so for this to be the case, so it's easy to do.

I just start fights with Immo > Incin > Conflag instead of Immo > Conflag

Interesting bug on Mimiron: while tanking the head, my imp was able to attack the head just fine. In phase 4 however, the imp would not attack the head or middle, only the base.

Well, if you look closely, it doesnt take 7 seconds to understand that Immolate is on the target.
On my DoT timer you can see that it has been on the target for roughly 7 seconds.

You might need to make him passive, then manually attack firebolt on the head and switch to defensive.
That is usually how I do it and it works for me.