If anything I think the threat on landing is a LOT closer to the landing than before.

As the MT of the encounter I have found it significantly easier to snap agro than it was prepatch.

Zanthor: Perhaps the threat wipe just happens later, so there's less global threat buildup, making it easier on the tank?

Every kill I've been in since 2.1 had a hunter MDing him onto the tank, so I really can't contribute my experience.

Heh, you can't do any per pixel operations. The only thing we are allowed to do with textures is manipulate texture coordinates or set their bounds. Can't even set masks :-/

Also all objects in WoW have to be axis aligned rectangles! Though that one makes sense really simplifies their widget positioning system.

whats the point in displaying the threat in kilo but with 2 decimal places? its kinda unnecessary...

For the most part, it's for debugging against KTM. If it bugs people I can knock it down to 1 decimal place or something.

Al'ar: Does he do a threat wipe at the end of phase 1? #wowace is currently split on the issue, and I've yet to see the encounter myself.

He does not.

Yeah I always unclick salv stage 1, stand it a designated spot, and have tanks taunt before it gets to me, then shatter. Everyone else can go absolutely ape shit stage 2 with no worry of pulling agro.

I'm not sure if this has been asked yet, but does Omen synchronize with KTM? Reason I'm asking is I'm not sure if guild wants to swap out their threat mod as a whole, but I'd like to give it shot to ease up some resources.

If I go to solely Omen, will people still be able to see my threat accurately via KTM and visa versa?

As far as i know you see them but they dont see you, but as long as you keep an eye on your aggro and you arent MT you should be fine.

Playing on my shadow priest I'm getting rediculously low threat values like 7 TPS when i'm doing 600+ DPS

What's your update frequency set to?

sp00n - that likely means you were running a multi-lingual group without a translator for your target locale in the party. I'll see what I can do to address that.

In other news...



I'm too tired to explain what it is and what it does, but it's sexy. I'll elaborate tomorrow.

Let me guess - the green bit is your current aggro, the full bar is aggro gain, and the orange shade is your expected aggro based on average/max damage skills? Way cool if I'm right.

Is there an option to set the max to 2nd or 3rd on the list for those fights where u need to keep below both MT and OTs?

Time until aggro / relative TPS wrt Aggro holder ?

Antiarc (and everyone who works on Threatlib), it's almost frightening how fast this project moves. 2 weeks ago there were postings about what's bad with KTM and now we already have this so far. Kudos to you all !

Omen r38987
Threat r39053

When I leave combat my threat bar (and all "test bars" if I have them shown) extend infinitely off the right side.



This has happened consistently since last night around 6pm CST and I've run the ace updater a few times since.

The class colored bar is your current threat, the first red bar is the threat of the person you're comparing to, the second red bar is the point at which you'd pull aggro. (You can eyeball this fairly easily by comparing the length of each of the bars in the Omen window)
The leftmost text is your current threat expressed in a percentage of who you are comparing to, the rightmost text is the TPS difference between your own TPS, and the TPS you'd need to maintain your exact current relative threat. (Only the rightmost text part is an assumption on my part)

I'd assume all colors are configurable?

It really speaks volumes about how fed up people were with KTM not being responsive to new UI suggestions or requests for changes.

Same thing happening for me (priest) and another officer in our guild (enh shaman). Doesn't seem to be class specific.

Found a couple of bugs doing some testing earlier, not sure if any are intended or repeat reports, but thought I'd list them anyway.


-Right clicking on a bar then clicking "Pullout Threat Bar" allows you to pull out a comparison bar for anything, including yourself and the *Aggro Gain* bar.

-Demoralizing Roar doesn't seem to add any threat.

-Threat doesn't seem to show to other people unless you do some damage on the target. Here's what we did to reproduce this: Druid friend face pulls a mob, gets damaged, heals himself. He now sees his own threat, but I do not see any threat on the target. If I hit the target, I now have threat (and he can now see both his threat and my threat), but I still do not see his threat. If he does any damage to the target (e.g., melee) I can now see all the healing threat he previously had. We also experienced the same thing with threat generated from rage-generation (bear using Enrage).

-If I build threat on a target, leave party, then join again Omen will show 0 threat on the target until I hit it again, then it will show all the previous threat I had.

-If I change the width of Omen by dragging the bottom right it will reset to the default width when I mouseover the "Width" option in the right-click menu.

-In our small-scale testing (1-2 hits from each) bear agro seemed wonky and innacurate. After a bit of testing we figured out what it was. Heals from Improved Leader of the Pack seem to be giving the person that crit (and got healed from it) threat, when it shouldn't be. I am 90% certain this is what is happening. We did some good testing where I got healed for 500 from Imp. Leader of the Pack (giving me an extra ~250 threat) and I pulled agro about 250 threat late. When we clicked off Leader of the Pack everything was very accurate.

-Attacking something when not in combat makes the threat from the initial ability that puts you in combat very buggy. When we tested by pulling with Fearie Fire, the initial Fearie Fire did not give any threat, however subsequent Fearie Fires gave threat fine. When we face-pulled to be put in combat and then Fearie Fired, the threat worked fine (even with the initial Fearie Fire). When we tested this with Maul (by attacking a non-aggressive mob, where Maul was the ability that entered us into combat) it seemed very weird. We finally figured out that the initial Maul was not adding the static threat that Maul has now (since 2.0.3... 322 for rank 8). For example, entering combat with a 505 dmg Maul showed 505*1.45=732 threat, where it really should have shown (505+322)*1.45=1199 threat. Again, when we face pulled and then Mauled, it worked fine.

-Timelapse Shard does not show a reduction in threat. It reduces threat by 901 (before modifiers) and in the combat log it looks like this "You soothe <target>".

This was tested with Omen r39058 and Threat-1.0 r39053

Indeed, I'm running the English client on a German server, was the only one using Omen and had receive data from KTM enabled.

This is the error message:
Babble-Boss is up to date, DewDropLib is up to date.
It fires up when I log into the game, and not only after I've joined a raid.

I can see where that error comes from, it's supposed to be Gatewatcher Gyro-Kill, not Gatekeeper Gyro-Kill. Also are you sure the error is coming from Threat-1.0? It appears the error is coming from AtlasLoot.

In a Kharazan raid last night, the bar for my character wasn't drawing (there might have been one sliver of color on the far left, but it was hard to tell). Other threat bars were drawing correctly. Omen did show data and a chart position for my character, which seemed consistent with the data KTM was showing, but the bar wasn't drawing.

I looked for options that might be causing this, but didn't see anything obvious.