Authors CurseForge

If you click on a quest in your quest tracker it will open up a single pane instead of the normal double panel quest log and it's yellow text on yellow parchment, making it extremely difficult to read.

Talented skin seems to give an error as well. Blizzard also recently updated the dropdown for titles so that it uses a scrollbar now. Because of this, the character sheet frame is slightly bugged.

Is there any way to rearrange the data found when using an LDB display? Currently it shows MB/FPS/MS. I would like to see it be FPS/MS/MB if possible.

I'm getting tons of errors in the latest release, 1.2.4.

[2009/06/16 10:44:04-1654-x2]: Inquest-1.23\Core.lua:123: attempt to index upvalue 'InquestDataObject' (a nil value)
Inquest-1.23\QuestLog.lua:126: in function <Interface\AddOns\Inquest\QuestLog.lua:122>
(tail call): ?:
<in C code>: in function `QuestLog_Update'
Interface\FrameXML\QuestLogFrame.lua:57: in function <Interface\FrameXML\QuestLogFrame.lua:54>:

---

[2009/06/16 10:44:04-1654-x2]: Inquest-1.23\Core.lua:123: attempt to index upvalue 'InquestDataObject' (a nil value)
Inquest-1.23\QuestLog.lua:126: in function <Interface\AddOns\Inquest\QuestLog.lua:122>
(tail call): ?:
<in C code>: in function `QuestLog_Update'
Interface\FrameXML\QuestLogFrame.lua:57: in function <Interface\FrameXML\QuestLogFrame.lua:54>:

---
[2009/06/16 10:47:29-1655-x1]: Inquest-1.23\Core.lua:72: attempt to call method 'SetupOptions' (a nil value)
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0-5 (ButtonFacade):502: in function `InitializeAddon'
AceAddon-3.0-5 (ButtonFacade):614: in function <...dOns\ButtonFacade\Libs\AceAddon-3.0\AceAddon-3.0.lua:607>

---
[2009/06/16 10:47:31-1655-x3]: Inquest-1.23\Core.lua:123: attempt to index upvalue 'InquestDataObject' (a nil value)
Inquest-1.23\QuestLog.lua:126: in function <Interface\AddOns\Inquest\QuestLog.lua:122>
(tail call): ?:
<in C code>: in function `QuestLog_Update'
Interface\FrameXML\QuestLogFrame.lua:57: in function <Interface\FrameXML\QuestLogFrame.lua:54>:
<in C code>: in function `ExpandFactionHeader'
...bs\LibDogTag-Unit-3.0\Categories\TooltipScanning.lua:119: in function `func':
IceHUD-3\libs\LibDogTag-3.0\Events.lua:267: in function <...nterface\AddOns\IceHUD\libs\LibDogTag-3.0\Events.lua:260>

---
[2009/06/16 10:47:31-1655-x3]: Inquest-1.23\Core.lua:123: attempt to index upvalue 'InquestDataObject' (a nil value)
Inquest-1.23\QuestLog.lua:126: in function <Interface\AddOns\Inquest\QuestLog.lua:122>
(tail call): ?:
<in C code>: in function `QuestLog_Update'
Interface\FrameXML\QuestLogFrame.lua:57: in function <Interface\FrameXML\QuestLogFrame.lua:54>:
<in C code>: in function `CollapseFactionHeader'
...bs\LibDogTag-Unit-3.0\Categories\TooltipScanning.lua:125: in function `func':
IceHUD-3\libs\LibDogTag-3.0\Events.lua:267: in function <...nterface\AddOns\IceHUD\libs\LibDogTag-3.0\Events.lua:260>

---
[2009/06/16 10:47:31-1655-x3]: Inquest-1.23\Core.lua:123: attempt to index upvalue 'InquestDataObject' (a nil value)
Inquest-1.23\QuestLog.lua:126: in function <Interface\AddOns\Inquest\QuestLog.lua:122>
(tail call): ?:
<in C code>: in function `QuestLog_Update'
Interface\FrameXML\QuestLogFrame.lua:57: in function <Interface\FrameXML\QuestLogFrame.lua:54>:

---

I get a weird bug every so often. I'll try to get a screenshot of it when it happens again. Basically after a loading screen, my mana bar gets stuck as the red color even though I am in caster form (I play a Druid). I have to reload ui or shift into another form then back out for the color to fix itself.

Hey Jncl, do you mind skinning/fixing ExtendedQuestFrame?
http://wow.curse.com/downloads/wow-addons/details/eqf.aspx
With skinner enabled, the scroll bar is out of the frame. Here is a screenshot of the issue.
http://i39.tinypic.com/jikkky.jpg

