DHUD3
DHUD3
DHUD3 is a modular Heads Up Display Addon.
Core Module
Core functionality on which the other modules build up. Lets you set DHUD3 general settings (scale, situation alpha, font, etc). (More info)
Player Module
Bars to show Player and Target Health/Power information, and Target and Target of Target name plates. (More info)
Auras Module
Show player buffs and/or weapon enchants close to expiring. (More info)
Abilities Module
Show/track abilities specific to your class applied to your target (DoTs, HoTs, etc), or Death Knight runes.(More info)
Pet Module
Bars to display Pet's Health/Power information. You can also use them to show Vehicle/Player information when in a vehicle and/or to show druid mana while shape shifted. (More info)
Outer Module
Bars to display Focus' or Target of Target's Health/Power, and/or Threat information. (More info)
Cast Module
Bars to display PLayer and Target cast. The bars overlap with the Player Module. (More info)
TO DO
- Add more tracking posibilities to the Abilities Module.
- Bar's text and Name Plates "click through"
- Movable bars, or at least the options to increase the horizontal distance form the center (This one I am still thinking about)
Known Issues
Focusing using drop down menu is now a protected function. Using the focus option in DHUD3 drop-down menus will generate an error.
Can you elaborate on this? What do you mean with "default behavior"? Alphas have a precedence order:
5 = dead
4 = combat
3 = cast
2 = select (targeting)
1 = regeneration
0 = off combat
The higher ones will "override" lower ones. This means that out of combat alpha will only be used after you are out of combat, not casting, not targeting and stoped regenerating. Probably the name is missleading?
Foam
a) doesn't switch color appropriately (almost always)
b) assumes previous maximum, leading to 100 Energy/Rage displaying the bar as filled with 100/6000 Mana (often).
That's the issue I am having at least.
Fixed bug when hidding blizz target frame
Foam
is there a way to disable Bliz Cast bar, or are you planing to something alike?
Thanks
There is an option in the cast options menu to disable wow cast bar. Canyou check it's working?
Foam
Secondly, I'm getting the following error - Unfortunateley I don't know what triggers it. as it seems to just pop up.
Message: ...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:24: attempt to concatenate field '?' (a nil value)
Time: 10/16/10 09:42:36
Count: 1
Stack: (tail call): ?
...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:24: in function <...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:23>
...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:48: in function <...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:40>
[string "safecall Dispatcher[4]"]:4: in function <[string "safecall Dispatcher[4]"]:4>
[C]: ?
[string "safecall Dispatcher[4]"]:13: in function `?'
...ags\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...alBot\Libs\LibTalentQuery-1.0\LibTalentQuery-1.0.lua:148: in function `Query'
Interface\AddOns\HealBot\HealBot.lua:4284: in function `HealBot_TalentQuery'
Interface\AddOns\HealBot\HealBot.lua:1146: in function `HealBot_OnUpdate'
[string "*:OnUpdate"]:1: in function <[string "*:OnUpdate"]:1>
Locals: Sometimes debuglocals() returns nothing, it's one of those times... (FYI: This last sentence (only) is a HotFix from Decursive to prevent a C stack overflow in the new Blizzard error handler and thus giving you the opportunity to send this debug report to the author of the problematic add-on so he/she can fix it)
Message: ...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:24: attempt to concatenate field '?' (a nil value)
Time: 10/16/10 09:43:25
Count: 1
Stack: (tail call): ?
...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:24: in function <...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:23>
...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:48: in function <...\DHUD3\Libs\LibDogTag-Unit-3.0\Categories\Talent.lua:40>
[string "safecall Dispatcher[4]"]:4: in function <[string "safecall Dispatcher[4]"]:4>
[C]: ?
[string "safecall Dispatcher[4]"]:13: in function `?'
...ags\libs\CallbackHandler-1.0\CallbackHandler-1.0.lua:92: in function `Fire'
...alBot\Libs\LibTalentQuery-1.0\LibTalentQuery-1.0.lua:148: in function `Query'
Interface\AddOns\HealBot\HealBot.lua:4284: in function `HealBot_TalentQuery'
Interface\AddOns\HealBot\HealBot.lua:1104: in function `HealBot_OnUpdate'
[string "*:OnUpdate"]:1: in function <[string "*:OnUpdate"]:1>
Locals: Sometimes debuglocals() returns nothing, it's one of those times... (FYI: This last sentence (only) is a HotFix from Decursive to prevent a C stack overflow in the new Blizzard error handler and thus giving you the opportunity to send this debug report to the author of the problematic add-on so he/she can fix it)
The thing with ace libs is that one addon loads them and the rests uses them. That is why an error generated by healbot seems to come form DHUD3.
Foam
I've been using metahud for a few years (now dead), and I must say that I like this way better already. Initial setup was a breeze, had everything set up just the way I wanted in a matter of minutes. Works great, looks great, has everything I need :D
One thing I would love to see in a future update is an option for Center Spacing to allow me to bring the bars closer together and not just further apart.
My new favorite addon!
The combo points (if not other abilities) are not placing correctly. When I scaled them down, they moved to inside the bar.
Otherwise yes, fps issues fixed wonderful!
Foam
Let me appologize for the current "unusable" state of the addon. Time is not something I really have atm, but I am commited to making this version stable for 4.0.1 as sson as possible (this weekend).
Sorry for any inconveniences,
Foam
bars are grey and always "full"