Threat-1.0 is definitely enabled, as omen itself is functioning correctly.

Threat-1.0 is not listed as an optional dependency in the IceHUD_Threat TOC file.

As far as I can tell, the offending line is local Threat = AceLibrary("Threat-1.0") , but I have no idea why.

Go ahead and add Threat-1.0 as an opdep. What's happening is that IceHUD_Threat is loading before Threat or Omen, so when it tries to find the library, it's not there. Listing it as an opdep will cause it to load it, preventing that problem.

If there's already an ## OptionalDeps line, then just add Threat-1.0 to it. If not, then add this to your TOC:

## OptionalDeps: Threat-1.0

Thanks, worked perfectly.

We did a SSC run last night to attune some new recruits and there definitely seems to be a double clear issue with the Leo fight, once he changes into demon form it does the first clear like it should, but then around 5 seconds later it will do a 2nd clear, making Omen then useless and me scrambling for the KTM window.

Also Omen managed to get me killed yesterday, I was doing a bombing quest and got dismounted and then aggroed a few mobs, went to right click a potion from my bag which failed due to Omen bringing up a menu even though I have Omen set to only show the window in raids, which I wasn't in at that time.

This sounds like a sync issue caused by too much mod traffic (I've seen similar when raidofficers are using DoTTimer or the like on aggro clears; their addonspam is getting throttled, and the resync causes the reclear).

Wasn't DoTimers sync code disabled quite some releases ago?

I still have the issue of having my threat not reset on bosses with an aggro reset. It's my threat only that suffers from it and only on my own Omen. All the others report seeying my threat at normal numbers. I've tried a clean install of Omen, deleted my Omen and Threat 1.0 folder and deleted my config file in the WTF folder. Not working.

Bah. Let me see what debug statements I have in there that may help.

I believe it was, but you'd be amazed at people not updating on time. I gave DoTTimers mostly just as an example of a Mod I knew had caused similar issues to the poster; there are likely hundreds of possible culprits.

Yeah, generally spoken, installing Fubar_AddonSpamFu might be a good idea to diagnose problems in that area. It tracks Addon-Channel traffic to see which addon/player spams most.

The only problem I have with the addon message spam reasoning is that it only ever happens in the leo fight, any other fight in any other instance and there are no problems. Would addon spam be that localized?

Every whirlwind in human, which can be as often as every 15 seconds. Definitely likely to cause more Addonspam issues than most fights. Especially when he whirlwinds shortly after a phase transition, or so I am given to understand by friends more progressed than I.

Not saying it must be addonspam, but it fits the symptoms SO WELL.

It was pulled into a separate communication addon, which is enabled by default, as far as I recall. I had to have our warlocks and shadow priests turn it off. The other heavy spammer is Recount, though I believe there was recent work to have its sync optional.

I'm using KTM myself and it is usually Shahraz aswell where threat lags alot for Omen users - it takes about 3-5 seconds for my MT to get above me after he started while my threat and few others that use KTM are on top, then he lags for like 5 secs again... it's quite noticeable at the start of the fight I must say. I'm just used to ignore Threatmeter data on such encounters at the start and take this lags into account when I look at my KTM at all times.

Another thing - correct me if I'm wrong, but ChatThrottleLib only does addon traffic shaping for outgoing data, right? How come "spammy addons" would affect anyone but it's user unless you are on a dialup? I wrote a simple script (I don't use fubar) that just counts amount of data recived and hes not even sending much traffic.

Because when a user's outgoing data is backed up and he sends a "clear threat because of boss ability" message four seconds after it was queued, you get delayed clears in the entire raid group.

Why do you process threat clears of one event from everyone who has assist in the raid? Is it possible to ignore all other threat clear requests from the same event after the first threat clear happened?
Sorry if I misunderstood something...

The problem at Leotheras is that the threat list clears 2 times. Once at the Leotheras->Demon form transformation and 3-4 seconds after that.

I'm noticing that sometimes since 2.3, my misdirected threat is attributed to me, instead of my MD target. Perhaps this has to do with the change in 2.3 making it impossible to overwrite other peoples' MD? I'm thinking this bug happens when someone tries to overwrite my MD and fails, so my MD stays on the tank but Omen doesn't know that.

It's not valid to assume that there's a melee character with assist in range, or that the ranged people have extended their log ranges. Your second point is something along the lines of what I intend to do - it collects all events within a certain period right now, and then executes them, but it needs an ignore buffer after that's gone off.

You don't even need to broadcast clear threat if it is announced zonewide with a yell or emote - why bother even?
In case of a combatlog trigger ("Whirlwind fades"), broadcast it with a timestamp and remember last time you cleared threat, if someone recives clear request compare it with a local timestamp +/- fraction of a second, if matches - ignore, otherwise clear threat.

The threat clear mechanism is a general mechanism designed to handle any sort of trigger, be it local or zonewide.

There is event bucketing in place to handle multiple messages in a short time period. Those aren't the concern - the issue is someone with stopped-up traffic sending a clear 4-9 seconds after the event happens, and after the bucketed event handler has already collected events from non-congested raid members and fired off its clear.

Just wanted to check whether or not you knew anything about protection warrior threat with Omen being a problem since the sunder armour/devastate change recently? Just being lazy and spamming devastate seems to give me around 800tps according to omen which seems way too high for that.