Ooooh it *is* sexy.

Just one comment I find it hard to tell from the screenshot if this is valid or not:

There's plenty of fights where I just plain don't want to ever go over the main tank, even if I'm ranged dps and technically have tons of room. e.g. Gruul will slap me down on his way back to our main tank after a shatter if I'm over his threat (it happened Tuesday night.)

The visualization is awesome, but it might be nice to be able to either choose which you see (versus 100% or versus 130%) or have it some way integrated that both are there.


And. Oh yeah. It's sexy.

The bars update way too often. I don't need to see, when someone taunts, jumps to the top and then back. It's also distracting with the fast-changing bars. Could you please make it more subtle? There really is no need for realtime threat.

I actually enjoyed how dynamic the bars are, but that might be just because I like the way it looks less than it's actual functionality.

To unpollute this thread, I moved my response here:
http://www.wowace.com/forums/index.php?topic=6626.0

I'm getting an error when i run Omen:

\AddOns\Omen\Libs\ParserLib-3.0\Parser-3.0.lua:3`4:[string "local string_find = string.find; local type = type; return func..."]:1:malformed number near

Never mind, i just picked up the newest version and the error is gone. =)

Yes I know it says AtlasLoot, but before installing Omen/Threat, it worked just fine.

This is likely because Threat includes Babble-Boss, which had been updated to a newer version that incorrectly spells that mob name.

I have removed BabbleBoss from the embedded libs, only Threat and ParserLib3-0 is resident in libs because all other libs I had already.

But maybe AtlasLoot is still referring to the old name, quite possible.

Antiarc, I noticed last night that for most of the time my personal threat bar had no color, only rarely did it have the proper green class color. I'll get you the version number when I get home.

Doing some solo testing with comparisons to KTM, and Hunter pet aggro seems to be under reporting.

I was using a boar, and here is what I noticed:

White Damage Matched
Growl Matched
Bite Matched
Gore did not appear to apply in Omen, so threat was underestimated
Charge Matched

Charge + Growl is drastically lower than KTM:

Here is a screencap immediately after the charge

And a little further into the fight

Omen will often show me as significantly higher than my pet, however I do not pull aggro. (160% and higher at times) KTM is accurate on aggro switches, so it appears KTM is correct on threat values.

Unfortunately, I don't know how much threat Growl should generate, especially when affected by Charge, but it appears to be quite significant.

I hope this info helps!

EDIT: Ironically, after posting this threat matched for 3 more mobs using the same abilities. (Growl and Charge) Whatever it is, it is inconsistent.

Wow, that's a big discrepancy.

My hunter's level 29; what's the earliest I could tame a boar with charge and gore to test with? I'm using a generic wolf at the moment.

Hm. Looks like I'm missing a bit of pet stuff.

- Charge for boars. Unknown if this causes threat; I suspect it does. What threat per rank, and does it scale?
- Screech. Needs the threat for the debuff per rank. Does it scale?
- Thunderstomp. Same as above.

I got Demo Shout and Demo Roar in, though. As a bonus, it splits their threat value among the number of targets that ThreatLib knows about for the fight. Not perfectly accurate, but moreso than an assumption of "1".

Based on the screenshot, it would appear Threat/Omen isn't scaling growl with AP. It's pretty late here and while I saw the proper numbers in the Threat-1.0/ClassModules/Pet.lua file, it's apparently not getting properly implemented somewhere and I'm too tired to study the codebase to find it :-)

Anyway, the base threat of the top rank of growl is 664, the pet then followed with a 166 white damage hit, and voila, we've got 830.

However, ktm is following the formulae found at http://www.wowwiki.com/Growl_%28pet%29, which scales growl's threat with Pet AP after a certain threshold.

So, KTM is doing the calculation as:
664 + [(1279 - 734.2) * 5.7] = 3769.36 -- (1279 is the pet's AP, 734.2 is the PAP threshold at 70, and 5.7 is the threat per PAP over the threshold).

Not sure why the extra 166 hasn't been added in yet, but most likely, the SS just caught it before it updated.

Additionally, I don't believe that Charge itself has any threat (you can actually charge a neutral mob, but recall the pet before it growls/damages the mob, and it won't become hostile), but it's been speculated that the AP bonus it grants does affect the initial growl, substantially boosting its aggro. I've not seen any testing one way or the other, though it's something worth looking into.

Yesterday I did some arena matches and wanted to disable and fade out Omen for this, but wasn't successful. I 'standbyed' and toggled several times, rightclicked and pressed enable etc but it just didn't disappear.
Then I ignored it and simply kept on playing with the now non functional frame of Omen.

Later, after the arena, I went into an instance and wanted to re-enable Omen again, but was just as unsuccessful as before hiding it.
It just wouldn't accept any data, no matter what key I pressed / command I entered, and after showing the test bars, they wouldn't go away anymore.

A ReloadUI helped to make it work again, but I really felt quite stupid not being able to hide/enable it there. :S


Btw, the problem with the missing translation really seems to have been AtlasLoot.

Tested Omen/Threat for a Karazhan run yesterday and it worked very well for the majority of the evening.

I did have one weird incident though. On the big Arcane Protectors in the post-Curator trash Omen would show me as the only one on the list (I was tanking). Three or four others were using Omen and for other trash/bosses everyone was showing up fine (the non-Omen people showing with data from KTM). As soon as the Protector died everyone but me would show on the list for the Protector (I stupidly forgot to screenshot this after one died).

This was consistent on all (4?) Arcane Protectors, but I can't figure what could be different about this type of mob.

Versions used were Omen: 39058, Threat: 39053.



Screenshot is with the Protector half dead.

Well I remember I was able to charge low level mobs with my warrior alt to decrease my travelling time () without aggroing them, but it may have been changed in the last patch(es):
Maybe it's generating aggo now (if only 1), or it was just some sort of bugfix. Haven't tested it.

Also everything could be different for the Boar Charge of course.
Boar Charge seems to add the charge effect (1s stun), Apply Aura: Mod Melee Attack Power by 550 and another Boar Charge effect with Apply Aura: Root.

As the Charge: Stun mechanic didn't necessarily mean aggro of a mob, maybe the Rooting or AP Aura does?

This issue has been discussed earlier in the thread; everyone's aware that it's impossible to get complete accuracy. C'est la vie. It'll still be accurate on uniquely-named targets, which is still valuable.

There are obviously going to be limitations like the situation you described. I think the aim here is to A) Be more resource friendly than KTM B) Track threat on multiple mobs in scenarios where it is possible.

I don't think the authors really need to prove anything to you. What is your alternative? A mod that doesn't even realistically attempt to track threat on multiple mobs with any accuracy?

I just tested it on the yellow moths in Terokkar, and Boar Charge still doesn't put you in combat as long as you recall him before he damages or growls the mob. Additionally, there is no stun associated with Boar Charge, just the root and the AP buff.

Apologies for replying to myself a bit here, but after playing around with it a bit more, the AP bonus from Boar Charge is definitely being included in the threat calculation for growl. My boar has an unbuffed AP of 560 (low I know, but it's an alt :P) which is under the threshold for rank 8 growl, so when I just had him run up to a target and growl, it was generating the min threat for rank 8 (664). I did a few trials using ktm to confirm that I was pulling aggro at 110% in melee range (hitting him unarmed to keep the precision higher) and I was.

I then tried having him charge+growl for a few tries, and with the extra 580 AP, it was putting my boar at 1141 AP when he growled. Sure enough, ktm showed him just below 3k (or just above if he managed a hit before i could stop him) and I was pulling aggro in melee at ~3300.

So it looks like charge itself doesn't have an aggro component itself, but if the pet growls before it uses up the AP buff, this would greatly increase the effectiveness of that growl.

Also, Corinthian, I assume your pet normally has about 700AP and that SS you posted is still showing the buffed AP from charge?

(I apologize if I missed the answer to this already skimmed through 17 pages but may have missed it with the search as well).

One of the big questions our healers have that they have a person targeted through most of the fight showing their relative threat in regards to that target, rather then a global overall threat which they need to see if they have suddenly hammered the GH too often and there's now some big nasty coming to rip their face off. Is this an inherent limitation to Omen or is this taken into account that when you have a player character selected it defaults to Global threat for them?

Not being able to see the overall global threat to healers at the start of a fight is concerning to them.

(Sorry if this already been discussed before)

I'm testing out Omen in a heroic Arc run, and for some reason, only the casters of my party are showing. I've tried standing right beside the rogue/warrior, but they still won't show up.

It's baffling me because in my Kara run earlier, everyone was showing up in the display, and I know for a fact that the MT didn't have Omen.