- Home
- Downloads
-
Addons & Mods
Featured
World of Warcraft
4,833 Addons
-
Popular Downloads
- Top World of Warcraft Addons
- Top Rift Addons
- Top Skyrim Mods
- Top Minecraft Server Mods
- Top Terraria Maps
- Top Starcraft II Maps
- Top Runes of Magic Addons
- Top Warhammer Online Addons
- Top Age of Conan Addons
-
- Curse Client
- Premium
- News
- Giveaways
- Forums
DiamondThreatMeter
Login to Add Favorites
- 0 Likes
- World of Warcraft
- 131,390 Downloads
- Supports: 4.3
- 34 Average Daily Downloads
- Comments
- Created 3/30/2008 8:22:58 AM
- Updated 12/11/2011 9:46:38 PM
- 390 Favorites
- Project Site
- License: All Rights Reserved
- Release Type: Release
- Newest File: Diamond Threat Meter 4.3.0
About DiamondThreatMeter
WoWInterface
DTM is also now hosted on WoWInterface. Go there for an alternate download link: http://www.wowinterface.com/downloads/info9512-DiamondThreatMeter.html
Highlights:
- Complete multi-target threat meter (which makes difference between mobs sharing the same name).
- Independant threat computation. You have a fairly good idea of what one's threat is even if one hasn't DTM installed on one's client.
- Designed for English and French languages. :)
- Configuration is well explained and easily accessable, through Blizzard's interface and bindings menus.
- Final version.
DiamondThreatMeter could only be designed thanks to features Blizzard added to inspection and combat log systems (2.3 and 2.4 patches). :)
2.0.0
- This version and upcoming ones are no longer compatible with WoW 2.4.3 and older WoW versions.
- This build can be considered as a clean up for WotLK Xpac, as some things that weren't needed anymore were removed.
- Configuration settings will be reset, as well as skins.
- DTM no longer has ThreatLib2 emulation: Omen3 no longer uses it and relies solely on Blizzard threat monitor.
- KTM is also no longer supported for emulation; like Omen3, it relies on Blizzard threat monitor.
- Emulation panel has been removed from Engine section.
2.0.1
- DTM will be able to work with WoW 3.0.8 now.
- By default, Native method will be chosen for the threat engine.
- The addon can be considered as discontinued for now.
2.1.0 (final)
- It is now possible to change the anchor of the lists by right-clicking on them.
- This version can be considered as the Final version, there won't be any significant new feature from now on.
4.0.0 Mr.Cool Has added me into the Maintainability aspect in the addon and I will be doing my best to keep it running.
- Made the code compatible with the changes in LUA and XML in update 4.
4.0.0vRu
- (hopefully) Successfully added Russian (ruRU) to DTM. Someone please verify.
- Пожалуйста, простите мое невежество, как я не знаю вашего языка увлекательным.
- Oh yeah. The program now reports (to my knowledge) the correct version to other versions.
4.1 Fixed Syntax.
4.2 I don't play anymore but have updated the TOC and fixed an error that popped up. It's not perfect but works.
4.2.1 Fixed the code correctly thanks to the contribution from **phillshap**. Thanks for your post.
4.2.2 Made a minor adjustment to the Role Selection. Now all you have to do is use the first letter of your role. ( T for tank, D for DPS, H for heals, A for AOE damage, and S for solow with pet ) Very minor change, but I felt that some might appreciate it.
4.3.0 Fixed TOC file. No known breaking changes.
| File Name | Release Type | Game Version | Downloads | Date |
|---|---|---|---|---|
| Diamond Threat Meter 4.3.0 | Release | 4.3 | 791 | 12/11/2011 9:46:38 PM |
| Diamond Threat Meter 4.2.2 | Release | 4.2 | 3,533 | 9/21/2011 3:33:26 PM |
| Diamond Threat Meter 4.2.1 (revision) | Release | 4.2 | 4,275 | 7/28/2011 6:52:06 PM |
| Diamond Threat Meter 4.2 | Release | 4.2 | 1,424 | 7/24/2011 8:50:47 PM |
| Diamond Threat Meter v4.1 | Release | 4.1 | 6,762 | 4/26/2011 10:33:48 PM |
| Diamond Threat Meter 4.0 +Ru | Release | 4.0.1 | 10,952 | 10/28/2010 11:17:36 AM |
| Diamond Threat Meter 4.0 update | Release | 4.0.1 | 699 | 10/27/2010 5:18:21 PM |
| 2.1.0 [final] | Release | 3.2.0 | 32,368 | 8/6/2009 1:17:27 PM |
| 2.0.1 | Release | 3.0.8 | 59 | 1/21/2009 2:06:44 PM |
| 1.7.0 (hybrid, hotfixed) | Release | 2.4.3 | 313 | 10/4/2008 3:04:29 PM |
| 1.6.0 (hybrid) | Release | 2.4.3 | 41 | 8/22/2008 3:46:27 PM |
| 1.5.0 | Release | 2.4.3 | 32 | 8/5/2008 10:24:07 AM |
| 1.4.1 | Release | 2.4.3 | 27 | 7/21/2008 8:14:50 PM |
Comments
Looks like all that needed to be fixed was fixed. Just an entry in the TOC
I don't actually play WoW anymore, but I will make trial accounts here and there and fix little things in the files as I can. Thanks to the others of you that helped others while I was away.
Sorry, I know this question is dumb, but i'm a new user of curse client and wow add-on.
I just don't know how to use your fix, Phillshap.
Should I replace a file, add this script somewhere... I don't know.
Can somebody help me by explaining how to use this fix ?
Thanks.
Unfortunately there are a ton of steps along the way to doing this and I don't know how much you do or don't know about editing source (text) files on your computer. Here's a rough overview:
- find the addon sources you need to change; addon sources are kept in the Addon directory which is under Interfaces, which is in the same directory as the WoW app/exe itself. in this case the files are in the AddOns/DiamondThreatMeter/common subdirectory.
- open the source files you need to edit in a text editor (such as windows wordpad). in this case the only file changed was combatParse.lua
- apply the patch by hand by editing the combatParse.lua source file; the patch output I included is for a patching program but it's not too hard to read. The numbers between the @@ signs are the line numbers in the file where the change goes. each line in the change is preceded by an empty space, a '-' or a '+'. Space means no change, '-' means line deleted, '+' means line added. Of course this is complicated by the comment system which wordwraps postings and removes whitespace. There is probably a way to avoid this formatting but i don't know how to do it.
So in this case, you'd open combatParse.lua, scroll to line 213, and delete the line:
function DTM_DoCombatParse(...)
and then paste in the lines:
-- 4.2 FIXES: added srcRaidflags, dstRaidflags. these flags are currently ignored by DTM
--
function DTM_DoCombatParse(timestamp, event, hideCaster, srcGUID, srcName, sourceFlags, srcRaidflags, dstGUID, dstName, dstFlags, dstRaidFlags, ...)
DTM_DoCombatParse_4_1(timestamp, event, hideCaster, srcGUID, srcName, sourceFlags, dstGUID, dstName, dstFlags, ...);
end
function DTM_DoCombatParse_4_1(...)
That should do it. If it doesn't work or things go wrong you can always delete the DiamondThreatMeter folder and re-download it again to get a copy of the original sources.
Good luck :)
Does the slowdown occur only during battle? If not, then it's probably something else.
If you want to try to track this down, you can try disabling all other addons besides DTM. Also are you getting any lua errors while running wow?
--- Interface/AddOns/DiamondThreatMeter/common/combatParse.lua.bak 2011-02-28 22:40:06.000000000 -0500
+++ Interface/AddOns/DiamondThreatMeter/common/combatParse.lua 2011-07-01 13:02:08.000000000 -0400
@@ -213,7 +213,16 @@
-- * 14/ .Overheal
-- * The amount of overheal. Only for HEAL outcomes.
-- ********************************************************************
-function DTM_DoCombatParse(...)
+
+--
+-- 4.2 FIXES: added srcRaidflags, dstRaidflags. these flags are currently ignored by DTM
+--
+
+function DTM_DoCombatParse(timestamp, event, hideCaster, srcGUID, srcName, sourceFlags, srcRaidflags, dstGUID, dstName, dstFlags, dstRaidFlags, ...)
+ DTM_DoCombatParse_4_1(timestamp, event, hideCaster, srcGUID, srcName, sourceFlags, dstGUID, dstName, dstFlags, ...);
+end
+
+function DTM_DoCombatParse_4_1(...)
if ( useCoolLibParser ) then return nil; end -- Invalidate this function if CoolLib offers us its combat parse service.
timestamp, event, srcGUID, srcName, srcFlags, dstGUID, dstName, dstFlags = select(1, ...);
Omen has always been accurate about threat generated, since it´s using WoWs implemented threat lists. For example, if I (as a tank) do 1000 damage, this would be 3000 threat exactly - not including the *1,02 multiplicator from hands enchant. Melees would have to generate 3300 to get aggro, while Ranged need to generate 3900. Omen displays this correctly, while DTM seems to think, those 3000 threat includes *1,1 (for Melees) already and in this example divides 3000 by 1.1 first, then showing 2727 as threat, saying a Melee would get aggro if he exceeds 3000 threat - which is not true, because he would get aggro when he exceeds 3300 threat, due to some testing (with grey lowlevel weapon autohits) we have done.
Is there a chance for this to get fixed?
Message: ...ace\AddOns\DiamondThreatMeter\DiamondThreatMeter.lua:427: attempt to index global 'ChatFrameEditBox' (a nil value)
Time: 10/15/10 12:03:25
Count: 1
Stack: [C]: ?
...ace\AddOns\DiamondThreatMeter\DiamondThreatMeter.lua:427: in function `OnHide'
Interface\FrameXML\StaticPopup.lua:3468: in function `StaticPopup_OnHide'
[C]: in function `Hide'
Interface\FrameXML\StaticPopup.lua:3505: in function `StaticPopup_OnClick'
Locals: self = StaticPopup2 {
0 =
itemFrame = StaticPopup2ItemFrame {
}
button3 = StaticPopup2Button3 {
}
extraFrame = StaticPopup2ExtraFrame {
}
icon = StaticPopup2AlertIcon {
}
maxWidthSoFar = 320
button2 = StaticPopup2Button2 {
}
moneyFrame = StaticPopup2MoneyFrame {
}
moneyInputFrame = StaticPopup2MoneyInputFrame {
}
text = StaticPopup2Text {
}
editBox = StaticPopup2EditBox {
}
timeleft = 0
numButtons = 2
maxHeightSoFar = 172.68000796511
button1 = StaticPopup2Button1 {
}
which = "DTM_ROLE_POPUP"
}
(*temporary) = nil
(*temporary) = nil
(*temporary) = nil
(*temporary) = "attempt to index global 'ChatFrameEditBox' (a nil value)"