Update FAQ.
This commit is contained in:
@@ -66,6 +66,18 @@ L["Frequently Asked Questions"] = true
|
||||
L["Warrior"] = true
|
||||
|
||||
L["GENERAL_FAQ"] = [[
|
||||
|cffffd200How is Omen3 different from Omen2?|r
|
||||
|
||||
Omen3 relies completely on the Blizzard threat API and threat events and does not attempt to calculate or extrapolate threat unlike in Omen2.
|
||||
|
||||
Omen2 used what we called the Threat-2.0 library, which was responsible for monitoring the combat log and your spellcasting for action you do, checking your buffs, debuffs, stances, talents and your gear for threat modifiers and then calculating your threat based on what was known or guessed from observed threat behavior. Stuff like knockbacks reducing tank aggro was just guessed (we assumed them to be mostly 50% reduction) but impossible to confirm.
|
||||
|
||||
Threat-2.0 then used the addon communication channel to transmit what it thought was your threat to the rest of the raid and Omen2 used this information for display.
|
||||
|
||||
Now Omen3 does none of these, it just shows exactly what Blizzard says everyone's threat is on mobX, there is no syncing, no combat log parsing, no guessing involved. This results in a significant amount of savings in network traffic (no syncing), CPU time (no combat log parsing) and memory used (50 kb vs over 1 mb). Gone are the days of boss modules being needed to be coded for threat for each specific boss, such as Nightbane wiping threat on landing (we used the /yell trigger Nightbane does).
|
||||
|
||||
The drawbacks? The frequency of the updates is much slower, and you can only obtain threat from a mob you are in direct combat with, and only if someone is targetting it in your party/raid. The benefits? You can now see threat of NPCs (think Human Kalecgos) on a mob, provided someone in the raid has them targetted.
|
||||
|
||||
|cffffd200Why does no threat data show on a mob when I target it even though it is in combat?|r
|
||||
|
||||
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 bandwidth.
|
||||
|
||||
Reference in New Issue
Block a user