Authors CurseForge

If i recall some blue posts stated that the ingame threat meter wouldn't show the exact threat, so you're still guessing

The APIs are most certainly there:

New CVars:
+ "threatMinimap", -- default: "1"
+ "threatWarning", -- default: "1"
+ "threatWorldText", -- default: "1"

New APIs:

+ "GetThreatStatusColor",
+ "IsThreatWarningEnabled",
+ "UnitDetailedThreatSituation",
+ "UnitThreatSituation",

New Events:

+ "UNIT_THREAT_LIST_UPDATE",
+ "UNIT_THREAT_SITUATION_UPDATE",

At a cursory glance you can tell what your threat is (as a percentage) on a given mod by quering the API when UNIT_THREAT_SITUATION_UPDATE fires. As expected this means that there doesn't need to be any more addon communication, but there also won't be a pure threat number exposed. It seems you will be able to tell how far you are away from pulling aggro which is enough.

Why does this need to spread like wildfire? All this means is no one will need to download threat meters anymore, since this will handle 95% of the gamers.

Since the threat is only shown in tooltip/BlizzFCT, a threatmeter with bars can be viable I think :)

It's possible we could end up with either a build-in meter or a custom build meter. I think it will be a build-in meter despite Blizzard's objection to such things.

Quote from Ydrisselle »

Since the threat is only shown in tooltip/BlizzFCT, a threatmeter with bars can be viable I think :)

Of course, but why do they matter for most players anymore? All player X needs to know that he is 70% of the tank's threat, not how much threat he has compared to anyone else (tanks excluded of course)

AoE aggro and healer aggro. I agree that this is a very minority need. Most folks will probably not need addons or use addons for reskinning.

Also for fights like Bloodboil, it would be harder for multiple tanks to be close
to each others threat.

Quote from Xinhuan »

An exact number is still useful.

If I am a mage, and I'm at 120% of the tank's threat at range (Blizzard's function would return me at 1.2/1.3 = 92.3% threat), it is still highly useful to know how large that remainder 7.7% is. 7.7% of 100k threat is 7700 damage, 7.7% of 500k threat is 38k damage. I know that I can pull aggro with one spell that crits at 8k in the former, but not the latter.

In this regard, absolute difference between you and the tank is far more useful than a percentage difference, if my maximum burst (say a ret pally can burst 10k in 1 second easily) is 10k, then a safe buffer zone is always to stay 15k absolute value below the tank.

Same for me, as a Rogue I need to ride the tanks aggro till just about taking over to be worth a Raid slot, so I would need more than just a percentage

I agree that an exact number is very useful, as a tank, I like to know how far behind the DPS's are. It shouldn't be too much of a change to keep track of the exact amound of aggro the tank generates (100% reliable since he'll have the addon installed) and to adjust values based on blizzard's communicated percentage. A nice info imho, I'll be happy to see how far threat meters will go with this :)

Quote from Xinhuan »

It won't go very far, its just a number for each person in the raid for each mob, and displaying it in pretty bars. How hard is that? lol.

Unless someone can think of more unique ways of displaying threat such as in ovals or pentagrams instead of bars or pullout bars.

Actually, it would be awesome to be able to see everyone's threat over time (over the course of, say, a boss fight) as an overlaid line graph, or series of concurrent rolling line graphs. It would make a nice screenshot to show people how much more steep and spiky Hunter threat generation is without any passive threat reduction >.>

I really would like to see threat levels in the combat log. but I guess that won't happen .)

All player X needs to know that he is 70% of the tank's threat, not how much threat he has compared to anyone else (tanks excluded of course)

Well, raid leaders maybe want to have an overview. :-)

new infos from forum:

Aggro Warning System

NOTE: THIS IS STILL UNDER REVISION AND MAY CHANGE IN THE FINAL RELEASE
(this is always true of anything posted here, but this is still in active development)

First, some definitions:
* mob - enemy creature
* threat list - a mob's list of possible targets, along with each possible target's current threat value
* threat situation - the situation that a unit is currently in (either globally, or with respect to a certain mob)
* scaled percentage - a threat percentage, where 100% means you will pull aggro (become the primary target of the mob), and thus this % cannot be higher than 100% under normal circumstances
* raw threat percentage - the percentage of the units threat when divided by the threat of the mob's current primary target, this % CAN be over 100%

Now the API functions:

state = UnitThreatSituation(unit, mob)


Returns the unit's threat situation with respect to the given mob. The state can be one of the following values:
nil = the unit is not on the mob's threat list
0 = 0-99% raw threat percentage (no indicator shown)
1 = 100% or more raw threat percentage (yellow warning indicator shown)
2 = tanking, other has 100% or more raw threat percentage (orange indicator shown)
3 = tanking, all others have less than 100% raw percentage threat (red indicator shown)

state = UnitThreatSituation(unit)


Returns the unit's maximum threat state on any mob's threat list.

isTanking, state, scaledPercent, rawPercent, threatValue = UnitDetailedThreatSituation(unit, mob)


Returns detailed information about the unit's state on the mob's threat list.
isTanking is true if the unit the primary target of the mob (and by definition has 100% threat)
state is the unit's threat situation, as listed above.
scaledPercent is the current percent threat of the unit, scaled in the 0-100% range based on distance from target.
rawPercent is the current percent threat of the unit relative to the primary target of the mob.
threatValue is the amount of threat that the unit has on the mob's threat list. This is roughly approximate to the amount of damage and healing the unit has done.

r, g, b = GetThreatStatusColor(state)


Returns the colors used in the UI to represent each major threat state.
.
.
Now the new events:

UNIT_THREAT_LIST_UPDATE


* fired when a mob has its threat list updated. The mob that had its list updated is the first parameter of the event.

UNIT_THREAT_SITUATION_UPDATE


* fired when a unit's threat situation changes. The unit that had a change in threat situation is the first parameter of the event. Note that this only triggers when major state changes, not when the raw threat values change.