MazzleUI + Omen thread reporting issue

[MisterT]

Hi everybody!

My guild is using Omen instead of KTM for thread management. The RL asked me to switch to Omen since everybody use it except me. Omen is basically working but the reports are pretty damn wrong. You see, im a fire mage with decent gear and I see myself at position 10 or so on my Omen screen while everybody say im about to blow away the MT threat and it make me feel pretty damn noob . So far, ive been disabling Fubar KTM addon, KTM itself and KLH CPU thingy. Anyone have a clue of whats going on ?

Regards

[Zyonin]

Are you and the rest of guildies using the same version of Omen/Threat 1.0 (Threat 1.0 is the engine that Omen uses)? If you are using very different version, that can result in discrepancies. To make sure have everyone download and install the latest version either via this link http://files.wowace.com/Omen/Omen.zip or via your favorite updater such as WoW Ace Updater or WoW UI Updater.

[Mortlach]

An' dinna fergit m'personal fav'rit updater, jWoWUpdater.

Auto updates itself, can do fully automated updates and can handle non-ACE AddOns t'boot! An' only havin' tae explain one interface t'both Windows and OS X users makes guild texaport sae vera much easier!

--Mortie

[kythik]

I was having similar problems, but i ended up switching to Assessment.

[Zyonin]

Originally Posted by kythik I was having similar problems, but i ended up switching to Assessment.

Assessment works just fine for that role. The important thing is the back-end, Threat 1.0. This library is what does the actual work of collecting and processing threat data. Omen is just the graphical front end that displays the data. Assessment is another one. You can also use Violation and Pitbull to also display Theat 1.0 data. They may be others that I am forgetting. Just pick one and use it.