About Omen Threat Meter

Omen

Omen is a threat meter.

Basically, enemies in WoW decide who to attack by deciding who is the most threatening based on the abilities you use. What Omen does is provide accurate values of your group's relative threat level on individual enemies, so that you can see when you're in danger of pulling aggro (or, if you're next on the snack list if your tank bites it). This info is usually only critical in raids, where only tanks can survive aggro, but it's useful for any multi-player situation.

Changes from version v3.1.6 to v3.1.7

Add option to choose what sound channel to play warnings on, default is SFX (thanks tharai).

Add fixes for MoP patch 5.0.4 (thanks dridzt).

Removed compatibility code for older versions of WoW. This version now only runs in MoP.

FAQ

How is Omen3 different from Omen2?

Omen3 relies completely on the Blizzard threat API and threat events. It does not attempt to calculate or extrapolate threat unlike Omen2 except when Tricks, Misdirection, Mirror Image, Fade and glyphed Hand of Salvation are active.

Omen2 used what we called the Threat-2.0 library. This library was responsible for monitoring the combat log, spellcasting, buffs, debuffs, stances, talents and gear modifiers for calculating each individuals threat. Threat was calculated based on what was known or approximated from observed behaviors. Many abilities such as knockbacks were just assumed (to be a 50% threat reduction) as they were mostly impossible to confirm.

The Threat-2.0 library also included addon communication to broadcast your threat to the rest of the raid as long as they were also using Threat-2.0. This data was then used to provide a raid wide display of threat information.

Since patch 3.0.2, Omen no longer does any of these things and the need for a threat library is no longer necessary. Omen3 uses Blizzard's new in-built threat monitor to obtain exact values of every members threat. This means Omen3 has no need for synchronisation of data, combat log parsing or guessing, resulting in a significant increase in performance with regards to network traffic, CPU time and memory used. The implementation of boss modules for specific threat events (such as Nightbane wiping threat on landing) are also no longer necessary.

Further benefits of this new implementation include the addition of NPC threat on a mob (eg, Human Kalecgos). However, there are some drawbacks; frequency of updates are much slower, threat details cannot be obtained unless somebody in your party/raid are targetting the mob and it is also not possible to obtain threat from a mob you are not in direct combat with.

How do I get rid of the 2 vertical gray lines down the middle?

Lock your Omen. Locking Omen will prevent it from being moved or resized, as well as prevent the columns from being resized. If you haven't realized it, the 2 vertical gray lines are column resizing handles.

How do I make Omen3 look like Omen2?

Change both the Background Texture and Border Texture to Blizzard Tooltip, change the Background Color to black (by dragging the luminance bar to the bottom), and the Border Color to blue.

Why does no threat data show on a mob when I target it even though it is in combat?

The Blizzard threat API does not return threat data on any mob you are not in direct combat with. We suspect this is an effort on Blizzard's part to save network traffic.

Is there ANY way around this Blizzard limitation? Not being able to see my pet's threat before I attack has set me back to guessing.

There is no way around this limitation short of us doing the guessing for you (which is exactly how Omen2 did it).

The goal of Omen3 is to provide accurate threat data, we no longer intend to guess for you and in the process lower your FPS. Have some confidence in your pet/tank, or just wait 2 seconds before attacking and use a low damage spell such as Ice Lance so that you can get initial threat readings.

Can we get AoE mode back?

Again, this is not really possible without guessing threat values. Blizzard's threat API only allows us to query for threat data on units that somebody in the raid is targeting. This means that if there are 20 mobs and only 6 of them are targeted by the raid, there is no way to obtain accurate threat data on the other 14.

This is also extremely complicated to guess particularly for healing and buffing (threat gets divided by the number of mobs you are in combat with) because mobs that are under crowd control effects (sheep, banish, sap, etc) do not have their threat table modified and addons cannot reliably tell how many mobs you are in combat with. Omen2's guess was almost always wrong.

The tooltips on unit mouseover shows a threat % that does not match the threat % reported by Omen3. Why?

Blizzard's threat percentage is scaled to between 0% and 100%, so that you will always pull aggro at 100%. Omen reports the raw unscaled values which has pulling aggro percentages at 110% while in melee range and 130% otherwise.

By universal agreement, the primary target of a mob is called the tank and is defined to be at 100% threat.

The threat updates are slow...

Omen3 updates the threat values you see as often as Blizzard updates the threat values to us.

In fact, Blizzard updates them about once per second, which is much faster than what Omen2 used to sync updates. In Omen2, you only transmitted your threat to the rest of the raid once every 3 seconds (or 1.5s if you were a tank).

Who wrote Omen3?

Do you accept Paypal donations?

Older Changes

Changes from version v3.1.5 to v3.1.6

Multiply the threat values reported by the WoW Servers in Dragon Soul instance by 10 because they are scaled by 10%. This fixes MI/Fade/Tricks oddities and reported TPS values.

Changes from version v3.1.4 to v3.1.5

Remove code that causes divide by 0 for future WoW updates/PTRs.

Show the "Hide Minimap Button" option if the button is ever registered with LDBIcon instead of trying to check whether FuBar or FuBar2Broker is loaded.

Changes from version v3.1.3 to v3.1.4

Omen will no longer create a second unremovable minimap button for the players that have other installed addons providing the LibFuBarPlugin-3.0 library but are not using FuBar.

Changes from version v3.1.2 to v3.1.3

Optimize CLEU codepath for 4.2 instead of 4.1 now that we are in 4.2. That is, the 4.2 forward compatibility code is now 4.1 backwards compatibility code.

Rearrange initialization code slightly.

Changes from version v3.1.1 to v3.1.2

Fixed issue where some players are unable to see any threat text on the bars until the current profile or TPS option is changed. The fix also fixes issues with some bar settings being "reverted to default" on login.

Changes from version v3.0.9 to v3.0.10

Changes from version v3.0.8 to v3.0.9

Add option to make Omen click-through (non-interactive).

Optimized the bar animation code significantly.

Fix bar backgrounds not being set to the inverted color on login if the "Invert Bar/Text Colors" setting is on. This wasn't noticeable if the bar label color was the default white text with 100% alpha.

Changes from version v3.0.7 to v3.0.8

Fix GetShapeShiftFormInfo() error that occurs for DKs when they aren't in any presence. This occurs when they respec between their primary/secondary specs and the game drops them out of all presences and subsequently enter combat presence-less.

Changes from version v3.0.4 to v3.0.5

Fix Omen getting stuck to the mouse if autocollapse is on and you moved Omen while you are in combat and exited combat during the move.

Set a player's threat to 0 (for display purposes) if the player's threat is less than 0. This occurs on Fade and Mirror Image, which gives the caster a temporary threat reduction of 410057408 (or 4.1m threat in Omen's terms). Previously Omen ignored players with negative threat.

Omen will now remember its visible state when you log out (applicable only if auto-show/hide is off).

Changes from version v3.0.3 to v3.0.4

Update ruRU, koKR and zhTW localizations

Fix "Passed X% of Y's threat" message where it would report your name instead of the tank's name if you passed your tank's aggro AND pulled aggro at the same time.

Changes from version v3.0.2 to v3.0.3

Update various localizations. esMX will now see the same translations as esES

Add LSM callbacks so that the user can use custom media or media registered by other addons correctly

Allow the user to have different background settings for the Title Bar than from the main Omen window

Changes from version v3.0.1 to v3.0.2

Update various localizations

Fix error that occurs on changing Clamp To Screen option

Add option to change the Pet Color and changed the default Pet Color to violet

Omen will no longer create its internal minimap button if FuBar or Broker2FuBar are loaded

Changes from version RC3 to v3.0.0

Fix bug which caused ghost bars to show when some classes are not selected to be shown

Add Tank Bar color option

Add "Always Show Self" option

Add Show/Hide Title Bar option

Add Use Focus Target and Test Mode checkboxes into the configuration panel

Add Show Aggro Bar option

Make Test Mode much more useful by showing bars of every possible class and the player

Fix minor issue where the TPS numbers are 1 pixel higher than the rest of the text on the threat bars

Hard embed LibDataBroker-1.1 and use it

Add LibDBIcon-1.0 external

Add minimap button option, default shown

Fix Omen's FuBar plugin issue for right clicks to open the configuration panel interfering with library upgrading paths

Rewrite Auto Show/Hide options to be more intuitive. Add option not to use Auto Show/Hide

Add an internal flag so that if the user manually toggles Omen's visibility, it stays shown/hidden until he next zones, join/leave a party/raid, or change any Auto Show/Hide settings

Add option to ignore player pets to display threat info on (Default: On). Yes, player pets have aggro tables too!

Add Frame Strata and Clamp To Screen options

Apply a whole list of configuration settings that were forgotten on changing profiles

Updated the FAQ

Changes from version RC2 to RC3

Renamed localization\deDE.lua to Localization\deDE.lua so that the auto-generated zip file will contain the folder "Localization" rather than "localization", which means Omen will now work on non-Windows operating systems

Changes from version RC1 to RC2

Add keybind to toggle using the focus target

Fix missing localization entry for "Passed %s%% of %s's threat!"

Add option to color your own threat bar to a color of your choice

Fix "VGrip1Ratio" error that occurs when completing a drag and Omen incorrectly attempts to hide itself.

Thanks. I guess I spent all that time figuring out how to explain what was happening for nothing. I did raid today, and I noticed that I could mash my drink button as soon as I went out of combat. :) Thank you.

Love this mod. It's way better than KTM, imo. I especially love the the threat message in the middle of my screen once I get close to the tank's aggro.

I have a question about the "cool single bars". I don't think they're very cool at all. It might be a bug for me or something..... this is what's happening:

I have my omen right above my water/food bar. I have it set to expand upward. When I mouseover my water button, I get the tooltip thing for a person that's in my group. So, if I drag the invisible area over my buttons, it drags out one of those single bars. I know this happens after omen shrinks to its one bar size (after the combat ends and everyone's threat bar disappears). But it's not just happening where people's bars used to be. It's happening where the bars would have been if I didn't have it set to expand upward. The way I have it sitting now, that area that I can drag out those bars from, has something invisible in it that's making it happen.

I hope that I explained the properly. I just downloaded the latest version, so I haven't seen if this has been fixed in it or not. But I know that it was giving me trouble with the version I currently have.