If the libraries downloaded then you have something, somewhere, that's decided they are needed - usually as a dependency. That said, libraries only get loaded as needed so not usually something to worry about.

If you updated as described - you do use all of those libraries, just you didn't see them because they were inside addon subfolders.

Last night, I was MTing Black Temple and consistently had other people much higher than me on threat without pulling on many trash fights/bosses (ranged at about 150% let's say). It was especially noticeable on Illdari Council since that's 9 minutes of me threating up on the same target. It used to be wrong usually anyhow because of Spell Reflect but my understanding was that should be calculated correctly.

Not to nitpick, but screenshots or a version number would help Antiarc track down a bug like this. Without one he has no idea if it's an unknown bug in the current revision, or a bug fixed in a past revision. Just a thought.

Slightly same issue, I suppose. I've been having my entire raid use the same version of Omen (even if its out of date by one or two versions) to make sure we don't have 'unknown' show up on the lists, it seems to help a bit. The issue we were having last night, was with 1 certain warlock, and no one else. While fighting Brutallus no one could touch our tanks threat, but our affliction/ruin lock rode their nuts for each attempt. He even went over and didn't pull threat, while in "melee range". Not sure if its something with that class/talent specifically, but yea.

Edit: Blah, forgot version: 67718 is what the console shows in game, however we all downloaded it from a file named 66752 (I believe).

Omen froze up my WoW client last night in Hyjal. We were tanking a large wave, and I clicked on AOE Mode, and it got a few slow frames off and then froze. Then I was told on vent I went offline. There was too much data to process I'm guessing.

I was using revision 67718.

Machinator you saved me. It's not only Omen. Prat-Recount-Omen-Ebb didn't work because of cooldowncount. It was like they were not there at all. Half raid today I was without those four addons until I checked over here.

How are you guys installing these addons? I'm using Recount/Omen/the kitchen sink with CooldownCount and they work fine.

I used the wowace updater with externals and got the cooldown count problem, removed CDC and everythign works fine now.

This means cooldown count has an outdated library in it's internal lib folder... Bring it up with whoever manages cooldown count (can't remember off the top of my head).

FishEye: changelog WowAce/trunk/CooldownCount

Don't bother, it was the author/maintainer of CooldownCount that broke it in the first place because hes a moron. To prevent this happening in the future I suggest not using CooldownCount and instead using the much superior OmniCC (before you ask no it can't be found on wowace).

Soloing with my boar pet makes me suspect they changed the boar charge mechanic in 2.4.1 back to the pre-2.4 version. Before patch I could easily pull him off a mob he charged, but after patch I can easily go full out for a long time after crossing above the Omen 130% bar.

If any other boar-toting hunters notice a similar pattern perhaps it should be changed in the Threat module as well.

I've noticed that LibFuBarPlugin-3.0 is included as an embedded lib in Omen, despite having selected without externals in WoWAceUpdater. Is there any special reason for this, seeing that the lib is also available as a seperate lib on the wowace page?

We are having a problem with Omen that we have to have the entire guild on the same version or they don't show up on Omen. And the update are coming 10+ times a day. Is there any way (we) can make it backwards compatible for 24 hours?

This is ridiculous. We all updated 10 mins before raid start time. Everyone is flagged as having compatible versions (almost all 68146, a few on 67718). One of our feral tanks is sometimes visible, sometimes not. Same for our pally tank - some pulls he shows up on Omen, some he doesn't. Misdirect is Just Not Working, it attributes the threat to the hunter rather than the misdirect target.

Edit: On one pull, I found I got no bars at all if I used the default Omen skin, while using the "Classic" or "Compact" skins showed the bars as usual.

OK, this very definitely appears to be a bug with Misdirect

At the pull, our hunter (Drumar) misdirected to our pally tank (Riorik).

Drumar got assigned the threat from the initial shot, and also continued to show at the top of the list for 20 seconds ago, with excellent TPS, while Riorik was actually holding aggro. Then, some time later into the fight, Drumar dropped out of sight. Riorik never appeared on the list that I could see until the end.

It looks like the bars for Drumar and Riorik either got switched, or some similar error.

In case it is needed I can confirm this. MD and Omen don't mix well anymore.
I have begun to count the threat MD does and mentally try and keep track of it, mostly I give up after a short while and just FD. At which point sometimes the tank does appear to not get counted correctly. In one Heroic a Mage was running at 150% of the tank's threat, but not once did the boss look at him. That was one of the versions yesterday (too many updates to keep track of their numbers anymore)...

Everyone seems to be having horrible problems with Bloodboil. I have a theory I'd like people to check out. If you die during a Fel Rage (i.e. you have the Insignificance debuff), can you check to see whether you get a combat log message to say it fades from you when you die?

This would seem to fit many of the observed symptoms. Lots of people have posted that it's fine on the first pull, but that on the second and subsequent pulls, people start randomly disappearing from the threatlist. If Omen hasn't correctly cleared the Insignificance debuff (either because of a bug of because the fade message was never sent to the client), this would explain it perfectly.

Not clear why some Bloodboil pulls will show healers or hunter pets with huge threat, but I think the way some people just disappear from the threat list entirely is most likely to be a problem linked to the Insignificance debuff.

As we will likely be doing bloodboil tonight, this is rather relevant to me as well.

I'm curious though, if that is the issue, wouldn't having everyone reload their UI clear it up? Granted this would be a work around, not a fix.

Should do, if I understand right. If you hit problems, try that out and see if it helps.

Isn't there a /threat clear command available now? Should do the job.


On another note, the latest build seems a little buggy regards Pets - on Brutallus we had the occasional Pet on top of threat.

Whole raid using: Threat 2.0:68197 Omen:68250

Haven't seen this noticed yet.
I noticed that Invisibility drops threat in Omen completely immediately on cast. What it should do is reduce threat by 10% every second end drop to 0% after 5 sec. Kind of annyoing, because you don't normally let Invis really tick 5 sec in PvE.

I guess the reason is the way the combatlog displays Invis. If I recall correctly, on the PTR the invis buff only showed up when Invis goes the whole 5 sec, no message for the initial cast or the ticks.
Now it shows a gain message on initial cast, a fade message if it breaks early, and a fade message+gain message when the mage actually goes invisible. So a fully successful Invis is:
0:00 cast -> gain invis
0:05 fade invis
0:05 gain invs
0:25 fade invis
Omen seems to use the old PTR model


Some Combatlog samples:

attacked a Teromoth, Frostnova, used invis, got hit by wing buffet.

attacked a wolf, used invis, let it hit me with a normal swing

attacked a wolf, frostnova'ed him to get away, hit invis and got invisible after 5 secs, clicked of the buff a bit early.

Hope this helps.

/Edit: I forgot, Version is r68354, updated half an hour ago. Don't know if this makes any difference.