Thank you for your interest in the Quick Jump Daily Digest. Get notified of all new content on QJ.Net in our free Daily Digest.
To receive our Daily Newsletter, you must first be a member of the QJ website. Becoming a member is FREE and easy to do. To get your own
membership, click here to sign-up.
If you are already a member, click here to log-in. You
can then click on "Newsletter Settings" to customize your daily digest experience.
DamageMeters monitors damage and healing done by and to yourself and other nearby players. It keeps a running total for each player and displays the information as a bars chart in a frame on the screen. It is perfect for real-time comparison of the various members of your party or raid. At any time the text results can be output as "says", to raid or party chat, or whispered to another player. Many console commands exist for customizing the meters: type /dmhelp for a listing.
INSTALLATION: All files in the zip files should go into the directory [WOW]InterfaceAddonsDamageMeters, for example [WOW]InterfaceAddonsDamageMeters.toc. The directory is included in the zip file, so make sure you don't accidentally put the files in AddonsDamageMetersDamageMeters.
Q: What happened to the "Reset Each Combat" option? A: It was made irrelevant. DamageMeters now keeps in essence two full sets of information: one normal, and one set that applies only to the latest fight. This second set, the Fight set, is what provides the information for the DPS, HPS, DTPS, and HTPS quantities. Those quantities are basically the normal quantities but divided by the duration of the fight. If you turn off the "Visible QuantityShow Fight Data As Per/Second" option you have what is in essence the same thing as what you had before with the "Reset Each Combat" option.
Q: Why can't DM just automatically sync? A: Primarily because sync'ing takes a long time. There is just a lot of data to transmit, and since WoW likes to boot clients that send data too quickly DM transmits it slowly. While I've done what I can to make it go as smoothly as possible it still causes some people to lag out, so I prefer having the sync'ing be manual so that syncs can take place during times when its ok to be lagged.
Q: Why not add measurement of overhealing? A: I'm not sure its impossible but its certainly not a simple problem. In order to measure overhealing one would need to know the target's health BEFORE the heal lands, and we would need to know the precise order that heals land, but I don't think we clients have that information accurately. There are other practical issues, too, such as HoTs. If I cast 100 rejuvs and each one only ticks once, my overhealing will register zero even though I've wasted 75% of my heals. Honestly, I don't think that any overhealing monitor can really be accurate enough to give the information that people want from it.
Q: How do I get other player's pets to show up? A: Well, there is only one way: to turn off the option "Only Monitor Group Members". If you do so, though, you will likely get a lot of stuff in your list you don't want, like totems, non-raid players, and even some mobs. The reason that you can see your own pets OK but not other player's pets has to do with message categories. There are specific category of messages that indicate they come from YOUR pets, but other people's pets come in the "random friendly player" category. It would be possible to compare names to the list of raid member's pets, but there is no guarantee that the pets have a unique name. (For example, we actually had one pet in our raid named after another hunter!) The only way to accurately compare different hunter's output is to have them all use the "Treat Pet Data As Your Data" option and to sync. Changes : 4.1.3 - 1-28-06 : Fixed error which occurs when TitanPanel not loaded.
4.1.2 - 1-27-06 : SeraphTC did some nice changes to the Titan plugin part which resolved name conflicts with his original mod. Fixed bug in the /dmsave command (also in the menu command) which could result in a clear of one table clearing the other. /dmpop will no longer unready, nor will it add a "[Pop]" event. Added ModWatcher support.
4.1.1 - 1-16-06 : Added /dmsetbarwidth. Fixed bug reventing tooltips from updating constantly. Fixed bug which kept new players from entering the list when syncing while in the ready state. Fixed bug which prevented % text options from showing for Fight quantities.
4.1.0 - 1-13-06 : DM now can behave as a TitanPanel plugin when TitanPanel is installed.
4.0.2 - 1-06-06 : Fixed typo in help for /dmsyncbroadcastchan. Added command to bar menu for clearing list of banned entities. (/dmclearbanned still works.) Added /dmsyncstart to /dmcmd list. Fixed color error for people who downloaded 4.0.0 before 4.0.1. (The downside is that this version wipes everyone's custom color settings.)
4.0.1 - 1-05-06 : Fixed bug loading color information from older versions which was causing errors when trying to view the Visible Quantity menu.
4.0.0 - 1-05-06 : SYNC VERSION CHANGED. You will not be able to sync with players using older versions of DamageMeters.
DamageMeters has been greatly optimized for performance. On very low frame rate encounters (such as Vael) it was hurting FPS. It now has very little impact on framerate, but a sacrifice has been made: the bars only update once every second now. Some eye candy has been sacrificed, such as pulsing bars and sliding text, but I really think it is well worth it.
Added the Labels to combat the problem of people arriving late and bringing bad data to a sync session. Added /dmsyncstart, which is a convenience function which labels a session then broadcasts a clear and a pause. Added /dmsynclabel for manual labelling. /dmsyncping now shows you the label that each person is on. Please see the Readme.txt or in-game syncing help for the currently recommended sequence of sync functions.
Removed DMReporter.exe for security reasons. DMReporter.lua has been modified so that any Lua executor can run it. http://lua-users.org/wiki/LuaBinaries has a link to Lua binaries. DMReporter has also been modified to recognize the labels and can include them in report filenames.
Added Minimize mode. In this mode, only a single bar is visible. This bar always shows the player and the player's rank. Since the title button is invisible, the main menu is accessible by right-clicking on the bar itself.
Changed the way DPS is handled. Instead of just having DPS, DM now stores an entire separate set of data for the current "fight", so you can see the events for the current fight, and can also see per-second healing, etc. The "Show Fight Data as Per/Second" can be used to toggle between showing fight data as DPS vs. Total Damage, for example. This change increases the number of quantitites to 9 (4 regular, 4 fight, idle time). A Quantity Filter menu has been added to help you hide quantities you aren't interested in.
Minor changes: Pausing or readying DM will now stop the combat timer used to calculate DPS. Removed /dmmerge as it was a pain to maintain and didn't seem that useful. Added a bunch of keybindings: check them out. Fixed bug which allowed you to move a "locked" DM window by dragging the border. Bars now pulse only when the currently visible quantity changes. (Lies, bars don't pulse at all.) Added "Set Default Options" menu option. Removed "Lock List" menu option (though /dmlock still works). Added "Player Always Visible" menu option. Added "Group DPS Mode" menu option. Created a "General Options" menu to tidy things up.
Lastly, an optional feature has been added to help Shaman determine how effective they are with chain heal. To use, make a macro to cast your chain heals. The first line of the macro should be "/script DamageMeters_StartChainHeal()" (without the quotes), and the second line should be your cast call. DM will then track event data separately for each jump of your chain heals (ie. "Chain Heal 1", "Chain Heal 2", etc).
