Download
(654Kb)
Download
Updated: 12-19-09 12:31 PM
Pictures
File Info
Updated:12-19-09 12:31 PM
Created:10-23-08 07:07 PM
Downloads:119,604
Favorites:253
MD5:

MetaHud - Nuckin Branch  Popular! (More than 5000 hits)

Version: v30300-8.5
by: Nuckin [More]

MetaHud - Nuckin Branch is a Heads Up Display Add-on for World of Warcraft 3.0 and above. It is a continuation of the original MetaHud by MetaHawk which was discontinued after Patch 2.4.3.

Although MH-Nuckin is a continuation, it isn't the same. MH-Nuckin is focused on remaining encapsulated as a self sustaining Add-on without requiring other libraries. As thus, its feature set differs from MetaHud's.

As of v30100-8.0, MetaHud - Nuckin Branch no longer includes a cast bar. I suggest using my stand alone cast bar called Circle Cast.

MetaHud - Nuckin Branch Features: (as of v30100-8.0)

  • Curved Verticle Health, Mana, Rage, Energy, and Runic Power bars for Player, Target, and Pets.
  • Target's Target Name and Health Bar.
  • Reskinnable Bar Backgrounds.
  • Death Knight rune support.
  • Movable Death Knight Runes.
  • Skinnable Death Knight Runes.
  • Target Buffs (40) and Target Debuffs (40).
  • Countdown timers on all Target Auras.
  • Movable and Resizable Target Auras.
  • Target range indicator.
  • Target guild display.
  • Resting, PvP, Combat, Leader, and Looter icons.
  • Text based Threat Meter.
  • Unique HUD texture that are exclusive to MetaHud - Nuckin Branch.
  • In Game graphical configuration tool to make MetaHud look and feel how you want.
  • Savable Profiles per Warcraft Account.

Bug Reports!
Please leave all bug reports in the designated area in my portal.

Feature Requests!
Please leave all feature requests in the designated area in my portal.

How Can I Donate?
I do not accept donations. This project is an addition to my portfolio for possible job opportunities. All I ask is for your support, understanding, and gratitude.

v30300-8.5 (12/19/09)
-Updated the TOC number for WoW 3.3

v30200-8.4 (9/5/09)
-Fixed "Interface Action Failed Because of Addon" error.

v30200-8.3 (8/7/09)
-Fixed ToT Bar showing with the option disabled.
-Fixed the Threat text showing when disabled.
-Fixed self auras always being larger when option was disabled.
-Removed option to double removable debuffs.

v30200-8.2 (8/4/09)
-Updated TOC number for Patch 3.2
-Fixed GetDifficultyColor() bug in Patch 3.2
-Another attempt at fixing ToT frame bug.

v30100-8.1 (7/17/09)
-Fixed the ToT Frame's hiding
-Fixed the bar border hiding option
-Fixed Alpha setting delay

v30100-8.0 (7/15/09)
-New Death Knight Rune system.
-New Target Aura System with cooldown counts.
-New Options Interface.
-New bar textures.
-New Text Threat Meter
-Lots of bug fixes :)

v30100-7.6 (4/8/09)
-Fixes a Divide-by-Zero bug in Patch 3.1
-Updated TOC number for Patch 3.1
-Removed the README.txt file

v30000-7.5 (1/30/09)
-Party Leader icon can now be shown/hidden
-Party Masterlooter icon can now be shown/hidden
-Target castbar text no longer sticks on the screen
-Vehicle's combo point counters now display as Player Combo points
-Sunder Armor no longer activates combo point display
-Castbars are more accurate at picking up spellcasts when spells are cast very quickly
-A substantial number of this calls have been replaced

v30000-7.4 (1/19/09)
-Fixed bug #5331 for Deathknights

v30000-7.3 (1/8/09)
-Fixed bug #5324
-Fixed bug #5331

v30000-7.2 (12/29/08)
-REALLY Fixed bug #5314

v30000-7.1 (12/29/08)
-Fixed bug #5314

v30000-7 (12/29/08)
-Better Rune Support (huzzah!)
-Deathknight Runes are more accurate in their timing now
-Deathknight Runes can now be hidden via the options menu
-Removed FlightTimer option from the menu
-Fixed the bug where Deathknight Runes showed on Blizzard frames regardless of player class

