Outside of these forums, a majority of the people I know still use both CT and KTM, and have zero interest in switching. For half of them, it's "if it isn't broke, don't fix it" and for the other half it's "extract? folder? huh? lol! my dog isn't home to install addons right now." Ultimately I give up in frustration. I'm tired of trying to peddle mods and argue against stupidity.
External to Threat core is certainly fine. If it works, I ain't picky :P. Hopefully it'll be done by the time I hit 70 :P
I agree that sending data KTM data to player that don't have ThreatLib would be really nice. I think over 90% of the players i have raid with use KTM, but only a couple of friends use ThreatLib (and they are UI tinkerers). I actually think it would help getting people move to ThreatLib if it was fully compatible with KTM, simply because most players don't want two addons doing the same thing and forcing others to have KTM just to to send Threat to those who haven't replaced it yet is probably not an option.
Would be interesting to plot everyones threat in a graph from both KTM and ThreatLib throughout an evening to see the differences.
The problem is that by making threat and Ktm compatible, you might be agreeing to the constraints/limitations that KTM has...
What if threat is able to list Pet and Hunter DPS seperately....KTM can't do that.. it combines them.. so now What? KTM doesn't have multiple target threat, only the target that is the 'selected' target... So we're sending all this multi-target data over the wire to who again, if as many people as you say 'dont want to bother with fixing it'?
I'm okay with backwards compatibility, as long as it doesn't adversely affect forward progress. So far, I've never seen a software project not impeded by it.
You just dumb down the KTM output. For pets, KTM wants max(pet, master). It only wants one target, so only give it the selected target (or however KTM handles it). I don't see oRA being hindered by keeping compatability with CT. It's not like Threat is trying to use KTM's comm protocol for everything. It has it's own, and it'd be nice to broadcast KTM's as well, as best it can translate. No hinderance at all.
Yeah of course it should not make the Threat progress much slower. But when it's reaching a more stable and usable state for the masses maybe it's what needed. Should work by just sending KLH the data it expects the receive.
the only reliable way to deal with KTM not tracking Multi Targets is to use what KTM has, that is Setting a Master Target.
IIRC, once a MasterTarget is set, only threat information about Said Target is xmited. Use that. If a MT target is set then xmit over the KTM chl the treat values for KTM, and proccess information from the KTM chl for said target with in threat-1.0; for healers, tho you might want to add threat to global as well, tho off spec healers might have problems with that.
that IMHO would keep things consistant.
External to Threat core is certainly fine. If it works, I ain't picky :P. Hopefully it'll be done by the time I hit 70 :P
Would be interesting to plot everyones threat in a graph from both KTM and ThreatLib throughout an evening to see the differences.
What if threat is able to list Pet and Hunter DPS seperately....KTM can't do that.. it combines them.. so now What? KTM doesn't have multiple target threat, only the target that is the 'selected' target... So we're sending all this multi-target data over the wire to who again, if as many people as you say 'dont want to bother with fixing it'?
I'm okay with backwards compatibility, as long as it doesn't adversely affect forward progress. So far, I've never seen a software project not impeded by it.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumthe only reliable way to deal with KTM not tracking Multi Targets is to use what KTM has, that is Setting a Master Target.
IIRC, once a MasterTarget is set, only threat information about Said Target is xmited. Use that. If a MT target is set then xmit over the KTM chl the treat values for KTM, and proccess information from the KTM chl for said target with in threat-1.0; for healers, tho you might want to add threat to global as well, tho off spec healers might have problems with that.
that IMHO would keep things consistant.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumBut it won't have it. ThreatToKTM send *your* threat and will never send max(pet, master), that would be a non-sense.
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumso, there's a nil reference at
Threat-1.0/ThreatClassModuleCore.lua:712
if I summon my Water Elemental while I have a fresh mob targeted.
(self.targetThreat is nil)
Revision: 40194
cheers,
mitch
-
View User Profile
-
View Posts
-
Send Message
Curse Premium