Someone just put the Reliquary of Souls module I wrote into the Threat-1.0 lib. Only problem is that it DOES NOT WORK. It didn't work when I posted it. I was hoping some folks would help me test it and that I could get some peer review on the module.
For those who may be interested, I've written a simple interface to Threat-1.0 that shows information on your threat vs. targettarget's threat. It shows % of threat, delta of threat as well as estimated time to reach 100% threat with current TPS.
I've got a problem: Omen is visible, but doesn't show any bars, neither my own nor those of my party/pet. I also don't appear in my party's omen.
I'm not quite sure when this problem occurred, but I think it must have been when I updated Omen a few days ago (today's update didn't work too). I don't think I changed something within the configuration.
I already deleted all Omen-files and reinstalled. And I found out this problem exists with all my characters.
And I checked each option I thought could cause this. Omen is not in standby mode and is activated.
Edit: I found out Omen works again after disabling Recount. I now updated all my ace addons again but couldn't test it yet - the European login seems to be down.
Edit 2: After loading the latest updates it seems to be working again with Omen and Recount.
Threat-2.0 is undergoing internal testing by Antiarc, there's quite a bit of restructuring involved, part of which has to do with trying to avoid using Babble. It won't be made available until he is certain it works.
PTR will last at least 2 months anyway, there is no hurry.
Problem with Omen r60636 (with Threat-1.0 r61237, standalone) in a Kara raid last night in WoW 2.3.3 live. USEng client/server.
Am a main tank in the raid and sometime during it, the following error occurs. Can't be more exact on the timing or events; it was after the beginning though ;). During or after Moroes?
Dewdrop-2.0-56529 (DewdropLib):2813: attempt to perform arithmetic on local 'left' (a nil value)\nDewdrop-2.0-56529 (DewdropLib):2984: in function `Open'\nOmen-2.1r55025\\OmenDisplay.lua:359: in function <Interface\\AddOns\\Omen\\OmenDisplay.lua:353>
I did not make any adjustments to the Omen display during the raid; may have inadvertently clicked it, though.
Does anyone have any thoughts on why the Omen default profile is 'char' instead of 'Default'?
It makes packaging a UI that has Omen next to impossible.
I was under the impression that the best practice for Ace authors was to always code to 'Default' and let the user reclassify it as needed.
For now, I've just tweaked my update script to change this line:
Omen:RegisterDB("OmenDB", "OmenDBPC", "char")
to this line:
Omen:RegisterDB("OmenDB", "OmenDBPC", "Default")
Sure would be nice if someone changed this in the trunk. As it stands, you can't actually ship a named profile (e.g. Default) with positioning information in it and then let people use it. Since it is set to 'char', when they login with a new toon, Omen is back in it's as-coded position and skin. They can switch it to 'Default', but it doesn't seem to actually adopt the positions and settings in Default, instead opting to replace the Default profile with the as-coded defaults.
Not sure all that makes sense, but once again this blows from a collection packaging perspective and from the perspective of someone who has a lot of toons on a lot of realms.
Updated Omen the morning 2008-02-17, and that broke Omen for me, i can no lonegr see threat bars.
Since then i updated 4 times and omen was updated 3 times of those. The current version i have now is: 61752
I have deleted saved variables etc.
i get the following errors:
I get whenever i log a character in:
[2008/02/17 23:59:26-880-x1]: ...StatusHealer\libs\Threat-1.0\ThreatNPCModuleCore.lua:25: Cannot find a library instance of "LibBabble-Boss-3.0".:
!Swatter\Libs\SlideBar\SlideMain.lua:63: in function `LibStub'
...StatusHealer\libs\Threat-1.0\ThreatNPCModuleCore.lua:25: in function `v':
...dStatusHealer\libs\Threat-1.0\Threat-1.0-Cleanup.lua:35: in main chunk:
I get the following whenever in a party or raid.
[2008/02/17 21:03:00-872-x16]: Omen-2.1r61751\Omen.lua:528: Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
[2008/02/17 21:34:31-872-x1]: Omen-2.1r61751\Omen.lua:528: Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
<in C code>: in function `ClearTarget'
Interface\FrameXML\UIParent.lua:2405: in function `ToggleGameMenu':
<string>:"TOGGLEGAMEMENU":1: in function <[string "TOGGLEGAMEMENU"]:1>
[2008/02/17 21:38:00-873-x1]: Threat-1.0-61753 (GridStatusHealer):1867: attempt to compare nil with number
Omen-2.1r61751\OmenMenu.lua:79: in function `func'
Dewdrop-2.0-56529 (ItemSync):721: in function <...ace\AddOns\ItemSync\libs\Dewdrop-2.0\Dewdrop-2.0.lua:660>
[2008/02/18 00:11:42-1968-x1]: Omen-2.1r61751\Omen.lua:528: Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
[2008/02/18 00:11:45-1968-x1]: Omen-2.1r61751\Omen.lua:528: Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
<in C code>: in function `MoveBackwardStart'
<string>:"MOVEBACKWARD":2: in function <[string "MOVEBACKWARD"]:1>
[2008/02/18 00:12:48-1968-x4]: Threat-1.0-61753 (Threat-1.0):1469: AceComm-2.0: `SetCommPrefix' must be called before sending a message.
Ace2\AceLibrary\AceLibrary.lua:122: in function `error'
AceComm-2.0-60961 (Ace2):1503: in function <Interface\AddOns\Ace2\AceComm-2.0\AceComm-2.0.lua:1480>
(tail call): ?:
Threat-1.0-61753 (Threat-1.0):1469: in function `RequestThreatClear'
Omen-2.1r61751\OmenMenu.lua:89: in function `func'
Dewdrop-2.0-56529 (DewdropLib):721: in function <...erface\AddOns\DewdropLib\Dewdrop-2.0\Dewdrop-2.0.lua:660>
If you're updating with WAU, just make sure to grep it again and restart the game. (WAU should fetch all deps on its own)
If you don't use WAU, make sure you have a copy of LibBabble-Boss-3.0 and LibBabble-Spell-3.0.
I suppose all of you are running dis-embedded, because i just tried the embedded version of Omen and it worked fine.
Update all your mods using Threat-1.0, and make sure to restart your game!
(Also, if the error persist, maybe its the addons fault that includes Threat, i see GridStatus* for example here)