v30000-6 (11/19/08)
-DeathKnight rune support! (huzzah!)

v30000-5 (11/2/08)
-40 buff/debuff
-X coordinate customization of Target of Target, Target Text, Guild Text, and Range Text
-Runic Power now displaying correctly
-Smooth Mana-/Energy-Updates (thanks to Zasurus/Nukthem/Grimfist)
-Removed Polytimer
-Removed FlightTimer

v30000-4 (10/29/08)
-Target Buffs and Debuffs are now scalable in the options frame!
-Removed QuickMenu
-Bug Fix: Message: ..\AddOns\MetaHud\MetaHud.lua line 1419: attempt to index global 'MetaHudFu' (a nil value)

v30000-3 (10/28/08)
-Debuggers (such as Swatter) can now retrieve MetaHud's version number
-Removed Minimap button
-Removed FubarPlugin-2.0 and all Fubar support
-Removed AceAddon-2.0
-Removed AceEvent-2.0
-Removed AceOO-2.0
-Removed Dewdrop-2.0
-Removed Tablet-2.0
-Bug Fix: Message: ..\AddOns\MetaHudOPT\MetaHudOPT.lua line 41: attempt to concatenate local 'list' (a table value)

v30000-2 (10/25/08)
-Sunder Armor now updates combo point indicators without re targeting
-Bug Fix: Message: ..\FrameXML\UIPanelTemplates.lua line 32: attempt to index local 'tab' (a number value)
-Bug Fix: Message: ..\FrameXML\UIDropDownMenu.lua line 834: attempt to call method 'GetName' (a nil value)

v30000-1 (10/23/08)
-Main interface is now WotLK/3.0.2 compatable
Post A Reply Comment Options
Unread 04-02-09, 08:35 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
Re: Re: Backup Plans

Originally posted by Nibuca
3.1 currently forecast to hit the servers on 4/14 (at the earliest) or 4/21.

Date based on blue post about the end of Arena Season 5 and the fact that it coincides with 3.1 release.
Thanks, the information is appreciated.
Report comment to moderator  
Reply With Quote
Unread 04-02-09, 04:52 PM  
Nibuca
A Kobold Labourer

Forum posts: 0
File comments: 6
Uploads: 0
Re: Backup Plans

Originally posted by Nuckin
I've been hearing news that 3.1 may be coming sooner than I had expected.

I would like to reassure everyone that MetaHud will have a 3.1 compatible release before the servers come back up from maintenance on the day of the patch. The only question will be whether it is 8.0 like I've hoped. If 8.0 is not ready, I have created a v31000-7.6 build that is 100% compatible with patch 3.1.
3.1 currently forecast to hit the servers on 4/14 (at the earliest) or 4/21.

Date based on blue post about the end of Arena Season 5 and the fact that it coincides with 3.1 release.
Report comment to moderator  
Reply With Quote
Unread 04-02-09, 01:55 PM  
Maischter
A Defias Bandit

Forum posts: 2
File comments: 94
Uploads: 0
MetaHud-v30000-7.5\MetaHud.lua:1878: attempt to concatenate local 'typ' (a nil value)
MetaHud-v30000-7.5\MetaHud.lua:1864: in function `SetBarColor'
MetaHud-v30000-7.5\MetaHud.lua:2281: in function `UpdateValues'
MetaHud-v30000-7.5\MetaHud.lua:1378: in function `TargetChanged'
MetaHud-v30000-7.5\MetaHud.lua:514: in function `OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>
<in C code>: in function `TurnOrActionStop'
<string>:"TURNORACTION":4: in function <[string "TURNORACTION"]:1>



MetaHud-v30000-7.5\MetaHud.lua:1878: attempt to concatenate local 'typ' (a nil value)
MetaHud-v30000-7.5\MetaHud.lua:1864: in function `SetBarColor'
MetaHud-v30000-7.5\MetaHud.lua:2281: in function `UpdateValues'
MetaHud-v30000-7.5\MetaHud.lua:555: in function `OnEvent'
<string>:"*:OnEvent":1: in function <[string "*:OnEvent"]:1>

