Hmmm, Omen doesnt seem to show myself on the threatlist anymore for some very odd reason. Other ppl cant see me either.

[2007/06/27 19:25:06-386-x6]: Omen-2.1r41730\OmenThreatBar.lua:202: attempt to index field 'parent' (a nil value)

Dunno what caused this actually

Omen seems very bugged atm, threat is registered VERY weird, I was doing 100 TPS tops and I am a tank, people were at 300% aggro and not tanking etc...

people not seeing them self and alot more.

Anyone not seeing themselves should update; there was a change to Parser-3.0 yesterday that broke when Parser-1.1 was also enabled. It's been reverted since.

TPS calculations are broken - I'm expecting to have them fixed tonight. Raw threat numbers should be right though. However, if Revenge/Shield Slam/etc aren't giving their damage on top of the additional threat as total threat, that'd explain the tank discrepancy. I suspect that the Parser change is responsible, but it's top of the priority list to test tonight to be sure.

This is still happening to me (running latest build, 41859).

I just tested briefly and Omen automatically shows when dismissing and summoning a pet (warlock imp). It also shows in other situations (I'm guessing joining party/raid) but I haven't verified it with this build.

Oddly, if I'm inside an inn (resting) it Omen does not show, but as soon as I walk outside it does.

ThreatLib disables itself when you're resting, since you generally aren't going to be in combat with an NPC in a friendly city or inn, so there's no need to spend CPU cycles there.

I'll make sure that a manually hidden Omen is respected on lib reactivation. I can see how that would become really annoying really fast.

It should, yes. However, there were problems in the library upgrade path in older versions. Threat's something of a unique animal in the Ace library world - it's a full addon that can be used like a library that consists of many files. It required something of a hackish solution to get it to work as a library, which I didn't have right till just recently. Current and future versions shouldn't have conflicts with multiple versions installed.

I see that the files.wowace listing for Omen now says "beta, use at own risk!". Is there a particular revision that stable enough for general use? The version I have now seems to work fine, but I am wondering because I am requiring my raiders to pick it up.

Aye, I added that so people would know it is still beta

I haven't made a 1.0 Final release yet, since there are still bugs to be ironed out. I'd recommend waiting till 1.0 Final to make it required, but barring that, just have your raiders get the latest and update before every raid.

I used Omen (41730/Threat 41855) in TK and had the problem that my own threatbar did not appear. I could only see my own threat on Void Reaver but not when we did Al'ar or the trashmobs but the threat from other Threat/KTMusers was there.

Eggi: Omen - Ace Threat Meter

(If you run disembedded, update Parser-3.0)

Yep, same thing. Updating Parser-3.0 fixed it and threat from all sorts of damage is showing up again.

I'm at work, so I can't get a screenshot, but it appears that the odd looking bar for the one party member was due to them using an older version of something, didn't have any problems later on in the day in different parties.

I'll try updating Parser when I get home, but from other posts it looks like that'll fix it.

Edit: Also, no-one elses bar was showing up in that group as they didn't actually have KTM/Threat installed.. But in later groups other players' threat meters were working fine.

Yeah, Threat doesn't do any kind of calculation for others. It only calculates your own threat, and relies on net traffic from your groupmates to display their threat.

Yeah, I realise that, edited my post again cause it wasn't too clear.

The only person in that group whose threat was showing was the tank, which was showing up oddly, couldn't check at a later point (as they'd left the group) what version they were running, but in later groups during that day (with people who were running threat and/or KTM), everyone's threat was showing properly, and I didn't have the same issue, so it looks like an issue with that one person's version of whatever it was they were running.

On weird Void Reaver threat:

Is it possible that Omen discards parried/blocked/dodged knockbacks? De-aggro moves always work even if they are avoided. You can easily verify this on Teremus in Blasted Lands.

I think every real de-aggro. It works on Teremus (a knockback, I believe) and on those Karazhan Ushers (you can spell reflect the iceblock, but you'll lose aggro anyway). I'm quite sure it worked on Broodlord's knockback as well.

A missed incapacitate (gouge, fear, any temporary aggro ignorer) doesnt do anything of course.

This is true for Ushers, but I'm not sure about Void Reaver. We've had the same tank for 50+% of the fight a few times simply because that tank avoided all knockbacks.

Woah thats wrong. If you dodge the knockaway on Void Reaver you lose zero threat. We've had druids tank Void Reaver for 80% of the fight because they dodged them all.

Edit: I should say its only wrong for some abilites like Knockaway. A lot of threat reduction though can't be resisted like those ice blocks.

Edit 2: Also I should say we had warriors and druids all within threat range to overtake for most of those till the end where its way ahead.

Keeping the same tank has a lot to do with how strong your tanks are in generating threat compared to each other. We've only done Reaver once so far and I was tanking about 50% of the fight. I think I flew back 6 times before I lost aggro the first time. I've even solo tanked Broodlord before.

I am quite convinced that avoiding a de-aggro does not avoid the threat change. Unfortunately I am not in a position where I can do lots of testing. I already had a hard time convincing people into using a threat meter :s

It's been my experience that a dodged knockaway wont result in an aggro drop, but a blocked one will. I can go through combatlogs and look for a correlation between knockaways and aggro and provide some more data on it. Ggranted it won't be able to calculate approximate threat values, but I can look for a knockaway and see if he switched target or not.

You shouldn't be able to block the entire Knock Away, so it should still register as a hit.