Did anyone ever figure out a fix for pet health bar color not updating to happiness level changes except via respawning it (i.e. dismiss/summon or mount/dismount)?
Works great otherwise, I really like it.
Edit:
Actually, looks like it sorta happens in other situations too. For example, I was invited to a group by a Pally so there was a Pally bar in the Party UF area, then he invited a hunter and both bars were pink until I /rl'd.
Got this error message when I disabled the cast bar (so much so that BugStack stopped watching for a while):
[2008/07/22 07:17:05-94-x1000]: ag_Extras-09-19-07\castbar\castbar.lua:207: attempt to index field 'CastBar' (a nil value)
ag_Extras-09-19-07\castbar\castbar.lua:38: in function <Interface\AddOns\ag_Extras\castbar\castbar.lua:38>
I haven't looked at the code just yet, but if I get some time I'll see about a patch.
Got this error message when I disabled the cast bar (so much so that BugStack stopped watching for a while):
[2008/07/22 07:17:05-94-x1000]: ag_Extras-09-19-07\castbar\castbar.lua:207: attempt to index field 'CastBar' (a nil value)
ag_Extras-09-19-07\castbar\castbar.lua:38: in function <Interface\AddOns\ag_Extras\castbar\castbar.lua:38>
I haven't looked at the code just yet, but if I get some time I'll see about a patch.
This was after I had loaded the addon, and then turned off the casting bar for player.
Recently checked out the Ace3 branch again to have a look see. Pleasantly surprised to find a sleek but well rounded addon lurking there. I don't really understand why you haven't pulled this to trunk?
The only item I missed was an energy ticker. A bit of frantic researching found me this http://www.wowinterface.com/downloads/info8810-TickTock.html, just adjust the size to match your aguf energy bar, drag it over the top, turn off the various text options and most importantly choose Outline texture. Voila, you now have a working fully (aesthetically speaking) integrated energy ticker in aguf, props to Kergoth for his nice work on TickTock. Also props to Andreasg for his typically impressive work on aguf.
If I put Auras on the left or right side they become static in size. Whatever number of rows/columns I use they stay the same size (bit to small for me). Changing to below/above makes them scale.
I hope that Auras become splittable, because personally I'd like buffs/debuffs on different positions.
I assume andreasg would know the answer to this. I'd like to add container frame (I assume this would be the best way to do it) for all of the unit frame. What we want to do is have ZMobDB for the 3D models instead of just the portrait, and move the text (and add additional text items) to the right of the model so it roughly would look something like what's in the png attachment.
Would a new module work for this, or would I need to (or could I) do the whole thing inside a custom layout?
I think this was asked before, but I haven't found an answer to it. I'm using the Ace 3 version from the SVN, and I'm really liking it so far, however about the only feature I can't seem to find is the "Tapped" status for Target.
Its pretty important to know when a target is tapped or not, am I just overlooking this in the buried options or has it not been added yet?
I think the health bars turn grey if the target is tapped... I think.. just going off memory not running on coffee.
They don't for me, just tested it a couple minutes ago.
Also get this error on occasion:
[2008/08/06 12:10:28-190-x1]: ag_Extras-09-19-07\fivesecond\fivesecond.lua:79: attempt to index field 'ManaBar' (a nil value)
ag_UnitFrames-09-19-07\ag_UnitClass.lua:134: in function `ExecModuleMethods'
ag_UnitFrames-09-19-07\ag_UnitClass.lua:314: in function `ApplyLayout'
ag_UnitFrames-09-19-07\modules\powerbar\powerbar.lua:111: in function <...e\AddOns\ag_UnitFrames\modules\powerbar\powerbar.lua:104>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:395: in function <...s\AckisRecipeList\libs\AceAddon-3.0\AceAddon-3.0.lua:388>
(tail call): ?:
ag_Options-09-19-07\ag_Options.lua:1007: in function <Interface\AddOns\ag_Options\ag_Options.lua:1003>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:775: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:594>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:829: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:828>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...st\libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51: in function <...st\libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47>:
I think this was asked before, but I haven't found an answer to it. I'm using the Ace 3 version from the SVN, and I'm really liking it so far, however about the only feature I can't seem to find is the "Tapped" status for Target.
Its pretty important to know when a target is tapped or not, am I just overlooking this in the buried options or has it not been added yet?
It works for "new" targets but the current one doesnt update
Another small feature I miss, was previously using StellarUF and it has a small number on your unit frame (similar to where agUF puts the pvp icon) that designates which raid group you are in. Its not a huge thing by any means, its just kind of nice to know at a quick glance what group you're in.
Aguf works without problems most of the time, but sometimes aguf goes into error mode and throws bunch of errors. If i restart it can then be fine afterwards. Below is just and example of an error I got in bugsack.
[2008/08/11 17:26:24-1117-x14]: ag_Unitframes-09-19-07\modules\healthbar\healthbar.lua:344: attempt to index field 'HealthBar' (a nil value)
ag_Unitframes-09-19-07\modules\healthbar\healthbar.lua:205: in function <...AddOns\ag_Unitframes\modules\healthbar\healthbar.lua:161>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:140: in function <Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:114>
---
Aguf works without problems most of the time, but sometimes aguf goes into error mode and throws bunch of errors. If i restart it can then be fine afterwards. Below is just and example of an error I got in bugsack.
[2008/08/11 17:26:24-1117-x14]: ag_Unitframes-09-19-07\modules\healthbar\healthbar.lua:344: attempt to index field 'HealthBar' (a nil value)
ag_Unitframes-09-19-07\modules\healthbar\healthbar.lua:205: in function <...AddOns\ag_Unitframes\modules\healthbar\healthbar.lua:161>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[2]":9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?:
AceTimer-3.0\AceTimer-3.0.lua:140: in function <Interface\AddOns\Ace3\AceTimer-3.0\AceTimer-3.0.lua:114>
---
Could you just before line 344 in ag_Unitframes\modules\healthbar\healthbar.lua insert the following, and tell me what it prints when you get the error:
if not self.bars.HealthBar then
ChatFrame1:AddMessage(self.name)
end
This is regarding the WotLK beta branch. I've only had limited opportunity to try it out (effin' downtime!) but the cooldown of auras weren't working earlier. OmniCC would put "4d", I assumed the d was for days, regardless of what buff/debuff I put on.
But I changed line 434 in auras.lua to
local startCooldownTime = timeLeft - duration
and it seems to be working for me now. No other errors so far for me as a pally in beta.
Just curious if an in game editor of any kind will be made for this (before or after wotlk).
Trying to figure out how to add a bar, text areas, etc is more of a pain than I can spend time on right now.
Andreas pretty much has said this will be done using functions in LUA, much the same way as oUF. Bascially if you want a different kind of layout or whatnot for the bars, you have to either create it yourself or get someone who knows LUA to do it.
Layouts will be able to provide options that will integrate into the options frame though, so this mean that you will be able to set the bar heights or bar order through the GUI.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Works great otherwise, I really like it.
Edit:
Actually, looks like it sorta happens in other situations too. For example, I was invited to a group by a Pally so there was a Pally bar in the Party UF area, then he invited a hunter and both bars were pink until I /rl'd.
[2008/07/22 07:17:05-94-x1000]: ag_Extras-09-19-07\castbar\castbar.lua:207: attempt to index field 'CastBar' (a nil value)
ag_Extras-09-19-07\castbar\castbar.lua:38: in function <Interface\AddOns\ag_Extras\castbar\castbar.lua:38>
I haven't looked at the code just yet, but if I get some time I'll see about a patch.
This was after I had loaded the addon, and then turned off the casting bar for player.
The only item I missed was an energy ticker. A bit of frantic researching found me this http://www.wowinterface.com/downloads/info8810-TickTock.html, just adjust the size to match your aguf energy bar, drag it over the top, turn off the various text options and most importantly choose Outline texture. Voila, you now have a working fully (aesthetically speaking) integrated energy ticker in aguf, props to Kergoth for his nice work on TickTock. Also props to Andreasg for his typically impressive work on aguf.
I hope that Auras become splittable, because personally I'd like buffs/debuffs on different positions.
Would a new module work for this, or would I need to (or could I) do the whole thing inside a custom layout?
Its pretty important to know when a target is tapped or not, am I just overlooking this in the buried options or has it not been added yet?
I think the health bars turn grey if the target is tapped... I think.. just going off memory not running on coffee.
They don't for me, just tested it a couple minutes ago.
Also get this error on occasion:
[2008/08/06 12:10:28-190-x1]: ag_Extras-09-19-07\fivesecond\fivesecond.lua:79: attempt to index field 'ManaBar' (a nil value)
ag_UnitFrames-09-19-07\ag_UnitClass.lua:134: in function `ExecModuleMethods'
ag_UnitFrames-09-19-07\ag_UnitClass.lua:314: in function `ApplyLayout'
ag_UnitFrames-09-19-07\modules\powerbar\powerbar.lua:111: in function <...e\AddOns\ag_UnitFrames\modules\powerbar\powerbar.lua:104>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[1]":9: in function <[string "safecall Dispatcher[1]"]:5>
(tail call): ?:
AceAddon-3.0\AceAddon-3.0.lua:395: in function <...s\AckisRecipeList\libs\AceAddon-3.0\AceAddon-3.0.lua:388>
(tail call): ?:
ag_Options-09-19-07\ag_Options.lua:1007: in function <Interface\AddOns\ag_Options\ag_Options.lua:1003>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:775: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:594>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:829: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:828>
(tail call): ?:
<in C code>: ?
<string>:"safecall Dispatcher[3]":9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?:
AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...st\libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:51: in function <...st\libs\AceGUI-3.0\widgets\AceGUIWidget-CheckBox.lua:47>:
Could you just before line 344 in ag_Unitframes\modules\healthbar\healthbar.lua insert the following, and tell me what it prints when you get the error:
if not self.bars.HealthBar then
ChatFrame1:AddMessage(self.name)
end
But I changed line 434 in auras.lua to
and it seems to be working for me now. No other errors so far for me as a pally in beta.
Trying to figure out how to add a bar, text areas, etc is more of a pain than I can spend time on right now.
Andreas pretty much has said this will be done using functions in LUA, much the same way as oUF. Bascially if you want a different kind of layout or whatnot for the bars, you have to either create it yourself or get someone who knows LUA to do it.