Question , why do I see alot of people posting here with issues with showing Threat 2.0 as 2nd addon when the library is built directly into Omen2 , I was under impression u only needed threat 2.0 if u werent running omen2 to show up on peoples omen2 addon correctly , clarification please?
Also really like the changes to the gui , tonight all night in hyjal we had issues with half the raid not being able to see each other. We had 4 people who deleted there WTF files , omen / threat 2.0. Went an downloaded just Omen2 and it showed up in addon tab as enabled , in game no omen /omen config did nothing. Other 1/2 the raid had could only see 4-5 people on single target mode on threat on mobs. Im a tank , I saw the whole night on trash only myself - 1 mage - 1 healer. Version check randomly keep showing more an more people with Omen2 installed , but no one had reloged or added it , it just somehow keep updating who had it installed. Start of raid I saw 5 people , 10 mins later sitting there buffing an waiting for last healer , it showed 18 no idea on that.
Anyways overall after a few small bug fix's this will be far superior to first omen. Thank you for great work , but in its current state is very unreliable an buggy.
Getting an error that omen, and mapster can't find the library called acedboptions-3.0
This library is not visible in the WAU however...
[2008/03/29 09:57:26-4875-x1]: Omen-Omen r66676 / Threat-2.0 r66721\Omen.lua:61: Cannot find a library instance of "AceDBOptions-3.0".
Ace2\AceLibrary\AceLibrary.lua:49: in function `LibStub'
Omen-Omen r66676 / Threat-2.0 r66721\Omen.lua:61: in function <Interface\AddOns\Omen\Omen.lua:19>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher":9: in function <[string "safecall Dispatcher"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:316: in function `InitializeAddon'
AceAddon-3.0\AceAddon-3.0.lua:404: in function <...ce\AddOns\Mapster\Libs\AceAddon-3.0\AceAddon-3.0.lua:397>
I do have one issue though with SharedMedia, I installed it to get the option to choose other textures than the Blizzard one.
Without SharedMedia installed, BugSack reports no errors.
With Shared Media installed, I get a lot of errors with Omen2, BugSack reports 79 errors then.
[2008/03/29 15:14:52-41-x79]: Omen\Frame.lua:180: attempt to index field 'Anchor' (a nil value)
CallbackHandler-1.0\CallbackHandler-1.0.lua:146: in function <...men\Libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:146>
<string>:"safecall Dispatcher":4: in function <[string "safecall Dispatcher"]:4>
<in C code>: ?
<string>:"safecall Dispatcher":13: in function `?'
CallbackHandler-1.0\CallbackHandler-1.0.lua:91: in function `Fire'
LibSharedMedia-3.0\LibSharedMedia-3.0.lua:153: in function `Register'
SharedMedia\Core.lua:36: in function <Interface\AddOns\SharedMedia\Core.lua:30>
SharedMedia is installed in the Addons folder, so it's on the same level as Omen itself. Am I the only one getting these errors?
Thanks for this great AddOn and all your work.
Hope I can help to make it better, by posting some issues. Hope you can understand my bad English.
We had yesterday our first raid in SSC after the patchday.
All members used the 66721 version of the thread library and a German client.
We had two issues, one more general and one error.
In single target mode:
If we attacked mobs that switched targets for one special attack and than back to the tank, the tank was very often deleted from the aggro list. Also the target of the special attack had the aggro for omen instead of the tank, so many damagedealers got warnings because of the wrong target of target in omen.
Having a problem myself - Omen2 doesn't seem to be tracking hunter pet growls. Watching the meter it's as if the pet is just hitting the mob, but I can dps as usual ... and just kind of wonder when it'll be before the mob turns and charges me.
I keep getting a VERY loud Popping/explosion noise whenever I pass 90% threat on, seemingly, pretty much anyone. It's REALLY annoying and I can't find any way to turn it off, turn it down, or change the warning. Any help?
I've narrowed it to Omen 2. When Turned off, no noise gets made.