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.
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.
Does Omen3 sync or parse the combat log?
No. Omen3 does not attempt to sync or parse the combat log. Currently there are no intentions to do so.
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).
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.
Add Fade/MI Color to the options. This color is used on players under the effects of MI/Fade.
Add 410065408 threat to all players with negative threat for display purposes. English translation: You can now see the "un-Faded/un-MIed threat" of players under the effects of Fade and Mirror Image.
Changes from version v3.0.4 to v3.0.5
Implement an update event throttle, reducing CPU usage significantly without any loss of updates.
Clear the guidNameLookup table on zoning to recover some memory.
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
Fix bugs with "Hide Omen on 0 bars" option that caused Omen to keep appearing when unwanted
Changes from version v3.0.0 to v3.0.1
Fix error that occurs on changing profiles: Omen-3.0.0\Omen.lua:592: attempt to index global 'bar' (a nil value)
Changes from version RC3 to 3.0.0
Updated various localizations
Add Show threat values and % options
Add Aoogah! sound from Omen2
Fix Omen's alpha setting not applying on login
Add option not to use class colors
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.
Optional Files - Omen Threat Meter
Sorry, there are currently no optional files available.
Originally posted by Tegarbah Are the bars clickable? As a pally tank I want to cast Hand of Salvation on any encroaching threats but don't always have the time to check who it is and find their portrait to to cast on them.
This is not possible due to restrictions placed by Blizzard. Anything you can click to cast spells on (i.e a button assigned to represent a player) is not allowed to be moved/resized or shown/hidden while in combat.
If this was doable, it would have been trivial to decurse people aka Decursive four years ago back when this was possible before Blizzard patch 2.0.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
Are the bars clickable? As a pally tank I want to cast Hand of Salvation on any encroaching threats but don't always have the time to check who it is and find their portrait to to cast on them.
Message: Interface\AddOns\FuBar_OmenFu\FuBar_OmenFu.lua:2: Cannot find a library instance of Threat-2.0.
Time: 08/11/09 14:58:42
Count: 1
Stack: [string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:18: in function <[string "Interface\FrameXML\BasicControls.xml:<Scrip..."]:4>
[C]: ?
[C]: in function `error'
...nterface\AddOns\Aloft\Libs\AceLibrary\AceLibrary.lua:490: in function `AceLibrary'
Interface\AddOns\FuBar_OmenFu\FuBar_OmenFu.lua:2: in main chunk
[C]: ?
[C]: in function `pcall'
Interface\AddOns\FuBar\FuBar.lua:829: in function <Interface\AddOns\FuBar\FuBar.lua:824>
Interface\AddOns\FuBar\FuBar.lua:959: in function `LoadPlugin'
Interface\AddOns\FuBar\FuBar.lua:1094: in function `object_method'
...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:289: in function <...Ons\FuBar\libs\LibRockTimer-1.0\LibRockTimer-1.0.lua:227>
Locals: (*temporary) = "Cannot find a library instance of Threat-2.0."
Originally posted by pp0000656 So if border settings in general options is set to 8, the height of the bar must be at least 16?
Yes. Because the border must be at least 8 thick on the top and 8 thick on the bottom, so the whole thing has a minimum height of 16. If border thickness is set to 8 that is.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
Originally posted by pp0000656 Could you bring me the numbers so I had an example? Btw where to change the edgesize?In title bar options or in global?
Your border thickness (for Omen's background) can be found in the general settings at the bottom after you scroll down. You can set a different background for the title bar itself, but if the checkbox to use the same background as the general settings it ticked, it uses that instead.
The "edgesize" is called "Border Thickness" in Omen.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
B) Your preferred height setting is less than twice the height of your title bar background's edge size (border thickness). Omen forces the minimum height to be at least double your background's edgesize (border thickness).
[/b]
Could you bring me the numbers so I had an example? Btw where to change the edgesize?In title bar options or in global?
Originally posted by Landrell Do you think it's a possible memory leak in the mod? Just thought I'd throw this out there. Thank you for making such a wonderful mod!
Depending on the definition of "memory leak", strictly speaking, there can be no memory leak in any WoW addon because Lua uses an automatic garbage collection system that collects all unreferenced memory objects. Thus no memory leak can occur, unless it is at the Lua implementation level - i.e, a fault with WoW's programmers.
Less strictly speaking, "memory leak" can also refer to objects being held in memory unintentionally which are no longer being used due to programmer mistake. Omen has been looked over several times and has no such known leak. You can easily raid for hours without any memory growth attributed to Omen.
Nevertheless, there are known cases of particular addons causing crashes with certain players and/or characters which nobody else in the world can replicate. I've had Tomtom crash my WoW before but millions others use it fine without crashes. You're just the unlucky one where Omen crashed on your DK. :P
Not exactly trying to shake off responsibility here, but Lua in WoW is run in a sandboxed environment, and if any WoW crashes occur, it is in essence a WoW error due to the interactions between Lua and WoW, and should be reported to Blizzard via their error reporting tool.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
Originally posted by pp0000656 Why does the height of the bar where the name of the target is displayed resets to it's default after relog?
3 possibilities:
A) The Omen.lua file (where settings are saved) in your WTF folder in your account is write protected. If you are running Windows Vista, this folder could be in your virtual store.
B) Your preferred height setting is less than twice the height of your title bar background's edge size (border thickness). Omen forces the minimum height to be at least double your background's edgesize (border thickness).
C) You have another addon interfering, such as addons that switch other addon's profiles.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
Originally posted by Landrell I love Omen! Though I've seem to run into a problem with this mod here recently. I've noticed that it only happens with my Death Knight and no other characters. When I try to log onto my DK, the game automatically shuts down and errors out and gives me an error based on insufficient memory. I've even gone so far of trying out every single Add on that I currently use to see if they cause this issue, however, Omen is the only one that does this.
Do you think it's a possible memory leak in the mod? Just thought I'd throw this out there. Thank you for making such a wonderful mod!
So with Omen as the only addon enabled (other than the built in BlizzardUI addons), this is still the case? If so that sounds an awful lot like a buffer overrun/pointer pointing to a memory location outside the allocated stack. The latter shouldn't happen with the current LUA revision, and the former is very very seldom encountered.
Have you tried with just Omen enabled and temporarily moving your /WTF/Account/AccountName//ServerName/DeathKnightName out of the folder? Try that first and see if it corrects the problem. If it does, then you have a corrupt character file, which in theory could cause problem #2 above.
I love Omen! Though I've seem to run into a problem with this mod here recently. I've noticed that it only happens with my Death Knight and no other characters. When I try to log onto my DK, the game automatically shuts down and errors out and gives me an error based on insufficient memory. I've even gone so far of trying out every single Add on that I currently use to see if they cause this issue, however, Omen is the only one that does this.
Do you think it's a possible memory leak in the mod? Just thought I'd throw this out there. Thank you for making such a wonderful mod!
That's the interesting thing, Omen has had no updates, nor has the live servers got a patch since 3.1.3 so I'm not sure why there would suddenly be a new error now.
Edit: Alright, I've figured it out. Omen will cause that error if you are not in a presence. This happens if you respec (switch primary/secondary specs) and the game drops you out of any presence. This only started happening recently.
Also, you are running Omen 3.0.6, the latest is 3.0.7, although this error continues to exist in 3.0.7 and will be fixed.
__________________
Author/Maintainer of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, Routes and Cartographer_Routes
Originally posted by Xinhuan Can you give more details about the error, which server it is (PTR or live servers?), what class and level you are and how/what you were doing when the error occurred?
ok im a dk on silverhand live server as for what im doing sometimes im hoovering over my bar other times its when i hoover over a player ive had this omen for months with no problems i down loaded no new mods i use dominos as my bar mod its either obiterate, ghol frenzy or ice touch that triggers it on the bars
You have just downloaded by the author . If you like this AddOn why not consider supporting the author? This author has set up a donation account. Donations ensure that authors can continue to develop useful tools for everyone.
*Clicking the donate button above will take you to PayPal.com
*Clicking the donate button above will take you to Pledgie.com
Btw where to change the edgesize?In title bar options or in global?
