excuse my really bad english
i asked in the german wow interface forum but nobody could help me
is it possible to bound the aggrobars of omen on the right side instead of left?
or which file or code must be rewritten to bound the bars on the right side?
Hi Galla -
There currently isn't any option to do this. I'll think about adding it though :)
Quote from Ikky »
I've been getting this error for a while now. Only happens when I gain or lose a buff. enUS WoW
Threat-1.0\Threat-1.0\ThreatClassModuleCore.lua:453: attempt to index field 'BuffModifiers' (a nil value)
What class and revision?
Quote from Harc »
Friday we had a strange situation:
All my guild uses only OMEN/Threat-1.0
One of tanks wasn't showing up on omen at all even he was able to see everybody else.( he wasn't able to see itself also)
We all had same version of Omen/Threat-1.0
Sounds like he had two copies of Threat fighting each other; I still haven't been able to track down this issue. Have him run a full WAU update and he should be fine.
Omen and KTM should place nicely side-by-side. The publishing priority goes like so:
Omen publishes to Omen
Omen publishes to KTM if KTM is not installed on the source computer
KTM publishes to KTM if KTM is installed on the source computer
KTM publishes to Omen if Omen is not installed on the source computer
The Crystalcore robots do indeed have a -threat knockback, IIRC. Is it always the shaman, or are other classes doing the same? It may be that shaman calculations are incorrect - for example, if Unleashed Rage is still generating some threat, that'd do it, since I'm not handling that.
Can you verify others' versions for me and see if they're up to date?
I just browsed through the threat-code . There are a few npc-modules for "old" content like zg and aq , but it's not complete. I'm missing Onyxia for example. Maybe people who visit these old places already know how to handle the fight without aggrometer, but i think threat should have all raidbosses and the worldbosses . And YES, i know this library is still under development ;)
The plan is to have them eventually, but we're hitting the highly-active content first.
As long as a KTM target is set, Omen's threat level should be in synch with KTM's threat level and should be useful information. I suspect that it wasn't, though, which resulted in the following:
* KTM displayed threat on Tidewalker + threat accumulated on all murloc adds for the duration of the fight.
* Omen displayed threat on Tidewalker only, maintaining a separate list for the murlocs.
When Threat-1.0 reports to KTM, it says "Here's the total aggro I have on all my targets in one big lump sum plus global threat." This is close to the number that KTM expects...until Omen's more advanced features get involved. One of the things that it does is wipe the murlocs' threat list in between phases, so that for each phase, you get an accurate threat list for the murlocs themselves. This throws off the lump sum sent to KTM, though, since KTM is just expecting a total for how much threat you've done in the fight to all targets, which is a relatively useless statistic.
In this case, KTM's data is broken. There's no way to know what percentage of the reported threat level is from Tidewalker, and what percentage is from murlocs; the only way this data is useful is if everyone does about the same amount of threat to the murlocs. Even in a KTM compatibility mode, you could easily pull aggro over the MT while showing less threat than the MT if the MT had generated a decent amount of threat on the murlocs and you'd generated little-to-none.
The solution is to ensure that a master target is always set. Using KTM in a multi-mob fight without a master target results in worthless data.