ThreatClassic2
ThreatClassic2 is a threat meter for WoW Classic that provides reasonably accurate estimates of a monster's threat table based on LibThreatClassic2. It is compatible with all other AddOns providing threat data through LibThreatClassic2 and created as the successor of the abandoned ClassicThreatMeter.
FAQs
Q: Is this addon compatible with Details Tiny threat?
Yes! In fact any addon that uses LibThreatClassic2 (the library behind this addon) is compatible. You can make sure to always have the latest version of the threat library by installing this addon and hiding it, while still using another addon for display without any negative impact. ThreatClassic2 makes sure that the latest version of LibThreatClassic2 is loaded.
Q: Why use ThreatClassic2 instead of ClassicThreatMeter?
The author of ClassicThreatMeter left the addon with a lot of bugs, like spamming "You are not in a raid" in Alterac Valley and 25% bonus aggro for Warrior Defiance talent instead of 15%. ThreatClassic2 bundles LibThreatClassic2, which comes with a ton of bug fixes and provides new boss modules for handling Onyxia and Ragnaros threat mechanics.
Q: Why am I not seeing other players in ThreatClassic2?
A: Other players must have ThreatClassic2 or a compatible AddOn with LibThreatClassic2 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 ThreatClassic2 using the built-in threat API?
A: It's unfortunately not possible. Bizzard added the 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 ThreatClassic2 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: ThreatClassic2 is based on ClassicThreatMerer. More features and customization options will come over time. So far I added an always hide option, so players can install the addon to share their Threat data in the background.
Please submit any bug reports or feature requests here
i am not native. sorry for not accurate english. as far as i know , in case melee class, if threat is over 110% , mob's head is turn to melee cclass from tank.
do threatclassic2 show 110% on display? or only show max 100%? i want to know this part.
In reply to 코코팜맛있어:
it shows 100% for gaining aggro by default. You can turn on "show raw threat percentage" in options and it shows 110% then. I will release Korean translations with the next version.
In reply to dfherr:
thank you for your kindness.
For some reason I can't alter the RGB colors correctly in the config.lua. I wanna make the text in an orange color with 255, 135, 0. But whenever I change the green to any number from 1-255 and keep blue at 0, it turns yellow. Doesn't matter which value I choose it always turns out yellow. And if I also change the blue value to any number between 1-255 the text turns white, doesn't matter which value.
In reply to powntus4:
which color exactly are you editing and in which file exactly? There is different behavior for your saved configs and the default values.
In reply to dfherr:
core > config.lua and then font setting > color (the one that even says font color)
In reply to powntus4:
these are floats not 8bit integers. 255 = 1 . 0 = 0. 135 ~ 0.53
In reply to dfherr:
okey cool, thanks!
Morning All,
Could someone confirm to me if the Blessing of Salvation bug has been fixed with the latest release please? I tend to remove it manually anyway but i like to be extra cautious :)
In reply to Deathisi1:
yes it's fixed as stated in the changelog. removing manually or buffing over it had no influence on the bug (that was a misinformation by other authors)
In reply to dfherr:
Wonderful, thanks dfherr
Hello
We have a problem where we can't see our main tank on the meters on some encounters (yesterday on vaelastrasz, broodlord and chromaggus) while he still sees us. He is using both details and threatclassic2 and also has the old classic threat meter installed. What could be the problem and how can we fix it?
P.S. the versions are all updated
In reply to _ForgeUser1652519:
The problem is that he has the old threat meter installed. It sends out unnecessary messages and thus reaches the message limit. The old threatmeter is also not optimized for BWL and sends out a lot of unnecessary messages for trash mobs.
Have a small suggestion: Allow custom colors for specific people/tanks. I'd like to be able to highlight offtanks for example, so that it's easier to tell visually whether you're about to pass them or not (for bosses with CC mechanics like hakkar or tank swap fights or stuff like that).
Hello, I've recently updated from 2.07. The window position is moved (in my case partially off screen) if I lock position and reload ui. Does not happen, if I leave it unlocked. Also, if I uncheck "Lock" the window returns to it's correct position. I've cleared WTF. Any ideas what might be the problem?
In reply to Secret_Pipe:
this sounds like corrupted settings. you sure you cleared wtf correctly?
otherwise try relogging. reloadui isn't the same as a relog. Relog saves settings to disk, reloadui doesn't.
Relogging does not help. I've deleted all tc2 luas in wtf.
In reply to Secret_Pipe:
did you also delete the .bak files? so it doesn't fall back to those (dunno if that's a thing)? Also make sure to close the game before deleting them.
There is one in <account>/SavedVariables AND one in <account>/<server>/<character>/SavedVariables.
In reply to Secret_Pipe:
you could also try updating the position through the options panel instead of dragging the window. or by dragging the window. if you always did one, maybe the other one fixes it. what checking lock does it put the window back to it's "saved" position from the settings. so this is most likely corrupted settings in some way.
What does leaving it unlocked and relogging do?
In reply to dfherr:
- unlocked & relogg: position remains where I've actually moved the window (with mouse + sliders), but as soon as I lock & relogg the position is changed
- yes, I've cleared all files while game was closed
- if scale is below 90 I'm forced to move with mouse, because the X/Y offset sliders scale aswell, I guess? for instance, I can't move the window all the way to the bottom of the screen or to the right with only the sliders in the option menu (I have to check "show header" and drag with mouse). I've circumvented this problem by staying @ 90 scale and manually reducing bar sizes for now, since it seems the position remains correct with these settings (only using offset sliders).
- Apparently, if the mouse is involved with dragging/resizing and the window is locked the position changes after relogg.