Please be aware that the combatlog is often very much out of order and not 100% accurate. Sometimes events will be missing and such.

If I had to guess what is happening with flame shock the SPELL_AURA_REMOVED event is happening client side (it knows about the buff and the server tells the client the duration so it knows when it should expire) so it happens the ms it should. DAMAGE events all happen server side however and the client doesn't get notified about the damage happening until it gets the notification from the server. Thus you can see the damage event after the removed event if your server latency is greater than the time that it ticked before expiring. Same thing goes with Lava Surge, the client knows when flame shock expires, but it doesn't know when a Lava Surge proc occurs until it is told by the server.

From what you have posted, I don't see any behavioral bug. This can probably be called a combatlog bug, but it's just the way it works for everything, and nothing specific to flame shock. As Blizzard posted in a recent Q&A, if they wanted to synchronize the client events with the server events and have the events in order, it would break a lot of stuff. At a minimum from my understanding of the issue it would delay when addons receive events that are currently handled client side.

To put it in Flame Shock terms if you had a PowerAura showing when you had flame shock up, currently the addon will be notified right when it expires so that you can reapply it immediately. If they had to fix the out of order combatlog, the addon would not get notified about it expiring until the server could send an event, meaning you wouldn't get notified about your flame shock expiring until your server latency after it happened.

Healing Rain's first instant tick and any additional ticks granted by Haste are currently (4.1) not affected by Focused Insight.

Wind Shear still misses (despite patch notes). Edit: This seems to be fixed by the April 29th hotfix, WoL is not showing any misses as resto spec.

Healing Rain and Earthquake (and all similarly targeted abilities for other classes, afaik) targeting reticule can bug and change sizes or disappear. It can sometimes take several casts to get one to go off.
Edit: "/cast !Healing Rain" macro does not help with this issue at all for me.
Edit2: Patch 4.1.0a fixes this issue.

Can confirm, on our HC Halfus attempts I was in charge of interrupting Nova, as enhancement shaman. Due to missing some fractions of the spell hit cap, I missed one interrupt. World of Logs confirms this.

Don't know if this link will come out correct, but I'll try:

World of Logs - Real Time Raid Analysis

EDIT: Attempts were on Wednesday, 27.04.10

Someone posted in the Resto thread that using a /cast !Healing Rain macro fixes some of these issues. I use that macro, and have not noticed the targeting reticle changing size, so I`d advise everyone to try it.

I've still had problems casting HR, though, but I believe it's due to the decreased lag with the bandwidth un-throttling. It`s thrown my spell queue timing off.

Healing Rain procs the stacking spirit buff from DMC: Tsunami but not Jar of Ancient Remedies.

I found this bug for rly long time, it wasn't big problem for me, but sometimes it's getting annoying.

If u get kill shot by thunderstorm, sometimes(*) u still knock back the target, and he dies far away from you. When u go to loot that mob, it says "its too far away" so u cant loot that mob.

And in underwater, if u get killshot by thunderstorm, and if u knock back the target (*) target starts the fall down till it hits the bottom of the sea, lake etc. Its annoying too, if u fight with naga near the surface, and u need to dive for loot. Still, if u die for that loot, it says "its too far away" again.


* Some kill shots by thunderstorm dont throw your enemy back, its kinda random or im missing something.


Sorry for bad english, wanted to share.

I have confirmation from a blizz CSR that the developers are aware of a bug currently with searing totem that prevents it from attacking its target consistently when first dropped.