»
WeightsWatcher
Pictures
File Info
| Tested: | Hour of Twilight 4.3 |
| Updated: | 01-07-2012 02:45 PM |
| Created: | 12-03-2009 02:30 AM |
| Downloads: | 11,884 |
| Favorites: | 122 |
| MD5: |
WeightsWatcher 
Currently, all base stats, gems in non-crafted sockets, and enchants should be handled properly. Also, gems are suggested based on the weights you have enabled. Note that crafted sockets and other "stacking" enchants are not currently handled, because they are not detectable through the WoW API.
All weights can be changed as you see fit, and you can create and enable as many or as few as you would like.
The default stat weights are provided by AskMrRobot.com, with their consent. Everything else the mod does is of our own creation, and does not use the AskMrRobot.com optimization formulas.
Endgame players will probably want to create hit- and/or expertise- capped weights, which is easily done by copying an existing weight and setting the appropriate values to 0.
Slash commands:
- /ww config - Brings up the main configuration window
- /ww config display - Brings up the display configuration window
- /ww config calculation - Brings up the weight calculation configuration window
- /ww config gems - Brings up the ideal gem configuration window
- /ww config enchants - Brings up the ideal enchant configuration window
- /ww weights - Brings up the weights configuration window
- /ww version - Displays version information
- /ww help - Displays this message
Known issues:
- Trinkets and meta gems are not currently handled very well. Specifically:
- The special effects on meta gems are not included in the default set of weights (but you can add them yourself)
- "Chance on X" and some use effects on trinkets are not taken into account (these will be marked as unweighted)
- Use effects that increase a stat by a static amount are now handled
- Equip effects that increase a stat by a static amount, stacking up to x times are also handled
- Other, more oddball trinket effects are not handled either (these will be marked as unweighted)
- Similarly, enchants that have procs or other special effects are not handled well. You can weight those enchants manually, however.
Planned (eventual) features:
- Whole-character scoring
- Import/export weights from/to Wowhead and similar sites
- This would have to be limited to the stats that both WW and the site(s) supported, so it would likely be an imperfect translation
- Outfit creation based on a given weight
- Currently best handled by using Outfitter's WeightsWatcher support
- Ideally handling caps appropriately and suggesting changes to gems/enchants/reforging.
- Support for reforging (suggesting; reading the stat change works already)
- Handling unique-equipped gems, mutually-exclusive enchants and the like properly.
- Suggestions welcome!
The authors of WeightsWatcher can be contacted at WeightsWatcher@gmail.com, or through the project page at WoWInterface.com.
We take bugs very seriously; if something is not being parsed properly, you get a nil error, or anything else goes wrong, please try to reproduce it and let us know so we can fix it.
1.5r4:
1.5r3:
1.5r2:
1.5r1:
1.4r15:
1.4r14:
1.4r13:
1.4r12:
1.4r11:
1.4r10:
1.4r9:
1.4r8:
1.4r7:
1.4r6:
1.4r5:
1.4r4:
1.4r3:
1.4r2:
1.4r1:
1.3r5:
1.3r4:
1.3r3:
1.3r2:
1.3r1:
1.2b11:
1.2b10:
1.2b9:
1.2b8:
1.2b7:
1.2b6:
1.2b5:
1.2b4:
1.2b3:
1.2b2:
1.2b1:
1.1b10:
1.1b9:
1.1b8 (not archiving due to nil error, use 1.1b9 for these features and one less bug):
1.1b7:
1.1b6:
1.1b5:
1.1b4:
1.1b3:
1.1b2:
1.1b1:
1.0b2: Reposted 12/8 (patch 3.3 dropped)
1.0b1: First public release
- Fix a nil error when parsing certain stacking equip effects. Thanks to Faüst for the bug report.
- Handle a few trinkets that have extra text describing their effects (mostly from Molten Front)
- Update to the new names/stats for several enchants
- Fix a few parsing issues
- Lowered memory usage a touch
1.5r3:
- Changed to using weights from askmrrobot.com by default (with their permission)
- You will need to restore your default weights to see the new defaults. Open the weight configuration screen with /ww weights and click Restore Defaults.
- These are updated much more often than Wowhead's and we will do our best to keep our version up to date as well. Please feel free to poke us if we fall behind on that.
- Bumped to TOC to show that we're compatible with 4.2
- Fixed the stats on Vivid Dream Emeralds
- Removed some debug code that was accidentally put in the released version
- Localized some text that was missed in the enchant changes
1.5r2:
- Added several spell-only enchants that were accidentally skipped in 1.5r1 (embroideries, runeforging, etc.) to the list of weightable stats
1.5r1:
- WeightsWatcher now supports enchants!
- Any enchant with "normal" stats will be suggested automatically based on your current weights
- Those with procs and other unusual effects have been added to a list of enchants you can manually add weights for
- With the exception of Lightweave, Darkglow, and Swordguard embroideries, all of these enchants have a value of 1 when being weighted. The mentioned ones have a value of 1 for the first rank and 2 for the second rank.
- We eventually plan to support procs in general, but it will be another large project. When we do, we will move all the enchants we can to that method of handling.
- Those with procs and other unusual effects have been added to a list of enchants you can manually add weights for
- WW will take the following into account when figuring out the best enchant for your gear:
- Your level
- The item level
- Your professions and their level
- Your reputation with relevant factions
- The obvious stuff (slot, subslot, etc.)
- The options have been given a bit of a workover to support this
- All your current choices should carry over to the new structure
- There are some new ones specifically for enchants as well
- The options are still accessible via /ww config, but you can now use /ww config <submenu> to jump immediately to the submenu of your choice
- Submenus: calculation, display, gems, and enchants
- Note that Blizzard's code to do this has some bugs which may open you to the wrong menu if you have alot of addons using the Blizzard config UI. I recommend the addon BlizzBugsSuck to fix this issue (and a few others) until Blizzard releases their own fix.
- Any enchant with "normal" stats will be suggested automatically based on your current weights
- Frost mages no longer have a default value for mastery rating of 700
- Default weights have not otherwise been updated since Wowhead has not updated theirs -- if anyone can suggest a more up-to-date source for the default weights that won't take use hours of looking through forums AND handles all classes and specs, let us know!
- Some obsolete stats have been removed from the list
- The weights configuration window (/ww weights) is now a little smarter about what happens when it is asked to close
- Weight normalization now only takes the "normal" stats into account to avoid individual enchants and other oddball stats skewing the numbers
- Miscellaneous parser updates and other backend work
1.4r15:
- Fixed some issues with deleting weights. Nothing a reloadui didn't fix before, but now you don't have to.
1.4r14:
- Updated to the latest weights from Wowhead. You will need to restore the default weights to see these changes.
- Affected classes/specs:
- Balance and restoration druids
- Marksmanship and survival hunters
- Frost mages
- Holy and protection paladins
- Holy priests
- Elemental shaman
- Destruction warlocks
- All warriors
1.4r13:
- Fixed ideal gem suggestion for items with meta and/or cogwheel sockets. Thanks to dpsthree for the bug report.
- Previously, the meta/cogwheel gems only counted towards the "follow socket colors" path, which may have resulted in best-following-color gems being suggested for the colored sockets (instead of the actual best gem), or no meta/cogwheel gem being suggested (unlikely).
1.4r12:
- Added localization strings for the new gems in r10. Should avoid warning messages about them.
1.4r11:
- Fixed parsing of the Ebonsteel belt buckle, which I forgot to put in r10.
1.4r10:
- Added the new Cataclysm meta gems and a couple others that were missing
- Fixed a nil error when running /ww version (since 1.4r8)
1.4r9:
- Updated to the latest Wowhead weights. Use the Restore Defaults button in /ww weights to see the changes.
- I'm not entirely sure these are all better, but they are newer. As always, using rawr or simulationcraft to get numbers tailored to your character is better anyway.
- Updated classes/specs: hunters, arcane mages, holy paladins, shadow priests, and elemental shaman
- Tweaked a couple of parser patterns for item changes.
1.4r8:
- Removed the Ace2 libraries, which were both out of date and barely used.
- There should be no functional or visible changes, but if you find one, please report it!
- This may fix a bug reported by Zidomo.
- Another benefit is a somewhat smaller addon.
1.4r7:
- Fixed the quality limit for suggested gems being ignored
- Fixed a global variable being created unnecessarily
- Miscellaneous backend changes to make future updates easier
1.4r6:
- Hide weights with a value of zero by default and added an option to show them
- Other items WeightsWatcher puts into the tooltip will now only show if:
- You have the "Show zero weights" option enabled, or
- You have the "Show Debug Info" hotkey pressed
- Other items WeightsWatcher puts into the tooltip will now only show if:
1.4r5:
- Updated to new Wowhead default weights. You'll need to restore the default weights to see them.
- Fire Mage
- Retribution Paladin
- Disc Priest
- Warlock (all specs)
- Arms Warrior (typo fix, armor went from 1 to 2)
1.4r4:
- Added support for minimum item levels required for gems.
- I think Blizzard made item levels always show. If not, and you see only Wrath gems even on Cataclysm items (and you've set WW to use Cata gems), please let me know.
- Cogwheels are now properly in the Unique-Equipped group of gems.
- I'm open to suggestions for how to handle that better than WW does currently.
- Fixed a few dual-wield checks to be more accurate for Cataclysm.
- Note that you need to be in the dual-wielding spec (at least warriors and shaman do) for this to work.
- I could add an option to check both (let me know if you want one), but I don't think it's a good default.
- Note that you need to be in the dual-wielding spec (at least warriors and shaman do) for this to work.
- Minor backend changes to support the above and remove another global variable.
1.4r3:
- Added support for cogwheel gems. They should show up for anyone who looks at an item with cogwheel sockets.
- This is tested as much as I can without a high-level engineer. Please let me know if it breaks!
- I can add a filter if people really want one, but it seems unnecessary at this point.
1.4r2:
- Fixed the nil error when viewing items with prismatic sockets. Thanks to Zidomo for the initial report and dpsthree for finding me some items to reproduce it.
1.4r1:
- Support Cataclysm gems. There may be errors in the data (please let me know if you find any!)
- There are now categories in /ww config to include cataclysm gems.
- Currently, there are no item level checks for Cataclysm gems. This will be fixed in a future version, as it requires a bit of work on the backend.
- Engineering ("cogwheel") gems/sockets are not handled yet.
- Several (minor) parser updates. As always, please report any un- or mis-parsed items.
1.3r5:
- Updated to newest Wowhead weights. You will have to reload the default weights to see the changes.
1.3r4:
- Fixed a nil error that could come up when using TipTac. Thanks to Ambar0691 for the bug report.
1.3r3:
- Added support for mastery rating
- Added mastery to all weights, set to 100 for now
- Minor parser tweaks
- Changed default Death Knight weight names to reflect the fact that Blood is the tank tree now
- Started Cata gem support
1.3r2:
- Fixed a few nil errors when creating and deleting weights
- Fixed some graphical spacing issues
- Fixed some xml errors in Cataclysm clients
- WeightsWatcher is now Cataclysm compatible
- However, new stats such as mastery rating are not yet handled (and are marked as such)
- Also, certain items may have new wording that is not yet handled (again, marked as such)
- WeightsWatcher is now Cataclysm compatible
1.3r1:
- Fixed several unparsed items
- Changed the names of a few stats and added several that were not weightable previously
- These should be auto-updated
- Specific changes (not a complete list):
- Melee and ranged weapons' damage, speed, and dps can now be weighted separately
- Spell hit and crit, as well as ranged hit, crit, and haste, are now weightable
- Disorient and fear resists are now weightable
- Changed the organization of the weights config
- Localized everything for enUS (laid the groundwork for other translations)
- Updated to the latest weights from WoWhead
- Warriors now have separate weights for arms and fury
- Death knights now have Blood Tank and Frost Tank weights (Frost Tank is the old Tank weight)
- You will need to restore the default weights to see these changes (click "Restore Defaults" in /ww weights)
- Fixed marking of unweighted lines to mark all sections of multi-line (graphically) tooltip lines
- Fixed a potential issue with the handling of invalid SavedVars data
- Added contact information to the help
1.2b11:
- Fixed ideal gem calculations (broken in 1.2b10). Thanks to dpsthree for the bug report.
- Fixed the upgrade function for stun resist chance (and forced a re-run of said function).
- Fixed a bug with triggers being "changed" even if returned to their original state (UI only).
- Fixed a bug preventing classes in the weights config dialog from collapsing when you had deleted an "active" weight from a different character (UI only).
1.2b10:
- Fixed handling stat weights that had decimal parts that don't exactly convert to binary. The main symptom was a weight that "changed" without you doing anything but selecting it (and no visible change).
- Fixed a nil error when using a decimal point in stat weights (everything still worked as long as you used valid numbers).
- Changed stun resistance to stun resist chance to match similar stats. Weights using stun resistance are automatically upgraded.
- Lots of code cleanup (no visible changes though).
1.2b9:
- Fixed handling of the meta gem stat "armor from items (percent)".
- Fixed thrown weapons to have their dps marked as ranged dps instead of melee dps. Thanks to Edwilly for the bug report.
1.2b8:
- Fixed a bug causing nil errors when creating a new, empty weight. Thanks to dpsthree for the bug report.
1.2b7:
- Fixed a bug causing prismatic gems to not be considered as ideal gems
- Fixed comparison values in tooltips for weapons (again). This should fix all remaining issues with weapon comparisons, but if not please let us know.
- Added comparison values to AtlasLoot tooltips (and any future addons with tooltips that we support)
- Added a hotkey to show everything the parser parses, defaults to never (change it in /ww config).
- This is as much for our own use as anyone else's, but it may help people track down bugs.
- I'm not going to heavily document this (yet), but feel free to ask questions!
1.2b6:
- Fixed a bug causing nil errors when showing tooltip hints. This is why you should always test your default settings, kids. Thanks to Zidomo for the bug report.
1.2b5:
- Added support for equip effects that grant a stat on certain actions, stacking up to a certain number of times.
- Added triggers for said equip effects to each weight. The default weights have been updated to include appropriate triggers. The data upgrade function will attempt to choose the right trigger(s), but is not perfect. For example, hit-capped caster weights will almost always have the wrong triggers picked. To fix this, open /ww weights and pick the correct triggers for each weight.
1.2b4:
- Fixed a bug affecting current weight calculations when an item's socket bonus was being used. Ideal gems and ideal weight calculations were not affected.
1.2b3:
- Handle simple use effects
- For now, this is only use effects that increase a stat by a static amount
- New config option added, to allow tuning of use effect calculations
- Set to 80% of ideal uptime by default
- Can be set to 0% if you never remember to use your trinkets, 150% if you always use them to maximum effect, or whatever number you feel works best for you.
- Several backend changes, mostly to support use effects
1.2b2:
- Fixed a bug affecting (some) hunter and warrior weapon comparisons. Thanks to Zidomo for the bug report.
1.2b1:
- Complete parser rewrite
- All corner cases for basic stats should be handled
- The groundwork for use effects and procs has been laid (they don't work yet, though)
- Most enchant scrolls and formulas are now parsed properly
- Any unweighted effect is now marked as such in the tooltip, with a total count at the bottom
- Lots of backend cleanup
- Newly supported/fixed stats:
- Feral AP
- Ranged AP (also added to the default hunter weights)
- Mana
- Schooled spell damage
- Spell resistances (fixed)
- Increased threat
- Disarm reduction
- You can now see comparison numbers without holding shift
- This also fixes comparing to an empty slot
- Minor fix to tooltip hints (the alternate gems tip used to show even with no alternate gems)
1.1b10:
- Stopped regular gems from sometimes showing up in meta gem recommendations
- Made the weights configuration dialog (/ww weights) expand all used classes instead of just the current class
- Minor code cleanup
1.1b9:
- Fixed a silly typo in the default vars. Thanks to attackfrog for the bug report.
- Only affected new users, but caused a nil error
- Minor fixes to weapon comparison handling
- Properly show comparison numbers for a one-hand weapon when you currently have a two0hand weapon equipped
- Properly compare weapons that aren't affected by Titan's Grip (only affected fury warriors)
1.1b8 (not archiving due to nil error, use 1.1b9 for these features and one less bug):
- Added the ability to show all equally-weighted ideal gems
- Should at least help with meta gem suggestions, still best to give weights to the meta effects you want though
- Set to Alt key by default (but can be configured)
- Changed the way allowed ideal gems are configured
- Gems are now sorted by:
- Source (vendor, pvp vendor, quest, drop, etc.)
- This includes procced gems (like wrath perfects)
- Restrictions (none, unique-equipped, JC-only, etc.)
- Quality (unchanged from before)
- Source (vendor, pvp vendor, quest, drop, etc.)
- Should be a fairly seamless transition, but it wouldn't hurt to check your options using /ww config
- Gems are now sorted by:
- Various backend changes to support the above
1.1b7:
- Fixed a MAJOR bug with ideal gem calculations
- All ideal gem calculations were following the socket color, whether it was better to get the bonus or not
- Yes, even if you had the options set differently
- Yes, that's really bad (sorry!)
- Yes, even if you had the options set differently
- Introduced in version 1.1b1
- All ideal gem calculations were following the socket color, whether it was better to get the bonus or not
- Fixed a few parsing issues
- Most notably shield block rating/value now work correctly
- Also fixed some enchanting scrolls
- Fixed an error when determining whether a warrior had Titan's Grip talented
- Only affected comparison numbers when a warrior was comparing weapons
- Miscellaneous invisible code cleanups
1.1b6:
- Finally fixed that SCT bug. Thanks to SmuvMoney for the bug report.
- Removed a bit of dead code
1.1b5:
- Reduced indentation on the tooltip
- Fixed several parsing errors
1.1b4:
- Changed the way gems are handled. You will probably want to re-visit your gem options (/ww config, left side).
- Split JC-only, unique-equipped, and procced (i.e. wrath "perfect") gems from the main gem quality option
- This should be somewhat faster when finding ideal gems
- Attempted to intelligently convert the old level to the appropriate options...but it's not really a linear conversion
- Split JC-only, unique-equipped, and procced (i.e. wrath "perfect") gems from the main gem quality option
- Changed the comparison behavior when viewing an item without sockets while wearing an item with sockets
- Holding the modifier key to show ideal weights (Shift by default) now causes the ideal weight to be compared against instead
- Well, technically, it's the higher of the two, but usually that means the ideal one anyway
- Unless you have a JC-only gem socketed but don't have them turned on for ideal gem calculations
- This list is getting ridiculous...
- Unless you have a JC-only gem socketed but don't have them turned on for ideal gem calculations
- Well, technically, it's the higher of the two, but usually that means the ideal one anyway
- Holding the modifier key to show ideal weights (Shift by default) now causes the ideal weight to be compared against instead
- Fixed some cache issues triggered by changing options and/or weights
1.1b3:
- Fixed a typo causing a nil error when parsing certain items.
1.1b2:
- Fixed which items' scores are compared when comparing weapons. Should do the Right Thing(tm) now.
1.1b1:
- Fixed meta gems' weights. No default values were added, so you still have to give the meta gem effects weights if you want to use them...but they all work now.
- Re-did caching, which has no visible difference but allowed me to:
- Added colorized differences to the currently equipped item(s). Will pick the lower-scored item to compare to for rings, trinkets, weapons, etc.
- Added compatibility with AtlasLoot (adds weights to its tooltips now)
- Fixed a minor bug with the "Show Class Names" option
1.0b2: Reposted 12/8 (patch 3.3 dropped)
- The ONLY difference from 1.0b1 is the interface version and the b1 to b2 bump
1.0b1: First public release
- Features:
- Tooltip display of an item's score according to the enabled weights
- Completely customizable weights, based on each item's actual stats
Archived Files (40)
File Name |
Version |
Size |
Author |
Date |
1.5r3 |
105kB |
IQgryn |
08-06-2011 08:23 PM |
|
1.5r2 |
106kB |
IQgryn |
06-17-2011 07:16 PM |
|
1.5r1 |
106kB |
IQgryn |
06-11-2011 11:00 AM |
|
1.4r15 |
65kB |
IQgryn |
03-06-2011 06:23 PM |
|
1.4r14 |
65kB |
IQgryn |
03-06-2011 08:26 AM |
|
1.4r13 |
65kB |
IQgryn |
02-26-2011 01:06 PM |
|
1.4r12 |
65kB |
IQgryn |
02-19-2011 01:13 PM |
|
1.4r11 |
65kB |
IQgryn |
02-18-2011 11:32 PM |
|
1.4r9 |
65kB |
IQgryn |
02-14-2011 08:46 PM |
|
1.4r8 |
65kB |
IQgryn |
01-27-2011 07:28 PM |
|
1.4r7 |
100kB |
IQgryn |
01-23-2011 06:18 PM |
|
1.4r6 |
99kB |
IQgryn |
01-22-2011 11:07 AM |
|
1.4r5 |
99kB |
IQgryn |
01-21-2011 05:24 PM |
|
1.4r4 |
99kB |
IQgryn |
01-16-2011 11:22 AM |
|
1.4r3 |
99kB |
IQgryn |
01-09-2011 10:16 PM |
|
1.4r2 |
99kB |
IQgryn |
01-09-2011 12:49 PM |
|
1.4r1 |
99kB |
IQgryn |
01-09-2011 11:33 AM |
|
1.3r5 |
97kB |
IQgryn |
12-31-2010 04:49 PM |
|
1.3r4 |
97kB |
IQgryn |
11-22-2010 10:42 AM |
|
1.3r3 |
97kB |
IQgryn |
11-11-2010 08:28 PM |
|
1.3r2 |
98kB |
IQgryn |
09-06-2010 06:59 PM |
|
1.3r1 |
98kB |
IQgryn |
08-31-2010 02:33 PM |
|
1.2b11 |
79kB |
IQgryn |
08-01-2010 02:07 AM |
|
1.2b10 |
79kB |
IQgryn |
07-29-2010 12:49 AM |
|
1.2b9 |
79kB |
IQgryn |
07-13-2010 03:01 AM |
|
1.2b8 |
79kB |
IQgryn |
06-14-2010 06:13 PM |
|
1.2b6 |
79kB |
IQgryn |
05-24-2010 11:32 PM |
|
1.2b4 |
77kB |
IQgryn |
05-17-2010 02:00 PM |
|
1.2b3 |
77kB |
IQgryn |
05-13-2010 01:47 PM |
|
1.2b2 |
76kB |
IQgryn |
04-26-2010 12:53 PM |
|
1.1b10 |
70kB |
IQgryn |
02-11-2010 02:11 PM |
|
1.1b9 |
70kB |
IQgryn |
01-20-2010 09:22 PM |
|
1.1b7 |
69kB |
IQgryn |
01-14-2010 02:24 AM |
|
1.1b6 |
69kB |
IQgryn |
01-07-2010 06:09 PM |
|
1.1b5 |
69kB |
IQgryn |
01-06-2010 02:33 PM |
|
1.1b4 |
69kB |
IQgryn |
12-18-2009 03:51 PM |
|
1.1b3 |
68kB |
IQgryn |
12-17-2009 04:05 PM |
|
1.1b1 |
67kB |
IQgryn |
12-15-2009 02:48 AM |
|
1.0b2 |
68kB |
IQgryn |
12-08-2009 10:11 AM |
|
1.0b1 |
68kB |
IQgryn |
12-07-2009 02:54 PM |
 |
Comment Options |
01-07-2012, 04:59 PM
|
|
|
A Cyclonian
 Forum posts: 46
File comments: 70
Uploads: 1
|
Version 1.5r4 Released
The main change is a nil error fix on some items (thanks to Faüst for the report and enough information to track it down), but there are a few other fixes as well. I also bumped the TOC to indicate WW is 4.3-compatible (though it always has been). See the change log for details.
As always, feedback is welcomed. Post it here, send me a PM, or e-mail WeightsWatcher@gmail.com.[/quote] |
|
|
|
08-06-2011, 08:31 PM
|
|
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Version 1.5r3 Released
I am sorry that it took so long, but 1.5r3 is now released. The major change is moving to using Mr. Robot's weights by default. Thank you to Daagar for the suggestion, and Mr. Robot for allowing us to use their weights.
You will need to restore the default weights to see the new defaults. See the change log for full details. As always, feedback is welcomed. Post it here, send me a PM, or e-mail WeightsWatcher@gmail.com.
Last edited by IQgryn : 08-06-2011 at 08:36 PM.
|
|
|
|
|
06-17-2011, 05:55 PM
|
||
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
|
|
|
|
|
|
06-17-2011, 05:08 PM
|
|
|
A Murloc Raider
Forum posts: 6
File comments: 49
Uploads: 0
|
For decent default weights, ask the folks at askmrrobot.com if you can embed theirs. Granted, some classes (hunters) will still yet at you that they aren't perfect, but they will typically be closer than wowhead. For some classes (spriest) they will be about as accurate as is possible.
Another alternative is to use the weightings that are generated and posted at simulationcraft.org. Also very accurate and almost always up to date. |
|
|
|
06-11-2011, 11:10 AM
|
|
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Version 1.5r1 Released
Hey, folks. It's been a long time coming, but 1.5r1 is now released. The major change is that WeightsWatcher now supports enchants. See the change log for details, and please feel free to ask questions here.
As always, feedback of any sort is welcomed. Post it here, send me a PM, or e-mail WeightsWatcher@gmail.com. |
|
|
|
|
05-19-2011, 08:43 AM
|
||
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
I will accept patches, but I can't promise much more than that until the travel slows down a bit. Just as a reminder, you can update the weights for your own copy using /ww weights. |
|
|
|
|
|
05-12-2011, 09:08 AM
|
|
|
A Cliff Giant
Forum posts: 76
File comments: 1041
Uploads: 0
|
Poke poke, wink wink, nudge nudge for updated WoW 4.1 changed class values
 . |
|
|
|
|
03-07-2011, 04:43 PM
|
||
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Those numbers will work with WeightsWatcher. You can put them in using /ww weights. You will need to make sure that you either zero or change any stats that already have values but are not in the EJ weight (or just start with an empty weight).
WeightsWatcher automatically normalizes the values (by default -- you can turn it off if you prefer in /ww config), so you should get the same results with the same ratios between the stats, regardless of the actual values.
Last edited by IQgryn : 03-07-2011 at 04:43 PM.
|
|
|
|
|
|
03-07-2011, 08:49 AM
|
|
|
A Deviate Faerie Dragon
Forum posts: 10
File comments: 93
Uploads: 0
|
I just tried your mod last night and while I really like the idea behind it, and think it could be very useful, I believe I may need some clarification in one respect.
I use the weights as given in the forums on elitistjerks.com and it would appear that some form of conversion needs to be done to use those weights with your mod. If you could give me some idea how I could convert the weights it would go a long way toward making your mod more useful to me. Below is an example of the weights I am using. [iLvl 359 - Frost DK 2 Hander Spec] Strength: 2.28 Hit: 0.99 Expertise: 0.94 Mastery: 0.80 Haste: 0.84 Crit: 0.60 Attack Power: 0.74 |
|
|
|
|
03-06-2011, 06:26 PM
|
|
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Re: Version 1.4r10 Released
Fixes some issues with the weights window when deleting weights. Please let me know if you find any more issues with this (or the weights window in general).
As always, feedback of any sort is welcomed. Post it here, send me a PM, or e-mail WeightsWatcher@gmail.com. |
|
|
|
|
03-06-2011, 08:27 AM
|
|
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Version 1.4r14 Released
The only change is new weights from Wowhead. You will need to restore the default weights to see the changes.
|
|
|
|
|
03-06-2011, 07:48 AM
|
||
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
That usually means your weights should be adjusted. As I've stated before, I am not a theorycrafter and do not generate the default weights myself, but instead rely on Wowhead's weights for each spec. I encourage you to change them to suit your needs, especially for non-endgame or non-PVE characters. In this case, giving attack power, critical strike rating, and/or weapon dps a non-zero weight would probably be more accurate.
The default weights for protection paladins are as follows (stats present on those items only): Stamina - 100 All others - 0 There is a stamina increase, so the computation itself is valid. You can use /ww weights in-game to adjust your weights as you see fit. EDIT: It seems Wowhead has new weights for several specs. I'll upload a new version shortly, but I don't think they will change the result in this particular case.
Last edited by IQgryn : 03-06-2011 at 08:05 AM.
|
|
|
|
|
|
03-06-2011, 02:29 AM
|
|
|
A Kobold Labourer
Forum posts: 0
File comments: 1
Uploads: 0
|
I think that you may want to rethink how this addon computes weights. With the default settings, I got this result while trying to figure out what gear to use:
 |
|
|
|
|
02-18-2011, 11:21 PM
|
|
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
Version 1.4r10 Released
(1.4r10) Fixed a nil error in /ww version and added the new Cataclysm meta gems.
EDIT: uploaded version 1.4r11, which also fixes Ebonsteel belt buckle parsing. EDIT AGAIN: uploaded version 1.4r12, which also adds localization strings for the new gems. This is why you don't upload new versions when you're tired and have a fever. The good news is you should've just gotten warning messages, with things still working. As always, feedback of any sort is welcomed. Post it here, send me a PM, or e-mail WeightsWatcher@gmail.com. Thanks!
Last edited by IQgryn : 02-19-2011 at 01:15 PM.
|
|
|
|
|
02-15-2011, 05:44 PM
|
||
|
A Cyclonian
Forum posts: 46
File comments: 70
Uploads: 1
|
I'm glad to hear I fixed the earlier issue. As far as hard crashes go, I've never experienced one due to WW, but of course I won't claim that means no one could. I've also never experienced that particular error before, with any addon. I don't think it's possible, but I'll be sure to watch WW's resource usage.
I have run into issues with another addon where the saved data would pass a limit and be deleted the next time the game loaded. This was with the full item text of nearly every item in the game, though. If you can give me an instance or two that the crash occurred in, and what difficulty level, I'll try to run those and see if I can make anything happen. Unfortunately, unless I can reproduce it or other people report it, there's not much I can do beyond that. Finally: what are your system specs (CPU, ram, and graphics ram)? I'd be surprised if they're lower than mine, but I don't want to rule anything out prematurely. Thanks for the feedback!
|
|
|
|
|
|
