Debuff colouring is a bit pointless, because it only shows your own buffs/debuffs not anyone elses. Highlighted target is already implemented.
One thing I'd like to see, is, say you have a maximum of 5 bars showing. You have about 7 bars running for all different targets, it would be nice that when you changed targets, all the timers for that target get "put to the top" so to say.
Also, what time format does the addon use, on the time thing whatever number I put it it always filters out every buff/debuff. I thought it was seconds..
When I tried to switch profile I got this error message:
"LibBars-1.0\\LibBars-1.0.lua:704: attempt to perform arithmetic on field 'orientation' (a nil value)
LibBars-1.0\\LibBars-1.0.lua:748: in function `SetOrientation'
Yatba-r81047\\Yatba.lua:1789: in function `InitializeGroup'
Yatba-r81047\\Yatba.lua:560: in function `?'
CallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>
<string>:\"safecall Dispatcher[3]\":4: in function <[string \"safecall Dispatcher[3]\"]:4>
<in C code>: ?
<string>:\"safecall Dispatcher[3]\":13: in function `?'
CallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'
AceDB-3.0\\AceDB-3.0.lua:169: in function <Interface\\AddOns\\Ace3\\AceDB-3.0\\AceDB-3.0.lua:158>\nAceDB-3.0\\AceDB-3.0.lua:355: in function `SetProfile'
AceDBOptions-3.0\\AceDBOptions-3.0.lua:181: in function <...ce\\AddOns\\Ace3\\AceDBOptions-3.0\\AceDBOptions-3.0.lua:180>\n(tail call): ?:
...:
<string>:\"safecall Dispatcher[3]\":9: in function <[string \"safecall Dispatcher[3]\"]:", -- [1]
"5>
(tail call): ?:
AceGUI-3.0\\AceGUI-3.0.lua:257: in function `Fire'
...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:423: in function <...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:414>:
(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'
...3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown-Items.lua:333: in function <...3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown-Items.lua:328>:
---", -- [2]
Fresh install, it was my first attempt to configure Yatba.
Debuff colouring is a bit pointless, because it only shows your own buffs/debuffs not anyone elses.
Anyway, that shouldn't be to hard to add and I knew it was coming.
Quote from Elarenda »
One thing I'd like to see, is, say you have a maximum of 5 bars showing. You have about 7 bars running for all different targets, it would be nice that when you changed targets, all the timers for that target get "put to the top" so to say.
Good idea.
Quote from Elarenda »
Also, what time format does the addon use, on the time thing whatever number I put it it always filters out every buff/debuff. I thought it was seconds..
It is. I worked on the filtering code recently (notice the unit filter changes). I'll recheck it...
First, I really liking this addon. You've definitely put a lot of thought into its design. The only problem I'm having is the header bar showing incorrect health. I don't think anyone else has mentioned it yet. Sorry if I missed it. Only seems to happen on my shaman that I can tell. Or it just might be more obvious as my main is a lock :). Say my shaman is down to 75% health and I heal. The bar will still display 75% even though I'm at full health. I haven't tested with the revisions you made today as I haven't had a chance to get on(trying after I type this up). I'll also keep a closer watch on my warlock and see if I get similar results.
Ok, I got a chance to take some screenshots. The first one is the problem I noted in the above post. The second is something I noticed while testing on my warlock. Basically mount and unmounting will cause the stacking that's show in the screenshot. I had my duration set high while I was configuring it so this problem really isn't a huge deal since I've lowered my max duration and that aura is no longer tracked. I'm tired so I hope that made sense :)
Also, the problem that I was having on my shaman does not happen with my warlock. Thinking back I don't think I tried to use bandages on my shaman to see if the problem still arises. I'll check that out if you need me to.
I got the time to test the addon and liked it, but can't really use. Is there buff/debuff filtering planned? For example whitelist and blacklist - if you add something to the whitelist, then only those effects show for the selected group, if you add blacklist - all but those mentioned. For example I don't want to see the 40 debuffs on the boss, but only the few ones that are worth to me. Can be done as fixed list or learning mode, I guess fixed list is easier and less cpu consuming
For example I don't want to see the 40 debuffs on the boss, but only the few ones that are worth to me.
Did you put 40 debuffs on the boss alone ? Else there is a bug. You should only see the auras you applied yourself. Were you testing it on WotLK beta ?
Quote from DrunkenDonkey »
Can be done as fixed list or learning mode, I guess fixed list is easier and less cpu consuming
Whenever the list is fixed (i.e. hard-coded) or user-defined, the CPU usage stays the same. In contrary, if the list was fixed, I would have to write it, what I'm too lazy to do ATM.
Speaking of white/blacklisting, in WotLK, we will be able to see the duration of every buffs and debuffs on the units. Actually Yatba should filter out those you have not cast. What I plan is this :
There will be the possibility to register auras (at hand, using names or spell ids) for whitelisting or blacklisting at global level. For each of these aura, you have three choice : completely ignore it (global blacklisting), display it in every group (global whitelisting), or enable group-specific setting. The latter will have the aura displayed in each group filtering panel.
And there will be one special case : "buffs and debuffs I have applied", which will be globally whitelisted by default.
When I tried to switch profile I got this error message:
"LibBars-1.0\\LibBars-1.0.lua:704: attempt to perform arithmetic on field 'orientation' (a nil value)
LibBars-1.0\\LibBars-1.0.lua:748: in function `SetOrientation'
Yatba-r81047\\Yatba.lua:1789: in function `InitializeGroup'
Yatba-r81047\\Yatba.lua:560: in function `?'
CallbackHandler-1.0\\CallbackHandler-1.0.lua:146: in function <...Ons\\Ace3\\CallbackHandler-1.0\\CallbackHandler-1.0.lua:146>
<string>:\"safecall Dispatcher[3]\":4: in function <[string \"safecall Dispatcher[3]\"]:4>
<in C code>: ?
<string>:\"safecall Dispatcher[3]\":13: in function `?'
CallbackHandler-1.0\\CallbackHandler-1.0.lua:91: in function `Fire'
AceDB-3.0\\AceDB-3.0.lua:169: in function <Interface\\AddOns\\Ace3\\AceDB-3.0\\AceDB-3.0.lua:158>\nAceDB-3.0\\AceDB-3.0.lua:355: in function `SetProfile'
AceDBOptions-3.0\\AceDBOptions-3.0.lua:181: in function <...ce\\AddOns\\Ace3\\AceDBOptions-3.0\\AceDBOptions-3.0.lua:180>\n(tail call): ?:
...:
<string>:\"safecall Dispatcher[3]\":9: in function <[string \"safecall Dispatcher[3]\"]:", -- [1]
"5>
(tail call): ?:
AceGUI-3.0\\AceGUI-3.0.lua:257: in function `Fire'
...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:423: in function <...ns\\Ace3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown.lua:414>:
(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'
...3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown-Items.lua:333: in function <...3\\AceGUI-3.0\\widgets\\AceGUIWidget-DropDown-Items.lua:328>:
---", -- [2]
Fresh install, it was my first attempt to configure Yatba.
Same here: fresh install, first attempt to configure addon...
Just downloaded and getting this error while trying to set up the bars, I can't adjust the priority slider or check the different boxes for which unit types to include.
Interface\AddOns\Yatba\Yatba.lua:1667: attempt to call global 'groupOptionSetter' (a nil value)
(tail call): ?
Interface\AddOns\Yatba\Yatba.lua:1667: in function <Interface\AddOns\Yatba\Yatba.lua:1666>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:775: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:594>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:823: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:815>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...ddOns\AckisRecipeList\libs\AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...List\libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:47: in function <...List\libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:40>
I have solo tested, not dared doing raid test, so I wrongly assumed I will see all the debuffs on the mob, my bad. However, I'm thinking what I need may just be out of the scope of the addon :(
As a rogue, I want to have several groups of timers for:
1. Important buffs on me - filtered list where I only select to show the viable raid buffs - so it does not get huge, but allow me to check fast what buffs I have and what I'm missing
2. Debuffs on me
3. Small group of 2 bars - 1 is Slice & Dice buff and the other - Rupture debuff on target - this is what I base my combat cycle on
4. Important boss debuffs - selected list of debuffs to show on the boss, both mine and applied by the others, that include mele viable debuffs and my poisons
5. Important combat buffs on me - small selected list of buffs that contains for example my trinket and sword procs, heroism, AR, BF, etc - it allows me to precisely use cooldowns when they will do best job - stacking haste abilities with AP procs for example
So yeah, 5 bar groups with quite a mixed stuff in, I'm not asking you to do it, just informative if similar capabilities are in your plans for the future ;)
1. Important buffs on me - filtered list where I only select to show the viable raid buffs - so it does not get huge, but allow me to check fast what buffs I have and what I'm missing
2. Debuffs on me
3. Small group of 2 bars - 1 is Slice & Dice buff and the other - Rupture debuff on target - this is what I base my combat cycle on
4. Important boss debuffs - selected list of debuffs to show on the boss, both mine and applied by the others, that include mele viable debuffs and my poisons
5. Important combat buffs on me - small selected list of buffs that contains for example my trinket and sword procs, heroism, AR, BF, etc - it allows me to precisely use cooldowns when they will do best job - stacking haste abilities with AP procs for example
(Let "aura" mean "buff and/or debuff")
On live servers, there is no possibility to get duration of others' auras on anyone but yourself. I could have Yatba to scan the auras on yourself but this will become obsolete when 3.0.2 hits live. Nevertheless, for the auras you apply yourself, I think your setup could be doable with the filtering I plan but this will need a lot of fine tuning.
I admit this addon is primarily focused on druids and locks, who cast lots of hots/dots/debuffs.
I saw it mentioned in an earlier post, but I'm not sure it was noticed so I'll re-mention it, as I find it pretty important.
Being able to show Raid Icons for mob grouping, maybe instead of the portrait, would be very nice.
Anyone have feedback on how this compares to Classtimers?
ClassTimer has a specific list on what it tracks. It can also add buff names, sort of "opt-in" which is good to add specific procs you'd like to see. It only tracks stuff on you/target/focus.
Yatba tracks every buff/debuff and proc, and also tracks on multiple targets. You can filter out with time/units and upcoming blacklist, sort of "opt-out".
Personally, I think atm ClassTimer is better for my Rogue, while Yatba is better for my Priest.
[2008/08/31 10:49:14-1999-x1]: Yatba-r81181\Options.lua:296: attempt to index global 'notdb' (a nil value)
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:242: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:190>
(tail call): ?:
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1032: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1022>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1049: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1022>
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1461: in function `FeedGroup'
AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1383: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:1362>
(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'
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:424: in function `SetSelected':
...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:93: in function <...s\Ace3\AceGUI-3.0\widgets\AceGUIWidget-TreeGroup.lua:89>:
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
One thing I'd like to see, is, say you have a maximum of 5 bars showing. You have about 7 bars running for all different targets, it would be nice that when you changed targets, all the timers for that target get "put to the top" so to say.
Also, what time format does the addon use, on the time thing whatever number I put it it always filters out every buff/debuff. I thought it was seconds..
Fresh install, it was my first attempt to configure Yatba.
Anyway, that shouldn't be to hard to add and I knew it was coming.
Good idea.
It is. I worked on the filtering code recently (notice the unit filter changes). I'll recheck it...
@Ydrisselle: fixed in r81086.
Again, thanks a lot for this wonderful addon!
Also, the problem that I was having on my shaman does not happen with my warlock. Thinking back I don't think I tried to use bandages on my shaman to see if the problem still arises. I'll check that out if you need me to.
Thanks again!!!
For the health bug, I just committed a new scanning and refreshing code, please check the revision 81095.
Did you put 40 debuffs on the boss alone ? Else there is a bug. You should only see the auras you applied yourself. Were you testing it on WotLK beta ?
Whenever the list is fixed (i.e. hard-coded) or user-defined, the CPU usage stays the same. In contrary, if the list was fixed, I would have to write it, what I'm too lazy to do ATM.
Speaking of white/blacklisting, in WotLK, we will be able to see the duration of every buffs and debuffs on the units. Actually Yatba should filter out those you have not cast. What I plan is this :
There will be the possibility to register auras (at hand, using names or spell ids) for whitelisting or blacklisting at global level. For each of these aura, you have three choice : completely ignore it (global blacklisting), display it in every group (global whitelisting), or enable group-specific setting. The latter will have the aura displayed in each group filtering panel.
And there will be one special case : "buffs and debuffs I have applied", which will be globally whitelisted by default.
Same here: fresh install, first attempt to configure addon...
Interface\AddOns\Yatba\Yatba.lua:1667: attempt to call global 'groupOptionSetter' (a nil value)
(tail call): ?
Interface\AddOns\Yatba\Yatba.lua:1667: in function <Interface\AddOns\Yatba\Yatba.lua:1666>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[2]"]:9: in function <[string "safecall Dispatcher[2]"]:5>
(tail call): ?
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:775: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:594>
...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:823: in function <...nfig-3.0\AceConfigDialog-3.0\AceConfigDialog-3.0.lua:815>
(tail call): ?
[C]: ?
[string "safecall Dispatcher[3]"]:9: in function <[string "safecall Dispatcher[3]"]:5>
(tail call): ?
...ddOns\AckisRecipeList\libs\AceGUI-3.0\AceGUI-3.0.lua:257: in function `Fire'
...List\libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:47: in function <...List\libs\AceGUI-3.0\widgets\AceGUIWidget-Slider.lua:40>
@Shinja: I deleted my savedvariables to test a "fresh install" but I could not reproduce this bug.
I have solo tested, not dared doing raid test, so I wrongly assumed I will see all the debuffs on the mob, my bad. However, I'm thinking what I need may just be out of the scope of the addon :(
As a rogue, I want to have several groups of timers for:
1. Important buffs on me - filtered list where I only select to show the viable raid buffs - so it does not get huge, but allow me to check fast what buffs I have and what I'm missing
2. Debuffs on me
3. Small group of 2 bars - 1 is Slice & Dice buff and the other - Rupture debuff on target - this is what I base my combat cycle on
4. Important boss debuffs - selected list of debuffs to show on the boss, both mine and applied by the others, that include mele viable debuffs and my poisons
5. Important combat buffs on me - small selected list of buffs that contains for example my trinket and sword procs, heroism, AR, BF, etc - it allows me to precisely use cooldowns when they will do best job - stacking haste abilities with AP procs for example
So yeah, 5 bar groups with quite a mixed stuff in, I'm not asking you to do it, just informative if similar capabilities are in your plans for the future ;)
(Let "aura" mean "buff and/or debuff")
On live servers, there is no possibility to get duration of others' auras on anyone but yourself. I could have Yatba to scan the auras on yourself but this will become obsolete when 3.0.2 hits live. Nevertheless, for the auras you apply yourself, I think your setup could be doable with the filtering I plan but this will need a lot of fine tuning.
I admit this addon is primarily focused on druids and locks, who cast lots of hots/dots/debuffs.
Being able to show Raid Icons for mob grouping, maybe instead of the portrait, would be very nice.
ClassTimer has a specific list on what it tracks. It can also add buff names, sort of "opt-in" which is good to add specific procs you'd like to see. It only tracks stuff on you/target/focus.
Yatba tracks every buff/debuff and proc, and also tracks on multiple targets. You can filter out with time/units and upcoming blacklist, sort of "opt-out".
Personally, I think atm ClassTimer is better for my Rogue, while Yatba is better for my Priest.