ClassicThreatMeter
ClassicThreatMeter is a threat meter for WoW Classic that attempts to provide reasonably accurate estimates of your group's relative threat values against enemy NPCs by recording pertinent data from the combat log and making calculations from that data.
FAQ
Q: Why am I not seeing other players in ClassicThreatMeter?
A: Other players must have ClassicThreatMeter or a compatible AddOn enabled in order to track their threat similar to how KLH Threat Meter/Omen required compatible AddOns communicating threat to one another in Vanilla/TBC.
Q: Why isn't ClassicThreatMeter using the built-in threat API?
A: To answer simply, it can't! Blizzard added in a threat API in patch 3.0.2 for WotLK and has been in the game since, but it has been purposely removed for WoW Classic, which means we must rely on combat log parsing.
Q: How does ClassicThreatMeter handle multiple targets?
A: The combat log in WoW Classic is fortunately much more detailed than that which was available in the game originally before patch 2.4. This allows us to track NPCs by GUID (global unique identifier), and there should be no issues with mobs having the same name and threat becoming muddled between them. It is also designed in such a way that effects that are meant to add divided threat between active targets, such as heals and buffs, are able to do so.
Q: Why are there so few options to customize the threat window?
A: ClassicThreatMeter is still a very young AddOn. More features and customization options will come over time.
Bug Reports / Feature Requests
Please submit any bug reports or feature requests here.
I love your add-on. I use it mainly on my hunter to watch my threat level to keep from pulling aggro off my pet. Recently, I've noticed that a setting change I make keeps reverting after every logout. I've set the maximum count bar to 2 so it shows me and my pet for each mob we kill. It always reverts to 1 after every logout. All my other add-ons keep their settings. Is there some way to fix this?
My addon list:
hello and thx for addon.
I use Elvui and addonskin integration to right chat panel,
addonskin can embeded 2 windows, one is use for detail and i want second for CTM, but i don't find the name of the windows .
i try CTM ,classicthreatmeter, and menace (game in french) and nothing work.
If i use integragion with addonskin on 1 windows, sized half on chat, on each restart/reload , the size take all chat.
Sorry for my english
can you help me ?
In reply to kordman1:
i find a way, if anybody want :
set addonskin to 2 windows, set first with details, left the second free.
with this, details take half of chat, et i manually place and size CTM in the other half part
.
i'll ask to Azilroka a support for CTM in addonskin classic.
again thx for addon. have fun a good game
Doesn't even work well with pets. Seriously what is the point.
Thanks for this awesome addon :) Unfortunately most people do not have this installed during leveling, but I wanted to use the colored namesplates anyway while tanking dungeons. The threatmeter was kind of useless for me though if no other members of the group had it installed. Since there is no option to hide the bars but keep the colored nameplates, I changed a lua file to get the result I wanted.
In case someone else is searching for the same thing:
- Open core/core.lua
- go to "function CheckVisibility()"
- replace "local hide = (c.general..." with "local hide = true"
Hello, may i ask you for the name of the font which you are using in your addon?
thanks in advance
(possible issue?) I just installed the addon and noticed that my druid's Demoralizing Roar (currently rank 3, in Bear Form) doesn't register any threat on the threat meter window. Overall the addon looks very promising, nice work.
In reply to Masauwu:
This should be fixed now in the latest update.
Is there a macro or something to toggle the visibility of the window?
In reply to vladchatb:
Nothing like that at present, but there are visibility options in the config that can be access via /ctm.
Is this compatible with players who have the Details! threat meter?
In reply to Moreorlessmaybe:
It will be compatible if they're running compatible versions of the threat library. The TinyThreat module of Details! does embed the same threat library that CTM uses, so they should be compatible.
Feature request:
Addon is unfortunately kinda useless if it requires other people to have the addon.
As far as I reckon, it just parses the combat log. But in combat log you can see what other players do as well? (Doesn't recount work like that?) Maybe it would be possible to rewrite it to not allow other players to have it installed.
In reply to vectros93:
Please see comment #38 below where I just wrote about this. It does parse the combat log, but it is missing some information that cannot be gleamed unless you are the player using certain abilities.
> Q: Why am I not seeing other players in ClassicThreatMeter?
> A: Other players must have ClassicThreatMeter or a compatible AddOn enabled in order to track their threat similar to how KLH Threat Meter/Omen required compatible AddOns communicating threat to one another in Vanilla/TBC.
This is unnecessary in the modern API. Inside an instance, every combat action is visible in all player's logs now. Outside an instance, you can use the millisecond timestamp with two GUIDs to parse the information such that if you were communicating you could eliminate duplicates. Previously this was required because you couldn't parse what happened to separate duplicate entries, and inside an instance, you could still out-range combat log entries.
Please don't require everyone to install your mod, and expand the processing so that a Tank can have an accurate log even if playing with noobs.
In reply to PerrinGaiden:
It is necessary.
While you can pick up spells by spellName (as spellID always returns 0 in the CLEU payload), you can't tell which rank was used. In addition, you can't inspect another player's talents to see if they have spent points in talent modifiers. You must be in range of the player to track gear changes (needed especially for abilities which apply threat values which scale based on attributes like weapon speed).
You can do it, but you'll be inaccurate in the process. I am considering a fallback that allows guesswork by assuming max rank always and relevant modifiers are there (which can be be improved somewhat by seeing what spells are used and what auras a player has), but I will never be making this the only option if implemented, as it simply is not the better option for accuracy. Probably would have the fallback controllable by the raid leader / raid officers (assist) so that they can still choose to require their group run it for greater accuracy. Omen also had the combat log afforded to them (even with the ability to have spellIDs and talent inspection) in TBC when patch 2.4 gave us the new combat log format, and it too required players use a compatible addon for these very reasons.
CTM isn't required. The threat library it uses is. Adoption for it is being picked up by other addons.
Hi, are there any plans on profile/per character settings? Currently, when I am switching characters (one is tank and other dd) I have shared settings and have to check/uncheck invert coloring for tanks.
In reply to Huntawoo:
I'll add this in to a future release.
since the update I'm seeing this error...
Date: 2019-09-02 05:36:44
ID: 2
Error occured in: Global
Count: 680
Message: ..\AddOns\ClassicThreatMeter\core\core.lua line 499:
attempt to index global 'threatColors' (a nil value)
Debug:
ClassicThreatMeter\core\core.lua:499:
ClassicThreatMeter\core\core.lua:482
[C]: CompactUnitFrame_UpdateInRange()
..\FrameXML\CompactUnitFrame.lua:299: CompactUnitFrame_UpdateAll()
..\FrameXML\CompactUnitFrame.lua:176: CompactUnitFrame_SetUnit()
...e\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:250: OnAdded()
...e\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:84: OnNamePlateAdded()
...e\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:42:
...e\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:33
Locals:
self = NamePlate1UnitFrame {
0 = <userdata>
selectionHighlight = <unnamed> {
}
maxDebuffs = 0
unit = "nameplate1"
RaidTargetFrame = <unnamed> {
}
maxDispelDebuffs = 0
disableMouse = true
inVehicle = false
statusText = <unnamed> {
}
optionTable = <table> {
}
newUnit = true
healthBar = <unnamed> {
}
name = <unnamed> {
}
maxBuffs = 0
unitExists = true
displayedUnit = "nameplate1"
LevelFrame = <unnamed> {
}
}
unit = "nameplate1"
nameplate = NamePlate1 {
0 = <userdata>
driverFrame = NamePlateDriverFrame {
}
GetPreferredInsets = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:299
GetAdditionalInsetPadding = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:288
ApplyOffsets = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:281
OnRemoved = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:268
OnAdded = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:246
namePlateUnitToken = "nameplate1"
UnitFrame = NamePlate1UnitFrame {
}
OnOptionsUpdated = <function> defined @Interface\AddOns\Blizzard_NamePlates\Blizzard_NamePlates.lua:275
}
status = 3
(*temporary) = <function> defined =[C]:-1
(*temporary) = <unnamed> {
0 = <userdata>
r = 0.999998
b = 0
g = 0
barTexture = <unnamed> {
}
border = <unnamed> {
}
background = <unnamed> {
}
}
(*temporary) = <function> defined =[C]:-1
(*temporary) = nil
(*temporary) = "attempt to index global 'threatColors' (a nil value)"
InCombatLockdown = <function> defined =[C]:-1
C = <table> {
font = <table> {
}
general = <table> {
}
warnings = <table> {
}
frame = <table> {
}
backdrop = <table> {
}
bar = <table> {
}
}
UnitThreatSituation = <function> defined @Interface\AddOns\ClassicThreatMeter\core\core.lua:58
unpack = <function> defined =[C]:-1
In reply to Hyattmeister:
Sorry about that. This was introduced in the last update, but I've just pushed a new one specifically to address this. Please try 1.06.