Herro! I didn't write the below, but we've had our guild convert over to the new Threat Meter, if you really want to have a much higher quality meter, read this and make the switch. After the 3ish paragraphs about backstory, all the features are listed. Enjoy, I know we have.
So, a little backstory. With 2.1, mod authors got the ability to individually profile addons and see how much CPU time and RAM they're taking. What we've discovered is that KTM takes an absolutely horrid amount of CPU time, even when it's doing nothing, due to its architecture (it's poll-driven, rather than event-driven, like every other WoW mod). Kenco, the author has basically said "buzz off, my mod's fine" to everyone concerned about this, and is not going to be updating it to be more friendly to the user.
Irritated by this, I started working on a threat meter of my own. The rest of the wowace developer community, being somewhat performance consciencious, is irritated with Kenco as well, and has chipped in to make this possible. At last check, I had 10 other people besides myself making commits to the project. The result of this is that in one weekend, the community has basically written a threat meter mod. We've gotten ability modules written for each of the nine classes, as well as a general framework to handle upgrades and updates in the future smoothly. We've collaboratively written Threat-1.0, which is a library that tracks threat and communicates it with your group, keeping you synched so that all members of your group with Threat installed are aware of each others' threat levels on all mobs at all times. It is purely event-driven, and built on the Ace library framework, resulting in a very lean, very fast, very mean mod.
This also means that any number of GUIs can be written to display your threat levels. Right now, I've got a very basic mod called Omen that provides a frontend for Threat-1.0. You can consider it (and Threat) beta for now, but they work well enough that they could use testing. If you are an end user, you only need download the Omen zip - it contains the Threat-1.0 library as an embedded library, so you don't need to even think about it. You can also download (and update) this mod through WoWAceUpdater.
This is not "KTM converted to Ace", but a ground-up, rewritten, brand-spankin' new threat mod. It is designed to be flexible, extensible, and easily maintainable, and it has a solid community of developers behind it, ensuring that it will stay up to date and accurate as threat mechanics change.
Features
As a GUI for Threat-1.0, Omen gains all of its power and features, including:
Multi-mob threat tracking. Omen shows a threat list for the mob that you have targeted, which allows you to maintain a reasonable idea of your threat level against any given target in a multi-mob encounter. This isn't possible for meters that only report aggregate threat.
Automatic boss encounter threat management. Encounters with threat wipes are handled automatically, and ensure that your threat lists stay relevant and usable.
No "bleed-over" threat from player-player damage. Unlike aggregate meters, Omen won't report incorrect threat levels for Shatter, Static Charge, and other player-inflicted damage.
Lean and mean. Threat and Omen are both written for speed and efficiency, and consume only trivial amounts of system resources.
Link: (info)
http://www.wowace.com/wiki/Omen
Link to DL it:
http://files.wowace.com/Omen/Omen.zip
Features include:
Fully configurable display, which allows you to change virtually all colors, textures, and sizes, letting you customize the meter to fit into your UI as you best see fit.
Class filtering, allowing you to ignore classes whose threat you aren't interested in.
Absolute threat, relative threat percentage, and threat-per-second (TPS) values
Aggro gain indicator to help you see when you might pull (or lose) aggro.
Pull-out threat bars that allow you to compare your threat level against a tank's threat level in single, easy-to-understand bar format. No more scanning a list of 25 people to ensure you stay below a tank - just pull off their bar from the main display and you can monitor your threat level versus theirs to ensure that you stay safe.
Optional display for threat values from KLH Threat Meter, so that even if your groupmates are not using Omen, you can still see approximate threat from them. Please be aware that as KTM is an aggregate meter and not aware of multiple targets, any values from it will be incorrect in any multi-mob encounter beyond the first mob.
FAQ
Do other people need Omen installed for it to work?
Short answer: yes
Long answer: kinda
To get fully accurate data, your groupmates must have Threat-1.0 (or an addon that uses it) installed and running. Any addon that uses Threat-1.0 will satisfy this requirement and will provide full and accurate threat data to Omen. Currently, addons that use Threat-1.0 include:
Omen (naturally)
Aloft
Assessment
PitBull
Recount
Violation
If you or your groupmates have any of these addons installed, or have Threat-1.0 installed as a standalone, then they are capable of sending and receiving threat data.
Additionally, Omen is capable of displaying data from KLH Threat Meter, so if your groupmates are using it rather than Omen, you will get threat data from them. Please be aware that as KTM is an aggregate meter and not aware of multiple targets, any values from it will be incorrect in any multi-mob encounter beyond the first mob.
Can I use Omen with KTM?
Sure! Omen gets along well with KTM. If you are running both Omen and KTM, then your groupmates running Omen (or Omen and KTM) will see threat data from Omen. If they are running only KTM, then they will see data from KTM.
Currently, Threat-1.0 (and therefore Omen) does not support sending data from Omen to KTM.
Omen is intended to be a KTM replacement, but there are obviously transitory periods for any raiding group.
How does Omen handle multiple targets with the same name?
Unfortunately, this is a major weak point in any threat library. Multiple targets with the same name are indistinguishable in the combat log, so you can't really tell which one to apply threat to. Therefore, all targets with the same name share a threat pool, and will show the same threat value. This is regrettable, but Blizzard has intentionally not provided enough information to distinguish same-named mobs in the combat log. Fortunately, there really aren't any threat-sensitive encounters where there are a lot of mobs of the same name that you need to dance the threat line on.\
DoTimer manages to tell the difference between multiple mobs with the same name, why can't Omen?
DoTimer makes some assumptions about what you're casting on - namely, that you're looking at it in some form. It's possible to hit enemies (and incur threat on them) without ever targeting, mousing over, or focusing them, so the same assumption can't apply to Threat-1.0. Sorry.
