Anyways, I got a question about the backward compatibility of Omen/Threat since I know many of my guildies don't update regularly their mods. If they run let's say today's version, will the value they return to the rest of the raid be wrong in let's say a month (assuming some changes to the threat calculation/values/etc. will be made).
Anyways, I got a question about the backward compatibility of Omen/Threat since I know many of my guildies don't update regularly their mods. If they run let's say today's version, will the value they return to the rest of the raid be wrong in let's say a month (assuming some changes to the threat calculation/values/etc. will be made).
Very likely. Don't recommend the mod to people that don't update often until an official 1.0 release.
From http://www.forumopolis.com/showthread.php?t=52465...
"KTM interoperability is currently not supported. We would like to support it, but the protocol that KTM uses is rather limited, so we're going to have to think hard about how to best do it. It is definitely on the wishlist, however."
The last couple of commits to Threat-1.0 have started the interoperability with KTM.
KTM read support is into ThreatLib and Omen. You'll see people broadcasting KTM data with a * next to their names in Omen. Note that this data may not be considered reliable if there are multiple targets of interest in the fight.
Would there be a conflict if I ran both KTM and Omen for a while?
example sending double threat data?
No, there's no conflict. KTM doesn't know about ThreatLib/Omen, so it ignores it, and ThreatLib ignores any KTM data from other people running ThreatLib.
Would there be a conflict if I ran both KTM and Omen for a while?
example sending double threat data?
No, there's no conflict. KTM doesn't know about ThreatLib/Omen, so it ignores it, and ThreatLib ignores any KTM data from other people running ThreatLib.
Using a version from last night and running both KTM and Omen, I showed up in Omen with the asterisk after my name indicating my threat data was from KTM. If the above was a recent chance since last night, then just ignore me :)
Will my correct threat be shown on KTM if I'm using Threat-1.0? Perhaps it was said already, but I'm a little slow sometimes and need clarification. ;)
edit: or does it not work in that direction? (or not yet? ;) )
Will my correct threat be shown on KTM if I'm using Threat-1.0? Perhaps it was said already, but I'm a little slow sometimes and need clarification. ;)
edit: or does it not work in that direction? (or not yet? ;) )
I tested out r37985.1001 in Shadow Labs this afternoon. First off, very impressed with how quickly you got the addon to this point. Secondly, two concerns, when I would feign death the Omen meter would not register the threat dump until I re-engaged the target or attacked something else. Was that intentional? Or has it already been addressed? And there seems to be something off with Misdirection, my first shot only goes to the tank, but the second and third shot gets recorded on both our threat levels.
And finally a feature suggestion, bars like on KTM that show "Tank Lose Aggro" and "Tank Regain Aggro" levels would be awesome.
Feedback:
After just loading it was way off. Didn't detect my Destruction threat reduction. And what was weirder, gave me threat for my dots higher than the actual damage. Didn't register Soulshatter at all. EDIT: the higher Dam was no doubt caused by Sacced Felhunter buff in retrospect.
After being a bit disappointed at first I suddenly noticed it had 'caught on to' my spec and was giving correct Destruction talent threat. Maybe I opened my panel, I don't remember. Unfortunately Soulshatter (50%threat reduction) still doesn't register. Also, casting a curse assigns 134 and not 54 as mentioned in the documentation. EDIT: I may have to test that again, could also be Felhunter related.
I noticed I get credited for Demonic Sacrificed Felhunter's mana gain. Not sure if that is supposed to generate threat. Will read up. EDIT: http://evilempireguild.org/guides/kenco2.php seems to justify this threat.
We had a raid member go offline mid fight and Omen/ThreatLib remembered his threat. However, he remained offline for a while, and we continued for several pulls, and his threat remained displayed by Omen until he came back online. It should be zeroed at the end of combat along with the other raid members. I was using Omen 38064/ThreatLib 38041 at the time (I was the only Omen user, the rest of the raid have KTM). I also had Violation loaded at the time (all addons updated via WAU).
I'm the mod monger for my guild. I will be starting to beta this with myself [shadow priest] my friend [warrior/MT] and my wife [healing priest].
I expect to jump ship to these mods shortly. You guys rock. I have never once thought you'd ace2 KTM, just because of the the kind of mod and the way it seemed to brute force its data.
I'm sorta dumb when it comes to understanding the 'way things work'. But my understanding is that KLHTM is very processor hungry due to the way it figures out threat. Is that just the nature of the beast? Or is Threat-1.0/Omen less memory/processor intensive?
Thanks to you guys for working on this mod. I look forward to trying it out.
Right now, you can see threat from people using KTM, but they will not see your threat if you are only using Omen. Basically, Omen can read KTM data, but KTM cannot read Omen data.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
Anyways, I got a question about the backward compatibility of Omen/Threat since I know many of my guildies don't update regularly their mods. If they run let's say today's version, will the value they return to the rest of the raid be wrong in let's say a month (assuming some changes to the threat calculation/values/etc. will be made).
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumVery likely. Don't recommend the mod to people that don't update often until an official 1.0 release.
Awesome news. :)
-
View User Profile
-
View Posts
-
Send Message
Curse Premiumexample sending double threat data?
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumNo, there's no conflict. KTM doesn't know about ThreatLib/Omen, so it ignores it, and ThreatLib ignores any KTM data from other people running ThreatLib.
Using a version from last night and running both KTM and Omen, I showed up in Omen with the asterisk after my name indicating my threat data was from KTM. If the above was a recent chance since last night, then just ignore me :)
-
View User Profile
-
View Posts
-
Send Message
Curse Premium-
View User Profile
-
View Posts
-
Send Message
Curse Premiumedit: or does it not work in that direction? (or not yet? ;) )
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIt doesn't work in that direction yet.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumAnd finally a feature suggestion, bars like on KTM that show "Tank Lose Aggro" and "Tank Regain Aggro" levels would be awesome.
Thanks for the hard work!
After just loading it was way off. Didn't detect my Destruction threat reduction. And what was weirder, gave me threat for my dots higher than the actual damage. Didn't register Soulshatter at all. EDIT: the higher Dam was no doubt caused by Sacced Felhunter buff in retrospect.
After being a bit disappointed at first I suddenly noticed it had 'caught on to' my spec and was giving correct Destruction talent threat. Maybe I opened my panel, I don't remember. Unfortunately Soulshatter (50%threat reduction) still doesn't register. Also, casting a curse assigns 134 and not 54 as mentioned in the documentation. EDIT: I may have to test that again, could also be Felhunter related.
I noticed I get credited for Demonic Sacrificed Felhunter's mana gain. Not sure if that is supposed to generate threat. Will read up. EDIT: http://evilempireguild.org/guides/kenco2.php seems to justify this threat.
Looking forward to this one. A lot.
Fire mage
I expect to jump ship to these mods shortly. You guys rock. I have never once thought you'd ace2 KTM, just because of the the kind of mod and the way it seemed to brute force its data.
I'm sorta dumb when it comes to understanding the 'way things work'. But my understanding is that KLHTM is very processor hungry due to the way it figures out threat. Is that just the nature of the beast? Or is Threat-1.0/Omen less memory/processor intensive?
Thanks to you guys for working on this mod. I look forward to trying it out.
-
View User Profile
-
View Posts
-
Send Message
Curse Premium