I've done about a million Misdirections in the past two days and we haven't seen anything like that.

That said, it's not impossible. I'd imagine MD is kind of a pain in the ass to model correctly...

I'm still having issues with Omen stalling (quite the right word for it) and being unable to open my raid window in combat / the character window showing in the middle of the screen.
I suspect it not to be a direct issue with Omen itself but rather with another addon tainting whatever frame is causing this and at the same time stopping Omen/Threat from working correctly.

I haven't come around updating all of my addons yet (maybe today), so couldn't figure out if that resolves the problem.
For me, when that bug happens, threat display just stops for everybody but me. Maybe your druid was affected by the same thing and therefore not reporting his threat to the other members.

Not according to my testing, though the threat from the reflected damage appears to be modified by stance: http://elitistjerks.com/showthread.p...077#post373077

I'm having a problem when soloing with pet threat. My pet show up but his threat is whacked. It shows his growl getting 5.4k threat which is almost 3 times what it really is. Normally when I fight mobs solo with just aspect of hawk and trueshot auro on my scorpids growl gets 1.7k-1.9k threat. I'm using the latest revision as I updated about 3hours ago just before logging on.

Ya I just noticed the same, it seems growl is being way over valued. Something else odd, without growl on, I'm not peeling at 130% either. Not sure what the discrepency is yet.

I was running the most recent version last night; I got a number of people reporting that they couldn't see my threat (or it appeared only for a little while), despite them showing up as running Threat and compatible when I did a version check.

I just committed the pet fix; should show up in WAU in about 20 minutes.

I had a little problem with this mod. In fact, i wanted to test it in raid situation so i asked my guildmates to install this one. And the result was that i saw "nothing" on the threath meter. Sometimes i saw the main tank, and one or two teammates. And its seems i wasn't generating any aggro
It was really strange and i wasn't the only one in this situation. And i had a problem with recount for no reason it retire some parts of my dmg out in my "screen" only, i had the correct amount of dmg on all the others recount but not on mine (and it was the same for the other one using recount). But it isn't the subject :-/

I think it could be a localisation problem because i play with a french version of WoW.
If you want i could post a screenshot of a raiding situation to illustrate my words. But i know it didn't work like it must. I tested the well-known KTM and no problem with it. But i like the ace mod and the idea of Omen/Threat. Everybody is free to use Omen or not, but they can send their information with Threat and that's pretty cool.

I had a similar problem and after disabling the 'show ktm data' or something similar on omen options it worked fine. No idea if it's the same issue though.

I seem to unable to install Omen without externals.
It seems to work, but BugSack displays me various error messages on startup (disabling Omen also disables these error messages):

[2007/06/24 14:43:20-22-x1]: stack overflow:
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
...:
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:359: in function `EnableKLHTMBroadcast'
Omen-2.1r41232\Omen.lua:329: in function <Interface\AddOns\Omen\Omen.lua:308>
<in C code>: in function `pcall'
AceAddon-2.0-40905 (Ace2):24: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:23>
AceAddon-2.0-40905 (Ace2):991: in function `ManualEnable'
AceAddon-2.0-40905 (Ace2):919: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:912>
<in C code>: ?
AceEvent-2.0-40601 (Ace2):232: in function `TriggerEvent'
AceEvent-2.0-40601 (Ace2):910: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:903>


I installed directly with WAU, as well as manually. Is there any library missing which I cannot identify?

Thank you so much, sp00n. I've been chasing some recursion that popped up in the KTM module in the past day or two; this helps me a ton.

starting to look good. I'll do some more testing with it in SSC and TK tomorrow.
Good work!

Antiarc, I noticed a minor bug today. As a ranged class I was attempting to bump up my threat warning percentage, and noticed that when adjusting the slider over 100%, it goes from 0-10% then resets back to 0 for every 10% above 100% to 130%.

I was also seeing tanks with 130% threat on Magtheridon today, but I was busy cube clicking so I couldn't really investigate more thoroughly. It could have had to do with KTM -> Omen threat however as our MT is not running Omen yet. I'm not overly concerned but I thought I'd mention it.

Keep up the good work!

It'd be nice if one of the warning sound options was the noise when you lose a flag in a battleground. It's the thing CTRA used to use when you pulled aggro.

There's an ace mod called BanzaiAlert that does just that. Comes complete with robotic female voices (if only that were a joke)

Did the arrow marking my own threat get removed? I have the Skin set to one of the bundled options (I think the "compact" one) and there's no little arrow floating by my name to help locate my bar.

Normally random secondary targetting is detached from the normal aggro mechanics, isn't it?
Would be a bug in his design then.

We killed him only once (since the key requirements have been removed last patch), but I think I noticed that, when targetting someone for an orb, Omen switched the threat bars with the current target being on top of the aggro list, but VR didn't run away from his tanks.

Omen swaps bars around based on who the boss is targetting, so because VR targets the person he throws an orb at, the bars will hop, adjusting for that "aggro."

No, I'm speculating regarding the actual aggro mechanics, not Omen's display. I suspect that he actually resets/reevaluates his aggro target when he orbs people, but if that's the case, it may explain some of the seeming "wtf Omen was wrong" experiences people have on that fight.

I've had this happen to me on Gruul right after a Ground Slam, I was 101% or so and I got aggro.

That is possible, though, due to aggro interacting with range and the granularity of the threat system (or, so it has appeared before)

I know, and maybe I wasn't clear enough in my point.
The player being targetted (ranged) was already exceeding the tank's threat, but was not yet above the 130% (at leas I believe so, had other things to do than constantly look at the threat bars ) and did not pull aggro from VR.
The bars did change during he was targetted (I was already at "oh shit" mode) and then turned back to normal.

I mean, there can't be problem with random secondary targetting system (was that the correct phrase? I remember I read this term only back when I was looking for some tactics for Molten Core :x), because there are several bosses who use it. One thing I have noticed is that VR seems to be targetting the person a few seconds before he actually shoots the orb, so it may very well be a specific bug for that encounter.
Can't say we have encountered it yet though, our first kill went quite smooth (to be honest, the trash packs were harder than the boss).