Blizzard's threat API only allows us to query for threat data on units that somebody in the raid is targeting. ![]() 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 backAgain, this is not really possible without guessing threat values. 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. If you haven't realized it, the 2 vertical gray lines are column resizing handles.How do I make Omen3 look like Omen2Change 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 combatThe Blizzard threat API does not return threat data on any mob you are not in direct combat with. Locking Omen will prevent it from being moved or resized, as well as prevent the columns from being resized. 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 middleLock your Omen. 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). 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. Omen3 uses Blizzard's new in-built threat monitor to obtain exact values of every members threat. 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. 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. Threat was calculated based on what was known or approximated from observed behaviors. This library was responsible for monitoring the combat log, spellcasting, buffs, debuffs, stances, talents and gear modifiers for calculating each individuals threat. ![]() 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 info is usually only critical in raids, where only tanks can survive aggro, but it's useful for any multi-player situation.FAQHow is Omen3 different from Omen2Omen3 relies completely on the Blizzard threat API and threat events. 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). 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.
0 Comments
Leave a Reply. |