---
Report comment to moderator  
Reply With Quote
Unread 04-01-09, 09:51 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
Lightbulb Backup Plans

I've been hearing news that 3.1 may be coming sooner than I had expected.

I would like to reassure everyone that MetaHud will have a 3.1 compatible release before the servers come back up from maintenance on the day of the patch. The only question will be whether it is 8.0 like I've hoped. If 8.0 is not ready, I have created a v31000-7.6 build that is 100% compatible with patch 3.1.
Report comment to moderator  
Reply With Quote
Unread 03-30-09, 07:19 AM  
Celeras
A Kobold Labourer

Forum posts: 0
File comments: 58
Uploads: 0
I would be an awful beta tester if I didnt push for things I felt were essential

As always, no rush! Thanks for the update~
Report comment to moderator  
Reply With Quote
Unread 03-29-09, 09:33 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
I am not dead yet!

... I just had to take a step back and take a serious break from WoW for the past couple weeks. Development will resume soon.

To the beta testers, Stage 2 will come. One redesign has been the only barrier to its release because I hate hearing Celeras complain about the lack of options for buffs
Report comment to moderator  
Reply With Quote
Unread 03-27-09, 06:25 PM  
dzikson
A Kobold Labourer

Forum posts: 0
File comments: 1
Uploads: 0
Is there a way to disable your own castbar but keep your enemies castbar active?
Report comment to moderator  
Reply With Quote
Unread 03-27-09, 07:58 AM  
Celeras
A Kobold Labourer

Forum posts: 0
File comments: 58
Uploads: 0
Alright im reverting out of beta version so I can have my buffs back ;x Will pick it up again once the customizations are in
Report comment to moderator  
Reply With Quote
Unread 03-24-09, 09:54 PM  
Celeras
A Kobold Labourer

Forum posts: 0
File comments: 58
Uploads: 0
Wtb new push!
Report comment to moderator  
Reply With Quote
Unread 03-07-09, 07:08 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
Originally posted by Grimfist
Since the last PTR-build, i'm getting the following exception everytime a bar has to update:
Code:
[2009/03/07 13:49:49-1-x7]: MetaHud-v30000-7.5\MetaHud.lua:1951: TexCoord out of range
MetaHud-v30000-7.5\MetaHud.lua:1951: in function `SetBarHeight'
MetaHud-v30000-7.5\MetaHud.lua:2280: in function `UpdateValues'
...
The following lines differ, depending on which event initiated the update. (firstload, targetchange etc.)

Since the error occurs in the command
Code:
texture:SetTexCoord(x0, x1, top, bottom );
i guess, that one of the arguments might be inaccurate.
That would imply, that the current calculation of the coordinates doesn't work the way it used to.

I debugged the values by adding this line
Code:
self:print("bar: "..bar..", x0: "..x0..", x1: "..x1..", top: "..top..", bottom: "..bottom);
right before the SetTexCoord-command and the error seems to be in the target health/mana bars. Every other bar uses values in the range of 0-1, but the target health- and mana-bars try to use -1.#IND as top-value occasionally.
This happens to the target health bar, when targeting nothing at all and to the target mana bar, when targeting something without a manabar. (Like the training dummies)

The mana- and health-bars of the player doesn't update at all, but that might be related to the error with the targets.

Any ideas on how to fix this?
At the moment, no. I don't specifically develop for/on the PTR too much because API changes are frequent and often volatile. However, I do troll the UI/Macro forums for API changes. Most of the documented changes are pertaining to the new features in the Calendar, Quest, Achievement, and Dual-Spec/Gear Swap interfaces. When the PTR gets closer to closing, I will switch my development to it since by that point, most API bugs are fixed.

Though I will reinstall the PTR client and see if I hit the same errors. Version 8.0 of MetaHud will be released for client 31000 (3.1) ONLY. There are a couple new API functions I would like to take advantage of.

For everyone who wants their Sunder Armor combo points back
They're back and 100% working in 8.0, the main functionality code is in 7.5, its just commented out. I'll write up some line numbers to uncomment to get them working soon.
Report comment to moderator  
Reply With Quote
Unread 03-07-09, 07:47 AM  
Grimfist
A Kobold Labourer

