GearDPS adds a DPS value to item tooltips based on weight given to each stat, which is calculated on the fly based on your current AP/spec/etc. Basically, the higher the number, the better that piece of gear is for pure DPS. Note that by default this doesn't take survivability into account, it's just for sheer DPS. Custom weight can be given to all stats, including stam, spirit, and MP/5. Any user specified weights will override the ones calculated by GearDPS.
This addon only applies to hunters, rogues, warriors and feral druids at the moment. I may also look into adding support for caster DPS in the future.
While GearDPS is similar to addons like HunterAEP, I'm fairly confident that the numbers are much more accurate. GearDPS calculates the weight of each stat dynamically based on your current AP (higher AP means more weight to crit/agi/hit) and spec (+% to crit bonus, +AP from int, +% to AP, etc). If you disagree with those calculations, you can specify your own weights for each stat.
If you have trouble with the tooltips, you can use /geardps value [Item Link] to manually evaluate an item.
This is still in the early stages and is likely full of bugs. If you encounter problems, I'd really appreciate it if you let me know about it. You can send a tell to Kbranch on the Shadowsong server, an email to kbranch38@gmail.com, or just leave a comment here.
- Fixed a problem where haste rating wasn't being counted.
Installation Guide
- Exit "World of Warcraft" completely
- Download the mod you want to install
- Make a folder on your desktop called "My Mods"
- Save the .zip/.rar files to this folder.
- If, when you try to download the file, it automatically "opens" it... you need to RIGHT click on the link and "save as..." or "Save Target As".
- Extract the file - commonly known as 'unzipping'
Do this ONE FILE AT A TIME!
- Windows
- Windows XP a built in ZIP extractor. Double click on the file to open it, inside should be the file or folders needed. Copy these outside to the "My Mods" folder.
- WinRAR: Right click the file, select "Extract Here"
- WinZip: You MUST make sure the option to "Use Folder Names" is CHECKED or it will just extract the files and not make the proper folders how the Authors designed
- Mac Users
- StuffitExpander: Double click the archive to extract it to a folder in the current directory.
- Verify your WoW Installation Path
That is where you are running WoW from and THAT is where you need to install your mods.
- Move to the Addon folder
- Open your World of Warcraft folder. (default is C:\Program Files\World of Warcraft\)
- Go into the "Interface" folder.
- Go into the "AddOns" folder.
- In a new window, open the "My Mods" folder.
- The "My Mods" folder should have the "Addonname" folder in it.
- Move the "Addonname" folder into the "AddOns" folder
- Start World of Warcraft
- Make sure AddOns are installed
- Log in
- At the Character Select screen, look in lower left corner for the "addons" button.
- If button is there: make sure all the mods you installed are listed and make sure "load out of date addons" is checked.
- If the button is NOT there: means you did not install the addons properly. Look at the above screenshots. Try repeating the steps or getting someone who knows more about computers than you do to help.
Translations
When you download a mod, please be sure that the mod is compatible with your translation of wow. Some mods only work on the US versions, while some only work on some of the various European versions. These variations are called "Localizations".
TOC Numbers (Out of Date Mods)
When Blizzard patches WoW, they change the Interface number. This means that all mods will be "out of date" unless or until the author releases a new version for that interface. Some people go into the .toc files and update the numbers themselves, but this is STRONGLY advised against as it will cause problems locating possible incompatibilities addons. When you log into WoW after a patch, you DO NOT have to delete your interface directory. All you have to do is simply tell WoW to ignore the interface numbers and load all the mods anyway. All you have to do is, while at the "character select" screen, look in the lower left corner and click on the "addons" button. A window will pop up listing all your installed mods.
If you look in the upper left corner of that window there should be a box that says "Load Out of Date AddOns". You want to CHECK this box. Now simply go into WoW normally and all your mods should load. As of the 1.9 patch, you will have to do this after EVERY patch/update that Blizzard posts! If you encounter any problems with a mod after a patch, please be sure to let the author of the mod know so they can fix it.
See also: About "Out Of Date AddOns"
Mac Support
WoW addons are not platformed based. As such, they can be used on either Mac or PC. You can extract both .zip and .rar files on a Mac using StuffitExpander.
Directory Structure
World of Warcraft
|_ Interface
|_AddOns
|_*AddonName*
|_ *AddonName*.toc
|_ *AddonName*.xml
|_ *AddonName*.lua
|_ (possibly others as well)...
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidSix weeks since my first report of the error; someone else as well reported it the other day below. Still more occurrences this week (v0.63, SVN r57023) of:
"GearDPS-0.63\\Calculations.lua:89: attempt to index a nil value\nAceAddon-2.0-57245 (Ace2):926: in function Interface\\AddOns\\Ace2\\AceAddon-2.0\\AceAddon-2.0.lua:919\n in C code: ?\nAceEvent-2.0-56171 (Ace2):263: in function `TriggerEvent'\nAceEvent-2.0-56171 (Ace2):914: in function Interface\\AddOns\\Ace2\\AceEvent-2.0\\AceEvent-2.0.lua:907"
Have moved on to EquipEval & Pawn for now; hopefully you are able to fix the GearDPS constant error.
- +0
- Thumbs Down
- Thumbs Up
kbranch saidSorry, I haven't checked Curse in a while.
I've seen that error myself, but only the first time I log in on a particular character after a patch. Not really sure what's going on there, but reloading the UI works for me, and logging on after that works fine for me. If that's not the case for other people, I can take a closer look.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidHaving people reload the UI is not an acceptable workaround for bugs in a mod. Hope you'll think about actually fixing this GearDPS problem sometime. I'm still using EquipEval here in the meantime.
Lots of help available in the WowAce forums and/or the IRC used by authors there if you need help with fixing it.
- +0
- Thumbs Down
- Thumbs Up
jtpowell saidI think the latest patch broke GearDPS. This is the error I get when I start it now:
..\AddOns\GearDPS\Calculations.lua line 89:
attempt to index a nil value
- +0
- Thumbs Down
- Thumbs Up
zeuseason saidWould love to see caster support in this mod.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidAgain at logon after the 2.3.2 patch went in today with SVN r57203 (on a hunter):
GearDPS-0.63\\Calculations.lua:89: attempt to index a nil value\nAceAddon-2.0-57245 (Ace2):926: in function <Interface\\AddOns\\Ace2\\AceAddon-2.0\\AceAddon-2.0.lua:919>\n<in C code>: ?\nAceEvent-2.0-56171 (Ace2):263: in function `TriggerEvent'\nAceEvent-2.0-56171 (Ace2):914: in function <Interface\\AddOns\\Ace2\\AceEvent-2.0\\AceEvent-2.0.lua:907>
- +0
- Thumbs Down
- Thumbs Up
Bloodbreaker saidin the tooltip stand only "No mainhand weapon equipped" but no values :(
anybody know whats wrong?
i'm ud rogue with the arena season 2 swords...
- +0
- Thumbs Down
- Thumbs Up
kbranch saidI'll see if I can look into it, but I'm not sure I'll be able to do much without some more information. A link to your armory, what version you're using, whether it still happens if you change weapons, etc.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidLogon with r56957 off the Ace SVN (corresponds with v0.62 here) on a level 11 rogue and:
GearDPS-0.61\\Calculations.lua:89: attempt to index a nil value\nAceAddon-2.0-46764 (Ace2):927: in function <Interface\\AddOns\\Ace2\\AceAddon-2.0\\AceAddon-2.0.lua:920>\n<in C code>: ?\nAceEvent-2.0-56171 (Ace2):263: in function `TriggerEvent'\nAceEvent-2.0-56171 (Ace2):914: in function <Interface\\AddOns\\Ace2\\AceEvent-2.0\\AceEvent-2.0.lua:907>
Standalone libraries, USEng server/client.
- +0
- Thumbs Down
- Thumbs Up
kbranch saidI've run into that myself, and I think I've fixed it. It seems to be intermittent, reloading your UI should fix it for some reason. I've updated the copy on Ace.
- +0
- Thumbs Down
- Thumbs Up
kbranch saidHeh, sorry about that, I should have caught that. A rename should have fixed it, though, not sure why you're getting errors. I've updated the downloads, if that doesn't fix it, post the exact errors and I'll see what I can do.
Thanks for letting me know, I changed how I zip things up for Curse, and I didn't stop to think long enough about what I was putting in there.
- +0
- Thumbs Down
- Thumbs Up
jtpowell saidStill problems with the downloads. These are the .lua errors:
...addons\GearDPS\statlogic-1.0.lua line 3918: attempt to call local 'strut8lower' (a nil value)
...addons\GearDPS\calculations.lua line 1: AceAddon:Ace-2.0: library 'FubarPlugin-2.0' does not exist
...addons\GearDPS\settings.lua line 727: attempt to index globa 'GearDPS' (a nil value)
...addons\GearDPS\core.lua line 3: attempt to index global 'GearDPS' (a nil value)
I noticed that the directroy UTF8 was present in 0.54 and previous versions, but not in 0.60 or 0.61. Could that be the problem?
- +0
- Thumbs Down
- Thumbs Up
kbranch saidSigh, I thought I was testing with only GearDPS enabled, but apparently WoW felt like helping out by automatically enabling libraries I had installed but disabled. After removing all addons but GearDPS from my interface directory, I was able to reproduce the errors you're getting, and I'm updating the downloads yet again with the fixes.
Sorry for all the trouble, hopefully it'll all work right now.
- +0
- Thumbs Down
- Thumbs Up
jtpowell saidThat seems to have fixed it. Thanks for your hard work on this. I use the addon daily to make "informed" choices for AH purchases.
- +0
- Thumbs Down
- Thumbs Up
jtpowell saidSorry, but the last 2 updates are a mess. The name of the expanded folders are "GearDPS-.0.60" and "GearDPS-0.61". WoW doesn't like those names, and won't load either addon. I changed the name of the folder to "GearDPS" (consistent with previous versions) and the GearDPS appears in the "Addons" list at the character choice screen. However, my name change caused a flock of .lua errors and the addon fails to load when logging onto a specific toon. I reverted to 0.54 which loaded normally.
- +0
- Thumbs Down
- Thumbs Up
kbranch saidZidomo:
Are you using .60? It was a bit of a CPU hog before due to the rate that tooltips get updated in some situations, but I changed some things once I realized it was doing that. The CPU usage should be drastically reduced now, I'm not seeing any noticeable performance hit under any circumstance anymore.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidv0.60 off the Wowace SVN, standalone libraries. If the CPU usage of this is reasonable, I shudder to think about what it was like in v0.54 ;)
Further testing has turned up some interesting info, though. The monumental CPU usage of this...only occurs mousing over specific items/item types.
For example, on a level 10 rogue (where I do most of my non-combat mod testing), mouse over a piece of level 34 green leather shoulder armor in his bags. MS/sec CPU=3.4 (between 3 and 4 average). Which is reasonable.
Head to the AH and mouse over a level 70 blue bow (the rogue isn't wearing a ranged weapon): MS/sec=4-5. Creeping up, but still reasonable
Then head to the fist weapon section. Mouse over a level 70 green off-hand fist weapon. MS/sec=13-14. Which is about 5 times higher than other tooltip addons that scan and report, like WhoHas.
Then mouse over a level 68 green _one hand_ fist weapon. MS/sec=35-50. Very unreasonable. At the top of my mods list. And its what causes the background slowdown mentioned before.
All those CPU times could be duplicated within the session. Hopefully it can be improved.
- +0
- Thumbs Down
- Thumbs Up
kbranch saidInteresting, I'll take a look. I can't think of anything off the top of my head that should make it do anything more than update the tooltip with the text from the last calculation (which happens every ten seconds if you're holding your cursor over an item, it used to do the calculation on every update), but hopefully some testing will turn up the problem.
What I was calling reasonable is what you seem to get on the green shoulders, the usage like you're seeing on the fist weapon is what I thought I had fixed. Thanks for the detailed report, should make it easier to figure things out.
Edit: I found the problem and fixed it in 0.61. It was only showing up when there were two or more tooltips open at the same time (as in via EQCompare or something), and being at the auction house would make it worse because it seems to generate the event that causes GearDPS to parse the tooltip every frame (where the character page generates this event a few times a second, and tooltips from linked items only generate it once per click). It would cut my frame rate roughly in half when comparing a ring at the auction house before, but I'm not seeing any difference at all now with GearDPS on or off.
Lemme know if you find any more problems.
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidYes, sorry, forgot to mention that I am using tekKompare hovertips for multi-tooltips. Would assume the same issue would appear with the default Blizzard SHIFT-click multi-tooltips for items.
Will let you know of any further issues with 0.61 when I have time to test again; thanks for looking into this :).
- +0
- Thumbs Down
- Thumbs Up
Zidomo saidA fairly large problem with this: it uses a gigantic amount of CPU time when you display tooltips for items/links (any type). So much so that it slows down the frame rate of surrounding environment (on my reasonably decent PC) when you access tooltips/links. Which is a problem.
Measured with FuBar_Usage (on http://files.wowace.com). Completely standalone libraries installed separately (so that Usage is not counting the Ace2 libraries). In terms of "Rate ms/s", this mod is close to the top in CPU usage. Would be nice to see it lowered.