Go to Page... |
Compatibility: | Battle for Azeroth (8.0.1) |
Updated: | 07-17-18 01:55 PM |
Created: | unknown |
Downloads: | 4,133,291 |
Favorites: | 5,507 |
MD5: |
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 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).
Where can I report bugs or give suggestions?
Comment Options |
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
08-09-09, 02:38 AM | ||
A Kobold Labourer
Forum posts: 0
File comments: 31
Uploads: 0
|
|
|
|
pp0000656 |
View Public Profile |
Send a private message to pp0000656 |
Find More Posts by pp0000656 |
Add pp0000656 to Your Buddy List |
08-08-09, 08:16 AM | ||
|
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 of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes |
|
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
08-08-09, 08:07 AM | ||
|
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 of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes |
|
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
08-08-09, 05:35 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 31
Uploads: 0
|
Why does the height of the bar where the name of the target is displayed resets to it's default after relog?
|
|
pp0000656 |
View Public Profile |
Send a private message to pp0000656 |
Find More Posts by pp0000656 |
Add pp0000656 to Your Buddy List |
08-02-09, 03:20 AM | ||
|
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. |
|
|
Squishy Tia |
View Public Profile |
Send a private message to Squishy Tia |
Find More Posts by Squishy Tia |
Add Squishy Tia to Your Buddy List |
07-25-09, 10:11 PM | |
|
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!
__________________
Fear my Aim, for it be True, Swfit, and Deadly! |
|
Landrell |
View Public Profile |
Send a private message to Landrell |
Find More Posts by Landrell |
Add Landrell to Your Buddy List |
07-11-09, 11:07 AM | |
|
Re: Re: Re: new error
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 of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes
Last edited by Xinhuan : 07-11-09 at 11:32 AM.
|
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
07-11-09, 01:18 AM | ||
A Kobold Labourer
Forum posts: 0
File comments: 153
Uploads: 0
|
Re: Re: new error
Last edited by lewal : 07-11-09 at 02:12 AM.
|
|
|
lewal |
View Public Profile |
Send a private message to lewal |
Find More Posts by lewal |
Add lewal to Your Buddy List |
07-11-09, 12:30 AM | |
|
Re: new error
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?
__________________
Author of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes |
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
07-10-09, 01:59 AM | |
A Kobold Labourer
Forum posts: 0
File comments: 153
Uploads: 0
|
new error
Date: 2009-07-09 19:15:34
ID: -1 Error occured in: Global Count: 2 Message: ..\AddOns\Omen\Omen.lua line 1585: Usage: GetShapeshiftFormInfo(index) Debug: [C]: ? [C]: GetShapeshiftFormInfo() Omen\Omen.lua:1585: UpdateBarsReal() Omen\Omen.lua:1344: Omen\Omen.lua:1342 AddOns: Swatter, v5.5.4293 (WombatII) Corpse, v3.1.0.4 Ace2, v ActionButtonColors, v1.3 AlarBGHelper, v3.5.10 r48 AlphaMap, v3.63.30100 AlphaMapBattlegrounds, v AlphaMapExteriors, v AlphaMapInstances, v AlphaMapPOIFlightMasters, v AlphaMapPOIInstances, v AlphaMapPOITravelAgents, v AlphaMapPOIUtilities, v AlphaMapWorldBosses, v ArenaCalculator, v1.6.3 Atlas, v1.14.1 AtlasBattlegrounds, v1.14.1 AtlasDungeonLocs, v1.14.1 AtlasOutdoorRaids, v1.14.1 AtlasTransportation, v1.14.1 AtlasWorld, vv3.1.1.11 AucAdvanced, v5.5.4293 (WombatII) AucFilterBasic, v5.5.4293 (WombatII) AucFilterOutlier, v5.5.4293.2531 AucMatchUndercut, v5.5.4293.2531 AucScanData, v5.5.4293 (WombatII) AucStatClassic, v5.5.4293 (WombatII) AucStatHistogram, v5.5.4293 (WombatII) AucStatiLevel, v5.5.4293 (WombatII) AucStatPurchased, v5.5.4293 (WombatII) AucStatSales, v5.5.4293.2842 AucStatSimple, v5.5.4293 (WombatII) AucStatStdDev, v5.5.4293 (WombatII) AucStatWOWEcon, v5.5.4293.2530 AucUtilAHWindowControl, v5.5.4293.3311 AucUtilAppraiser, v5.5.4293.2530 AucUtilAskPrice, v5.5.4293.3175 AucUtilAutoMagic, v5.5.4293.3142 AucUtilCompactUI, v5.5.4293.2530 AucUtilEasyBuyout, v5.5.4293.3583 AucUtilItemSuggest, v5.5.4293.3108 AucUtilPriceLevel, v5.5.4293.2545 AucUtilScanButton, v5.5.4293.2530 AucUtilScanFinish, v5.5.4293.2530 AucUtilScanProgress, v5.5.4293.2530 AucUtilSearchUI, v5.5.4293.3655 AucUtilSimpleAuction, v5.5.4293.0 AucUtilVendMarkup, v5.5.4293.2530 AwesomePlayerPortrait, v1.1 azHideSpam, v1.2 Babylonian, v5.1.DEV.130 BeanCounter, v5.5.4293 (WombatII) BloodyRare, v1.1d BonusScanner, v5.0 BrokerHitCrit, v2.8.4-release BUFX, v1.09 BuyEmAll, v CashStash, v1.2.1 CattleProd, v2.3.0 ComeHere, v1.6 Comix, v1.7 beta Configator, v5.1.DEV.130 DBMBurningCrusade, v DBMCore, v DBMRaidLeadTools, v DBMVictorySound, v DeathDealer, v1.2 DebugLib, v5.1.DEV.130 DepositBox, v30000.2 DirtyGear, v1.1-a5 Dominos, v1.9.4 DominosBuff, v DominosCast, v DominosRoll, v DominosXP, v Doomed, v1.0.1 ElkBuffBars, v2.2.4-149 EMLib, v Enchantrix, v5.5.4293 (WombatII) EnchantrixBarker, v5.5.4293 (WombatII) EnhTooltip, v5.1.3715 (SnaggleTooth) EquipCompare, v2.16 EWOlsonGetItemInfo, v EWOlsonGetSellValue, v EWOlsonPointsOfInterest, v Examiner, v09.05.24 Fizzle, vv1.3.2 FlightMap, v FocusFrame, v2.5.1 FuBarPlugin20, v2.0 $Revision: 66634 $ Gatherer, v3.1.13 GatherSage2, v2009-06-23 GearDPS, v0.77b GearScore, v2.2.09 - Release GearScoreRecount, v GemQuota, v$Revison$ GetOpt, v ImprovedMerchant, v3.6x5 Informant, v5.5.4293 (WombatII) InspectEquip, v1.4.0 Intel, v0.42 ItemInfo, v ItemRack, v JebusMail, v2.4b LanguageCycle, v LastWords, v2.0.10 LevelDisplay, v5 LibRareSpawns, v1.0.30100 LightHeaded, v293 MagicRunes, v1.0.61 MagicRunesIconDisplay, v1.0.61 MagicRunesRuneBars, v1.0.61 MagicTargets, v2.0.88 MapNotes, v5.16.30100 MapNotesBrowser, vv1.00.30100 MapNotesForAtlas, v1.00.30100 MapNotesIconLib, v1.04.30100 MapNotesIconLibFancy, v MapNotesIconLibLegacy, v MapNotesIconLibNeptunia, v MapNotesIconLibNumbers, v MinimapButtonFrame, v3.0.6 MinimapButtonFrameSkinPack, v3.0 MinimapButtonFrameTitanPlugin, v2.2 MovableBags, v MozzFullWorldMap, v3.35.30100 MrDamage, vr813 naiStats, v Omen, v3.0.6 Overcharge, v3.1.2.2 Postal, v3.1.2 PVPtimer, v QuickMountEquip, v RareSpawnOverlay, v4.0.30100 RatingBuster, v Rebar, v Recount, v Redeemer, v sct, v6.2 sctd, v3.1 SharedMedia, v3.0 shieldmonitor, v1.4.6 SlideBar, v5.5.4293 (WombatII) Stackpack, v2.4 StealYourCarbon, v3.0.3.16 Stubby, v5.5.4293 (WombatII) TalentedLoader, v TankPoints, v Titan, v4.2.5.30100 - Revision 273 TitanClock, v4.2.5.30100 TitanCompanion, v1.00.30000 TitanCoords, v4.2.5.30100 TitanItemBonuses, v4.1.6.30000 TitanMail, v3.0-r1 TitanMount, v1.00.30000 TitanPerformance, v4.2.5.30100 TitanRecZone, v3.0.2 TitanRegen, v4.2.5.30100 TitanRepair, v4.2.5.30100 TitanRider, v3.0 r2 TitanSpec, v1.4.3.30100 TitanVolume, v4.2.5.30100 TitanWG, v1.0.1.30100 UrbanAchiever, v WhereToNow, v1.6 WowLife, v1.0.0 (ck=10a9) |
|
lewal |
View Public Profile |
Send a private message to lewal |
Find More Posts by lewal |
Add lewal to Your Buddy List |
06-06-09, 10:22 PM | ||
|
Omen3 also creates a Fubar plugin for FuBar if FuBar is detected to be loaded. So if you have Broker2FuBar installed, you need to go /b2f options and tell B2F to not convert the LDB into another FuBar plugin (or you will have 2 omen icons). In your case, Omen3's FuBar plugin settings for whether its displayed on the minimap or FuBar's bar is stored and set in Omen3 itself. If you change the Omen's FuBar setting within FuBar itself, it will not be remembered or saved. This is because of having the optional fubar plugin, as opposed to having it in a separate addon called OmenFu. So go /omen config, find the FuBar subsection in Omen, and make your changes there.
__________________
Author of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes |
|
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
06-05-09, 01:49 AM | |
|
Okay here's what I did:
1. Enabled only Fubar and Omen, placed Omen on the fubar, relogged, and omen icon was gone. 2. Shut down game, deleted all Fubar and Omen related setting luas in the WTF folder, tried again... and it's gone... Hrmm... |
|
Kupotek |
View Public Profile |
Send a private message to Kupotek |
Find More Posts by Kupotek |
Add Kupotek to Your Buddy List |
06-05-09, 01:37 AM | ||
|
Alright, I'll enable fubar and omen, stick it on the bar with just those 2 addons enabled, see if it stays, then enable my addons 1 by 1 and let you know what's breaking it |
|
|
Kupotek |
View Public Profile |
Send a private message to Kupotek |
Find More Posts by Kupotek |
Add Kupotek to Your Buddy List |
06-05-09, 01:34 AM | ||
|
Omen hasn't changed in the last 1.5 months!
__________________
Author of Postal, Omen3, GemHelper, BankItems, WoWEquip, GatherMate, GatherMate2, Routes and Cartographer_Routes |
|
|
Xinhuan |
View Public Profile |
Send a private message to Xinhuan |
Find More Posts by Xinhuan |
Add Xinhuan to Your Buddy List |
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.