(728Kb)

Updated: 08-06-09 12:26 PM

Add Favorite

Install Help

Pictures

File Info

Updated:	08-06-09 12:26 PM
Created:	unknown
Downloads:	75,843
Favorites:	130
MD5:

DiamondThreatMeter

Version: 2.1.0

by: Mrcoolmods [More]

Hello there

I had uploaded DiamondThreatMeter for quite a long time exclusively on Curse, but I realized I could upload it too on WoWInterface, so here I go

DiamondThreatMeter 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, French and German languages (though the mod will be in English for German players).
- 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).

DTM versions start directly to 1.4.1 (compatible with WoW 2.4.3) on WoWInterface, previous versions are available on Curse :

http://www.curse.com/downloads/details/11838/

My Curse username is MrCool and my avatar is the same, you cannot be mistaken.

Feel free to leave comments. However if you want to do so, please post them on Curse or Curse-forge, I read them on a weekly basis.
Avoid sending me PMs, as I rarely check on them. =p

EDIT: 2.0.1: It has been a long time since I last posted a new DTM version.
Now I have less spare time to code mods, and I also switched my interest on a new mod (a boss mod), so DTM is kinda left in the dust

Blizzard native threat system is pretty robust and so the hybrid/parsing engine of DTM is almost useless now, only the GUI is still (mildly) useful.
I had some more plans to improve it, but I found out programming a boss mod to be more exciting now, as threat has become almost irrelevant since 3.0.2 patch.

Okay, so here comes 2.0.1 build, expect nothing shiny in it, except the mod can now work with WoW 3.0.8, as the latest WoW patch has broken critically the mod (shame on Blizz).

EDIT 2: Here comes the final version, 2.1.0, I managed to find a bit of time to release it.

2.1.0 (final)
* DTM will be able to work with WoW 3.2 now.
* 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.

---

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.

---

Highlights:
* Works fine with WoW 2.4.3 and 3.0.2 (Beta and PTR) like the previous version. :)
* A new textual warning is available for when you regain aggro. Check out the skin editor to configure it.

1.7.0 (Hybrid)
* This build is an hybrid build, which means it can be used on WoW TBC, WoW WotLK Beta test or WoW PTRs without any problem (theorically).
* NameplateLib was renamed CoolNameplateLib to avoid conflicts with other AddOns.
* Combat change checks, symbol change checks and target change checks have been nicely improved.
* A new option has been added in the Overview list settings panel of the skin editor that allows you to display first the mobs you have the aggro of.
* A new service can be turned on in the skin editor to display text alerts when you get the aggro of a mob.
* Nameplate threat bars are now more colorful: they go yellow and orange when reaching the aggro regain threshold.
* The "Who ?" column of Regain list is now more useful when you do not have the aggro of a given mob.
* Mind-controlled players will now be completely ignored by DTM, the overview list pollution they cause is not worth it.
* Some code upgrades.

---

1.6.0 (Hybrid)
* This build is an hybrid build, which means it can be used on both WoW TBC and WoW WotLK Beta test.
* You will just have to turn on the run out-of-date AddOns option to run it on the Beta.
* Fixed some miscellaneous bugs in both Engine and GUI.
* A few tooltips have been rewritten/corrected.
* CAUTION: UnitThreat and other DTM threat info APIs are now prefixed with "DTM_" (e.g: DTM_UnitThreat), to avoid conflict if Blizzard adds
its own APIs during the Beta phase. Any external mod that could use these functions would have to be modified.
* Beta-only changes:
* DTM will pull data from Blizzard native threat functions whenever possible.
* DTM should however continue to use combat events for threat determination between each value update of Blizzard's threat functions.
* Beta players can now find in the Engine options panel a dropdown to change the threat calculation method. Check them out !

---

1.5.0
* Threat can now be displayed on nameplates. Check out the new options! There are unfortunately some restrictions on this new system. :/
* This option can be turned on in a new config panel: "Nameplate".
* New API: DTM_FindGUIDFromName(name).
* Various files in docs folder have been updated.
* The bars of threat list are now right-clickable to make an option dropdown apparear.
* Currently, this option dropdown allows you to specify whether the unit the bar belongs to is a tank or not.
This will cause a tank icon to be displayed in front of the unit. This feature will evolve in a further version. :)
For the moment, DTM will not remember between game sessions who is and who isn't a tank. It will come in a next version.
* A "Reset everything" button has been added, it's now the last resort button in case DTM suffers from errors, especially when changing versions.
* Fixed a bug causing healers not to apparear on threat lists when healing someone engaged against a mob if this healer did not do anything harmful toward any mob engaged in combat (Finally, I got it ! :)).
* Fixed a bug causing header columns labels to show up despite being disabled in the skin editor.
* Fixed incorrect positionning of the ring button occuring when using an UI scale different from 1.