Forum posts: 0
File comments: 2
Uploads: 0
Since the last PTR-build, i'm getting the following exception everytime a bar has to update:
Code:
[2009/03/07 13:49:49-1-x7]: MetaHud-v30000-7.5\MetaHud.lua:1951: TexCoord out of range
MetaHud-v30000-7.5\MetaHud.lua:1951: in function `SetBarHeight'
MetaHud-v30000-7.5\MetaHud.lua:2280: in function `UpdateValues'
...
The following lines differ, depending on which event initiated the update. (firstload, targetchange etc.)

Since the error occurs in the command
Code:
texture:SetTexCoord(x0, x1, top, bottom );
i guess, that one of the arguments might be inaccurate.
That would imply, that the current calculation of the coordinates doesn't work the way it used to.

I debugged the values by adding this line
Code:
self:print("bar: "..bar..", x0: "..x0..", x1: "..x1..", top: "..top..", bottom: "..bottom);
right before the SetTexCoord-command and the error seems to be in the target health/mana bars. Every other bar uses values in the range of 0-1, but the target health- and mana-bars try to use -1.#IND as top-value occasionally.
This happens to the target health bar, when targeting nothing at all and to the target mana bar, when targeting something without a manabar. (Like the training dummies)

The mana- and health-bars of the player doesn't update at all, but that might be related to the error with the targets.

Any ideas on how to fix this?
Report comment to moderator  
Reply With Quote
Unread 03-03-09, 01:10 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
Originally posted by Celeras
How goes it Nuckin
Slow, lol. I wanna roll out Stage2 soon, and with that I'll give beta testers better means to communicate with me to work through bugs.
Report comment to moderator  
Reply With Quote
Unread 03-03-09, 05:42 AM  
Celeras
A Kobold Labourer

Forum posts: 0
File comments: 58
Uploads: 0
How goes it Nuckin
Report comment to moderator  
Reply With Quote
Unread 02-26-09, 03:17 PM  
Nuckin
is laughing at you
 
Nuckin's Avatar
AddOn Author - Click to view AddOns

Forum posts: 58
File comments: 210
Uploads: 4
Re: Re: Memory Overhead Issue

Originally posted by Ookami.kun
A bit late for the conversation, but personally out of the three I'd like to see casting bar/times kept. I could care less about the Aggro alerts since I have omen for that, and as you stated the range indicator is to broad, if it could be made to be more exact I might use it, but I've always turned it off. As for the casting bar I've always liked the ability to track timing for a number of things on the HUD and not have to rely on glancing elsewhere on my UI to see the information that MetaHUD already tells me... that being Mob castings, flight time, and fishing timer to name a few. this of course is just my opinion, but I'd hate to see it go.
Don't worry, cast bars have been saved, need to be rewritten a little, but are saved.

Only thing currently on the axe block is the Aggro alerts
Report comment to moderator  
Reply With Quote
Unread 02-26-09, 01:18 PM  
Ookami.kun
A Cliff Giant
 
Ookami.kun's Avatar

Forum posts: 79
File comments: 239
Uploads: 0
Re: Memory Overhead Issue

Originally posted by Nuckin
To combat the growing memory overhead in metahud, I have decided to roll back some of metahud's feature set. primarily to revert it to being a pure Player/Target frame replacement. By that I mean only reinventing features in the Blizzard frames.

That sounds a lot worse than it is, But the features being considered for the axe are as follows:
  • Target Range Indicator
  • Player castbar + cast times
  • Visable and Audible aggro alerts

Though the Aggro alerts will be replaced by a percentage threat meter display.

My aim is to make metahud NOT depend on 3rd party libraries as much as possible.
A bit late for the conversation, but personally out of the three I'd like to see casting bar/times kept. I could care less about the Aggro alerts since I have omen for that, and as you stated the range indicator is to broad, if it could be made to be more exact I might use it, but I've always turned it off. As for the casting bar I've always liked the ability to track timing for a number of things on the HUD and not have to rely on glancing elsewhere on my UI to see the information that MetaHUD already tells me... that being Mob castings, flight time, and fishing timer to name a few. this of course is just my opinion, but I'd hate to see it go.
__________________
Report comment to moderator  
Reply With Quote
Post A Reply



Category Jump: