hmm, here's a weird idea: maybe seal of light has a second, invisible debuff that prevents it from getting a bonus from +healing, and that debuff can get knocked off

wouldn't really explain how someone saw it when soloing, though

No, then it wouldn't just be Unstable Affliction that did this.

Maybe there's some issue with that dispell damage?
Can't see how the simple DoT would affect Judgement of Light.

I really have no idea either, but the evidence is compelling....

Theory:
Unstable Affliction has a second, invisible, undispellable debuff that monitors the primary one and inflicts the dispel damage+silence when it is dispelled.

This second debuff uses the same 'deal damage on specific action' function that judgement of light uses (with JoL using negative values for healing). Somehow, both of these debuffs being on at the same times creates some sort of conflict and does one of two things:
a) somehow changes JoL to stop ignoring +healing (less likely)
b) Judgement of Light somehow takes the +damage coefficient from UA and adds it to itself. (more likely)


Now they probably discovered this problem and added someway for this to correct itself, which is why most of the time we only see it for a couple seconds.

What I think what we need is to have raw numbers of the following:

How much Seal of Light heals player x for before Unstable Affliction.
How much Seal of Light heals player x after Unstable Affliction.
And maybe any amounts of +dmg the caster has and +healing player x has and any talents effecting the healing on him. (might effect things worth seeing)

With these numbers could start to maybe throw them together and try figure it out.

Edit: Below (no point making a new post) Yeah I didn't think of that. That should prove whether it is or isn't affected by caster/player x +dmg/healing.

Wasn't somenoe earlier in the thread stating that this used to happen in naxx? Specificly I mean pre 2.0, before UA entered the picture?

I realize there was raid time between 2.0 and TBC, so it could have well been in that window, but it's worth asking if anyone recalls something like this happening before (perhaps there's another debuff that functions in such a fashion?).

I realize the odds of this being logged by someone are more or less nil way back when, but worth asking about.

I never noticed it at all until we got 41 point talents.

It was when 2.0 came out that people first started posting about this.

A quick check over at thottbot returned the following ( http://www.thottbot.com/s27162 )

Where the Judgement of Light Intermediate links to:

This to me seems to fuel the theory of a knocked of buff, but does not explain why its only unstable affliction triggering it.

Am I the only one that spotted this?

Saw that, figured someone was named Thunderfury, but an Armory search has nobody of that name on that server. O_o

Have you considered that it might just be a hunter's pet? Why they would name it "Thunderfury" is beyond me though.

Thunderfury is indeed a hunter pet

It's resetting to the normal value when the Paladin refreshes Judgement of Light.
This is not immediately obvious from the logs since reapplying a debuff doesn't trigger a combat log entry. But as the first judgement lasts for 1:06, it was clearly being refreshed.

Additionally, Judgement of Light was only being actively maintained for the first minute of the fight, and that is the only period where you see the value reset back to the 115 base.
During the rest of the fight, once it is boosted by UA, it remains at the higher value until it expires.

And you can also see from logs that between the two warlocks casting UA, Dirtyc boosts the healing value to the 240 range, and Gilliam boosts it into the 340s. And there are periods where it is even higher, presumably when the warlock had activated a trinket. A quick glance at the armory confirms that Gilliam has more damage & healing gear.

So, it's definitely getting a bonus based on the warlock's gear, probably some fraction of their bonus healing, hard to say without knowing what buffs they had at the time.

Thunderfury is a wind serpent that breathes lightning.

It's awesome that this has been theorycrafted, i've been curious about why it was healing for so much for months, but didn't want to attract attention from Blizzard - they tend to be very hot on fixing bugs that benefit players.

Here's one odd idea? What's the pet scaling for warlocks? How much of the +damage gets applied to the pet?

Maybe some wacky bug where putting UA on a target slips the JoL into pet status for the warlock, and so it suddenly gets spellpower?

I personally still remember the Paladins on Kodos bug with some fondness.

But it's certainly an interesting interaction.

What was your talent spec when you were seeing these heals over 115 while soloing? What was your total amount of +healing gear at the time? What debuffs were you putting on the mob?

The thing is, he didn't see any over 115 while soloing. That's why his sentence had the word 'don't' in there, which when fully written means do not.

Although that one was at least explicable. I recall it was said that someone made a function call the wrong spell number (which just happened to be a "ride kodo" spell). I was pretty suspicious that that was deliberate, too, since of all the spells to accidentally call, it was the one with maximum humour.