Optional Files (1)

File Name	Version	Size	Author	Date	Type
Diamond Threat Meter 6.0.3a	6.0.3a	427kB	adracamas	11-12-14 08:14 PM	Patch

Comment Options

Page 2 of 4

11-02-08, 01:17 PM
Chronalis A Defias Bandit Forum posts: 3 File comments: 11 Uploads: 1	Is it possible for you to provide the current TPS value as a variable so addons such as Speedo can access it and display it? If it's already in, can you provide details in a comment somewhere here please. Cheers, Chron.

11-03-08, 11:00 AM

forty2j

A Cobalt Mageweaver

Forum posts: 232

File comments: 260

Uploads: 0

Originally posted by Chronalis
Is it possible for you to provide the current TPS value as a variable so addons such as Speedo can access it and display it?

If it's already in, can you provide details in a comment somewhere here please.

Cheers,
Chron.

Wouldn't that fall under the domain of ThreatLib / Omen? DTM is rather self-contained..

.. and you can probably calculate your own pretty easily anyway based on the threat numbers available through Blizzard's API.

11-05-08, 11:54 PM
AnElk A Kobold Labourer Forum posts: 0 File comments: 42 Uploads: 0	patch ... again... sigh As of November 5 and the silly mini-patch, DTM is not working on my system.

11-08-08, 06:19 PM

Chronalis

A Defias Bandit

Forum posts: 3

File comments: 11

Uploads: 1

Originally posted by forty2j
Wouldn't that fall under the domain of ThreatLib / Omen? DTM is rather self-contained..

.. and you can probably calculate your own pretty easily anyway based on the threat numbers available through Blizzard's API.

Here's the quote from the Author of Speedo:

"Ya, I know. But I just don't have the time to pull apart all the Omen/DiamondTM/whatever code. This takes hours and hours ... and with the next version I potentially can start again with that.

[Edit]
If you are able to force the Omen/DTM/whatever developer to provide the TPS data via a function/API to other addons I'll add it again. ;D"

11-11-08, 01:53 PM

forty2j

A Cobalt Mageweaver

Forum posts: 232

File comments: 260

Uploads: 0

Re: patch ... again... *sigh*

Originally posted by AnElk
As of November 5 and the silly mini-patch, DTM is not working on my system.

I just enabled out-of-date addons, and it worked again.

11-11-08, 02:01 PM

forty2j

A Cobalt Mageweaver

Forum posts: 232

File comments: 260

Uploads: 0

Originally posted by Chronalis
Here's the quote from the Author of Speedo:

"Ya, I know. But I just don't have the time to pull apart all the Omen/DiamondTM/whatever code. This takes hours and hours ... and with the next version I potentially can start again with that.

[Edit]
If you are able to force the Omen/DTM/whatever developer to provide the TPS data via a function/API to other addons I'll add it again. ;D"

The point is, right now, the threat is the threat is the threat. All the threat meters are pulling from the Blizzard API, which serves the same purpose ThreatLib used to. There's no more guessing. Whether you're using the built-in UI, Omen, DTM, or Joe's Threat Meter and Vending Repair, the threat is the same.

The best course, then, is if Speedo wants to show TPS values, it should just get them from the Blizzard API, and not rely on any other addon being present. (TPS = (Threat Value) / (seconds in combat)) The only reason for the author to potentially have to do "do it again" is if Blizzard substantially changes that API.

11-23-08, 09:12 PM
Chronalis A Defias Bandit Forum posts: 3 File comments: 11 Uploads: 1	There seems to be some sort of bug with a player sapping a mob, as well as vehicle combat and it's often not possible for me to click the "Close" button to close the error frame.

11-26-08, 11:29 AM

deflepp07

A Kobold Labourer

Forum posts: 0

File comments: 1

Uploads: 0

Originally posted by Chronalis
There seems to be some sort of bug with a player sapping a mob, as well as vehicle combat and it's often not possible for me to click the "Close" button to close the error frame.

Yes, and also has anyone else had it that the threat did not show up until you as DPS hit the mob? Being a rogue and waiting until the right time to jump in can get a bit iffy, lol. A few times this caused me to either wait too long or not long enough.

