Change Log:
--------------------
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.
Fixed potential errors caused from combat log changes introduced in patch 4.2 PTR (untested on PTR servers).
Changes from version v3.1.0 to v3.1.1
Fixed errors caused from combat log changes introduced in patch 4.1.
Changes from version v3.0.11 to v3.1.0
Omen3 will now read the combat log and:
Track and estimate temporary threat created by Tricks and Misdirect
Track and estimate threat caused by damage while Fade, Mirror Image and glyphed Hand of Salvation are active
Display these *estimated* threat in a grey (defau...
Description:
--------------------
https://www.paypal.com/en_US/i/btn/x-click-but21.gif
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.
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 rega...
--------------------
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.
Fixed potential errors caused from combat log changes introduced in patch 4.2 PTR (untested on PTR servers).
Changes from version v3.1.0 to v3.1.1
Fixed errors caused from combat log changes introduced in patch 4.1.
Changes from version v3.0.11 to v3.1.0
Omen3 will now read the combat log and:
Track and estimate temporary threat created by Tricks and Misdirect
Track and estimate threat caused by damage while Fade, Mirror Image and glyphed Hand of Salvation are active
Display these *estimated* threat in a grey (defau...
Description:
--------------------
https://www.paypal.com/en_US/i/btn/x-click-but21.gif
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.
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 rega...