I Want to See Big Numbers too!

[_Chloe]

Been looking at the Wotlk API and it might just be possible with that and the combat log changes that came with 2.4. Cross your fingers.

[moduspwnens]

Yes, a filter based on incoming threat would be nice. I'd put it somewhere around 15 or 20. It's also be cool to be able to have the spell's name beside it.

[Vividd]

Sadly with the way it gets the threat data right now I can't determine directly what spell caused it, or who threat was created on. These are limitations I have in using Threat-2.0.

I think it would be possible if Threat-2.0 itself was modified some.

Anyway, I've uploaded a new version which should be available for download soon.
I've added two new options, one to set a minimum threat to report, and another to enable it showing when not grouped.

[Zappi]

You can take my code from TankadinTps, it's published under the GPL

TtpsCombatEvents.lua
TtpsClass.lua
TtpsPaladin.lua
TtpsDebug.lua

are the relevant files. Change every call to TtpsData to a method in your addon and you'll get the threat, unit GUID, spell ID etc.

[Vividd]

I appreciate it, but there's still the issue that this addon isn't only for Paladins.

[Zappi]

TtpsWarrior.lua
TtpsDruid.lua