Also, if you notice on the right side, the new Objectives Tracker frame is transparent. Is there anyway to skin this instead of making it transparent? If I disable skinner, the default frame style is applied to it.

Thanks!

[2009/04/16 23:27:18-1279-x6]: IceHUD-3\IceBarElement.lua:704: TexCoord out of range

---
Getting this on the latest build, 1.5.3

Anyone have a fix to get this working for 3.1?

The timer in the LDB if you set up that option doesn't update at all unless you hover over the icon/text to show the tooltip. Any way to fix this? No LUA error is given.

Weird error I get in witchunt when I try to go into the spellfilter. Spell filter is completely blank.

[2009/01/22 18:04:38-669-x1]: WitchHunt-3.0\WitchHunt.lua:346: attempt to concatenate local 'rank' (a nil value)
WitchHunt-3.0\WitchHunt.lua:382: in function <Interface\AddOns\WitchHunt\WitchHunt.lua:357>
AceConfigRegistry-3.0-6:303: in function `app'
AceConfigDialog-3.0-25:1655: in function `Open'
AceConfigDialog-3.0-25:1720: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1718>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceGUI-3.0-16 (ClosetGnome):267: in function `Fire'
...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:67: in function <...AceGUI-3.0\widgets\AceGUIWidget-BlizOptionsGroup.lua:66>:
<in C code>: in function `Show'
Interface\FrameXML\UIOptionsFrame.lua:28: in function <Interface\FrameXML\UIOptionsFrame.lua:17>:
<in C code>: in function `InterfaceOptionsList_DisplayPanel'
Interface\FrameXML\UIOptionsFrame.lua:46: in function `InterfaceOptionsListButton_OnClick':
<string>:"*:OnClick":2: in function <[string "*:OnClick"]:1>

---

Do you mind updating the achievement frame skin? they added a few things to the default ui for Achievements with the patch. Also, in SexyMap I use the Blizzard Tooltip Border texture as the border for my Minimap, but it doesn't get converted to the border you use for the majority of skinner. Would it require a skinning of the addon itself on your part (if so, I can deal with it, don't want to hassle you) or could I point it at a particular texture in the skinner files to achieve the same look?

Not sure if you still need these bug reports or not with that debugger error.

[2009/01/09 10:11:27-567-x1]: Skinner-b1.9183.22 \Skinner.lua:593: Not a StatusBar
Skinner-b1.9183.22 \Skinner.lua:593: in function `glazeStatusBar'
Skinner-b1.9183.22 \UIElements1.lua:217: in function <Interface\AddOns\Skinner\UIElements1.lua:187>
<in C code>: in function `pcall'
Skinner-b1.9183.22 \Skinner.lua:415: in function `checkAndRun'
Skinner-b1.9183.22 \AddonFrames.lua:16: in function <Interface\AddOns\Skinner\AddonFrames.lua:2>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Omen):144: in function <...rface\AddOns\Omen\Libs\AceTimer-3.0\AceTimer-3.0.lua:118>
:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Omen):144: in function <...rface\AddOns\Omen\Libs\AceTimer-3.0\AceTimer-3.0.lua:118>

---

[2009/01/07 21:03:24-561-x65]: CoolDownButtons-2.1.16 \Modules\Cooldown_Manager.lua:167: attempt to index field '?' (a nil value)
CoolDownButtons-2.1.16 \Modules\Button_Manager.lua:135: in function <...ce\AddOns\CoolDownButtons\Modules\Button_Manager.lua:115>

---

Not quite sure what this bug means. I get when one of my CDs starts to flash as if it is nearing completing its cooldown when it's not. It's an odd error.

[2009/01/07 14:29:55-560-x1]: Skinner-b1.9183.22 \Skinner.lua:593: Not a StatusBar
Skinner-b1.9183.22 \Skinner.lua:593: in function `glazeStatusBar'
Skinner-b1.9183.22 \UIElements1.lua:217: in function <Interface\AddOns\Skinner\UIElements1.lua:187>
<in C code>: in function `pcall'
Skinner-b1.9183.22 \Skinner.lua:415: in function `checkAndRun'
Skinner-b1.9183.22 \AddonFrames.lua:16: in function <Interface\AddOns\Skinner\AddonFrames.lua:2>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Procodile):144: in function <...e\AddOns\Procodile\lib\AceTimer-3.0\AceTimer-3.0.lua:118>
:
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0-5 (Procodile):144: in function <...e\AddOns\Procodile\lib\AceTimer-3.0\AceTimer-3.0.lua:118>

---

Looks like procodile isn't playing nice for some reason.

Just a quick question. Is it possible for recount to track procs? (avg ppm, # of procs, proc uptime, etc) and the uptime of de/buffs? I'm currently using several addons to track each one, but it would be great if recount could somehow do it.