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 :
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.
* 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.
* 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.
* 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.
* 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.
* 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.
* 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 !
* 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.