I don't think so, unless Shadow Affinity applies to mana gains from Vampiric Touch (which I should test!). I've done some heavy priest testing in the past few days, and I'm nearly certain that it's VT that's causing the threat over-reporting.

Don't forget that KTM only broadcasts global threat unless a specific target is set for it. So if your MT was tanking channelers before he went to Mag and the KTM target was not set to Mag, the threat broadcasted for him will be for both the channelers + Mag whereas the rogues using Omen will only see the threat they are generating on Mag.

Right. And since you can't target Magtheridon to set the master target until he's unbanished, this is a problem. KTM automatically resets threat when Magtheridon is unbanished in recent versions, but an older version of KTM wouldn't, I suspect. Do you know what version the tank was running?

(We had a similar situation - tank running KTM, myself and the other rogue running Omen, but threat seemed right for us and we didn't have problems with aggro)

I have a request to make. It was a feature that used to exists, but seems to have vanished with the new version (updated it yesterday). Is it possible to remove columns and/or move them around ? The default settings have the 3 right-aligned bars numeric values overlap each others in raids, which makes everything hard to read.

EDIT: And unfortunately I have to report that I did get the 'messed up player colors' issue yesterday

It's under the skins menu, and still there. Look for the columns options.

A lot of things got moved to the skins menu - you can edit a skin, save it, and switch between skins as you like.

What time did you get the colors problem? I made a check-in at about 12:30 AM PST that should address them.

Correct.

Its possible. My usual friend isn't online so i can't test it and im resto spec atm. which means i got intensity.

How i would do it.
1) Find 2 druids, one without intensity
2) One druid bodypulls a mob in bear (make sure Furor doesn't interfere, go bear before the pull)
3) Second druid casts a rank 1 Rejuv on him. Rank 1 rejuv heals for 8 every 3 second in non-healer gear. If you cancel the buff after 16 healing (6 seconsd/2 ticks) it should be a good benchmark. Mob will go to the healer at first tick.
4) Blow Enrage and watch the result

If inaccurate, I can't say _increasing_ the reduction would be more accurate. As it stands, having killed VR for 3 months now, we have many -- shadowpriests -- that ride the threat line. 75% had accurate switches, and 70% would have certainly had said players with aggro over the tank 2nd in line. As well, I just don't see Blizzard switching to a more granular percentage, which is, in part, why we had expected the skill to be either Broodlord or Onyxia style.

Though, we don't run Omen/Threat, so I can't speak for inaccuracies there.

Well, I'll try a revert back to 25% and see what people experience with it.

I'm adding a command that will let a raid leader override various values for the raid group, too, so between attempts the raid leader could futz with the knockback reduction to find a percentage that gives accurate values.

My test was to have a druid bodypull a mob, hit Enrage, cancel after X ticks, and then have a level 20 mage melee the mob till they pulled aggro. The mage melees for 1-2 at a time, so it's pretty easy to get accurate readings. Threat was definitely fluctuating depending on when I cancelled enrage.

It was my fault, actually. I rearranged the menu, but didn't change the path to look up whether that variable was set or not. Sorry about that!

When setting the bars to "Grow Upwards" it works fine, but when the meter resets following a fight, it still uses the top as it's anchor. (Either that or I'm going nuts... I can't explain why the window is higher than it was.)

It was actually overestimating tank threat. And quite significantly. Hence I think it's more than a 30% cut, but I'll try to keep a closer eye on it next time.

If the tank's threat was over-estimated, and the tank was running KTM, there's not much we can do about that, I'm afraid.

Edit: Wait, this was Void Reaver, right? Heh, nevermind, wrong issue. Please keep an eye on it.

If you'd like, I just added a (untested) feature to ThreatLib that will let you set raid-wide variables for some fights to help debug values like that.

/script AceLibrary("Threat-1.0"):SetNPCModuleValue("VoidReaverKnockbackMultiplier", 0.6)

would set the multiplier to 60%, so it'd calculate the reduction at 40%. Play with that between tries until you find something that works, assuming that everyone's update to today's latest revision.

Void Reaver threat is nutty as far as what my guild has experienced. I'd like to think that I really am a crazy-awesome tank, but something just dosen't jive for me. I held aggro through 3 knockbacks, on the fourth, he went to another tank and I pulled aggro off of him before he got knocked back.

So either VR's aggro mechanics aren't normal, or I can pump out like, 2k threat per second with the rage from my white attacks. I definately feel that a 30% or even 25% reduction in threat is a bit steep. Also, even after being knocked back 4 times (and eventually losing aggro to another tank) ranged dps never pulled aggro. We specifically have all ranged DPS dump without regard for what their threat meter says because we've NEVER had a ranged DPS pull aggro on VR. Possibly because of arcane orbs and DPS downtime, but we have some crazy mages and locks that should be able to pull after 4 bloody knockbacks.

bleh, just my experience, hopefully I've said something in there that'll help you =p

just a note, I was running KTM and omen, they both had ranged dps over the tanks by 30% and both had me far under other tanks while still retaining aggro.

I had a Paladin of ours who often specs Protection for running Heroics ask today if there was a way to have Omen display all of the targets it is tracking at once. I searched around the menus and didn't see one. Is it possible?

the members in my guild that updated today are not getting any threat at all showing up

There isn't, but if you use something like Aloft (nameplate replacement mod), it puts threat data on the nameplates, which can be extremely useful for a tank. I believe that ckknight's working on a new tooltip mod called CowTip that will be integrating threat data, as well.

A-ha! I think that will work dandy. I did see the Threat feature in Aloft but I didn't put 2 and 2 together.

Thanks for all the work you're putting in.

a few questions/ideas.

Questions:

1. Can addons create concrete output files, meaning, can they create a .txt somewhere.

2 a. Is there a way to enable certain things that are normally invisible to the combat log (sunder when already stacked to 5) yet still generate threat, to be included in the combat log.

2 b. Do all combat log messages have a target and source. Meaning, is there ever a time where it's just "Mob1 is afflicted by Spell" or is it always "Mob2 is afflicted by Player's Spell"

Idea

if 1 is true: create an addon that tracks everything in the combat log with time-stamps, as well as a separate timestamped output of everyone in Omen's threat list for every mob, in a sort of tabular format, rows being seconds, columns being people, and each set being a mob

if 1 is not true and 2 a/b are true, could you reverse engineer a combat log and discover relative threat values? Meaning, you see a combat log and you see RaidMobA hits TankA for X damage then later you see RaidMobA hits MageB for Y damage you'll know that either the mob does a random charge-type thing (which you could search for and disregard) or they pulled aggro.

depending on either version, you could then look up each player's talent spec for relative -threat and +threat talents to derive the final threat value of the tank, and the threat that the dps had over the tank to arrive at a complete threat model for that point in time. It would take a while, but it would definately help to narrow down where some of these discrepancies are coming from.

if 1 and 2 are false, well, nevermind then =/

1. Kinda, you create a saved variable file and can parse that
2a. Not in a way that wouldn't cause all sorts of other issues plus you would only have your invisible messages
2b. Its always Mob1 is afflicted by Spell we never find out who its afflicted by till it ticks. Thats one of the major reasons you can't figure out aggro for others.