12-27-08, 06:38 PM

gothicknight

A Flamescale Wyrmkin

Forum posts: 131

File comments: 87

Uploads: 1

Originally posted by deflepp07
Yes, and also has anyone else had it that the threat did not show up until you as DPS hit the mob? Being a rogue and waiting until the right time to jump in can get a bit iffy, lol. A few times this caused me to either wait too long or not long enough.

That is not a problem with the mod. That is actually part of the threat API. Blizzard has made it so you can't see threat until You actually hit the target yourself. All Threat meters have the same problem. Once you hit the target all threat is accurately displayed. All i can suggest is just use a basic hit to bring up the threat on your meter then wait to unleash.

__________________

12-28-08, 03:40 AM

Elhana

A Wyrmkin Dreamwalker

Forum posts: 51

File comments: 8

Uploads: 1

you can fix error by adding new sap level duration to a CC file:
WoW\Interface\AddOns\DiamondThreatMeter\engine\crowdControl.lua

-- Rogue's crowd controls

["SAP"] = {
ignoreGlobalThreat = 1,
notSpammable = nil,
duration = {
[1] = 25,
[2] = 35,
[3] = 45,
[4] = 60,
},
},

and for other classes need to add spell level also obviously, a bit harder in case of shamans - need to add your spell name in WoW\Interface\AddOns\DiamondThreatMeter\common\internals.lua under "-- Crowd control effects" like any other CC effects, like:
["Shackle Undead"] = "SHACKLE_UNDEAD",
["Hex"] = "HEX",

and add in crowdControl.lua
["HEX"] = {
ignoreGlobalThreat = 1,
notSpammable = nil, -- I don't know if it is, figure out
duration = 30,
},

01-04-09, 09:13 PM

SmurfbutcherBob

A Kobold Labourer

Forum posts: 0

File comments: 3

Uploads: 0

click the "Close" button to close the error frame.

For closing the error pane... scroll through the end of the text (much like a EULA) and the close button will be enabled.

Possible super-kludge to mask the SAP bug -
...ce\AddOns\DiamondThreatMeter\engine\crowdControl.lua:282: attempt to compare number with nil

Note this is not a fix, per-se, in that Elhana's actually resolves the problem - this solution merely fixes what happens with "unknown" spells, giving them a duration that isn't a pop-up causing nil.

engine\crowdControl.lua, circa line 196: add the line in bold...

-- Leave it as it is.
end
if (durationData == nil) then durationData = 0; end
return data.ignoreGlobalThreat, data.notSpammable, durationData;
end

(edit: single line for easier cut/paste. )

Last edited by SmurfbutcherBob : 01-15-09 at 04:44 PM.

01-21-09, 01:04 AM
Shinryu Masaki A Kobold Labourer Forum posts: 0 File comments: 26 Uploads: 0	Doesn't work since patch 3.0.8 came out. Hope this get fixed soon, I do not want to go back to Omen... =( shivers

01-21-09, 04:13 PM

Fonjask

A Fallenroot Satyr

Forum posts: 25

File comments: 266

Uploads: 2

Oh ma gahd!

Thank you so much for updating this for patch 3.0.8!

But...

* The addon can be considered as discontinued for now.

Noooo!!!

Could you at least permit us to send you an email when it's broke! I really hate omen and there's no threat meter like DTM out here!

Please consider

Thanks in advance,

Fonjask

__________________
~~~~~~~~~~~~

01-21-09, 06:50 PM

Phanx

Cat.

Forum posts: 5617

File comments: 2321

Uploads: 54

Re: Oh ma gahd!

Originally posted by Fonjask
I really hate omen and there's no threat meter like DTM out here!

Not to derail this too much, but what specifically don't you like about Omen? No threat meter requires syncing anymore, so really the only differences now are in code quality and visual appearance, and Omen is pretty well-written and very customizable.

01-21-09, 11:44 PM

jadakren

A Flamescale Wyrmkin

Forum posts: 103

File comments: 112

Uploads: 2

Re: Re: Oh ma gahd!

Originally posted by Phanx
Not to derail this too much, but what specifically don't you like about Omen? No threat meter requires syncing anymore, so really the only differences now are in code quality and visual appearance, and Omen is pretty well-written and very customizable.

I notice this mod (diamond) still looks like crap.

Page 2 of 4

Report this File

Category Jump: