Once an official release is made, I'll release "super stable" releases to wowi, curse, etc. The trunk will be kept relatively stable, with changes not being committed unless they've been tested and are believed to work as expected. Dangerous changes will be made on a branch and merged once they've been debugged and tested.

Rough ETA for when this will happen? I'm kinda waiting for the stable version before evaluating this for my raid.

Once I've got the bugs worked out, really. Threat's feature-complete, Omen's almost feature-complete, and it's just a matter of polish and debugging right now. There are still some showstopper bugs I'm wanting to knock out before I stamp it production-ready, but the design expansion has basically stopped.

Killed Leotheras today and used Omen the first time on this encounter.

The Leotheras-Mod was totally screwed up - no proper resets after his demon phases or after the whirlwind.
Also one of our holy priests always was on top of the aggro list.


Has anyone else encountered the same problems when fighting Leotheras?

We killed Void Reaver with:

/script AceLibrary("Threat-1.0"):SetNPCModuleValue("VoidReaverKnockbackMultip lier", 0.8)

20% threat reduction seems accurate; I didn't notice major discrepancies, so it's at least close.

If I can get someone else to validate 20%, I'll set it to that in the trunk.

You can reset the threat by yourself.

We've only recently started using Omen, are we meant to do it manually all the time? Or is it meant to do it automatically and we should have just done it manually because it didnt work?

This. Hence your post was quite useful to Antiarc, Zork was just offering an alternative option.

Thanks.
BTW, love your work Antiarc!
Just need to convince some of those that raided to stick with it.

We had similar issues with Nightbane last week, where a druid (feral) pulled aggro at 90%. Additionally, there seemed to be a partial reset of aggro during the transition. Our warrior was nearly immediately at 15k threat after the transition, I doubt he can generate that much threat that quickly.

It was set to either 25% or 30% depending on when you downloaded it. We're doing VR this week, too, so I'll have a chance to test it.

I made some major changes to both Threat and Omen last night which should address the vast majority of weird, odd threat-level bugs we've been seeing lately (super-inflated threat from priests, threat jumping around like a monkey on crack, people disappearing, etc). The whole raid will want to upgrade - I've marked that check-in as the oldest backwards compatible revision, so anyone not using that revision will show up with "Incompatible" next to their name.

Please keep an eye out for inconsistencies and bugs, as I can only test so much outside of a genuine raiding environment. It seems to be working really smoothly for me, but time will tell.

Last night in Karazhan Omen displayed something strange:



Isse is a feral druid in catform. As you can see, her threat is reported lower than Thargans and Talazars, but she's listed higher than both of them. We all use Threat/Omen.

Another thing I saw several times was a shadow priest sometimes having ridiculous threat values (up to 360%) and then jumping back to a more realistic value after a second or so. Could that be just glitch in the sync timing or something like that?

Edit: can probably disregard this post as I just saw your latest post (I shouldn't spent so much time in the edit box I guess, heh).

I too would like to also add my report of odd behavior on the Nightbane fight. Our guild killed him on Tuesday, but not before a wipe because of two dps pulling agro and getting nuked (both of them and the tank were using Omen) when they were only about 90% of the tank's agro.

I hope that the fixes Antiarc implemented last night address the issue, but I'd love to see a guild that still has Nightbane up this reset test with a new revision and report to see how it works. I lost a lot of ground getting the guild to buy into omen that night when we had to have people running only omen log out and reload KTM; having a solid report of omen working well on that fight would go a long way to restoring that confidence.

If I don't see such a report by next week I'll try to replicate the scenario.

Geheim: Which phase did they pull aggro in, and what class was tanking for you? It's possible that I'm doing the threat clear at the wrong time and showing the tank with more threat than I should. I'm hoping that last night's fixes will address it, but I'd like to stay open to as many possibilities as possible.

Nightbane was at about 80% health so no flight phase threat reset should have been a factor. Warior tank, two dps classes that pulled agro were a rogue and a warlock.

Warior was running both KTM and Omen, rogue and lock both had only Omen loaded. I'm sorry that I didn't get Omen revisions, but I had put it out of my mind until I saw others posting about similar problems in the same fight.

I've checked the code for KTM, and KLH does two threat wipes for Nightbane, one when he says "Enough! I shall land and crush you myself!" and one when he says "Insects! Let me show you my strength up close!". Other then that there are no threat reducers or wipes. A quick glance at your code and I see both implemented.

It just seems odd that it would be a problem for us before any wipes, and that multiple raids have reported problems with the same fight.

The obvious answer is that Threat is over-reporting warrior threat. The less obvious answer is that the bug I fixed last night (which could potentially result in the global threat being added in twice) could be responsible; if the warrior had generated a decent amount of global threat - say, through Prayer of Mending - then that reporting discrepancy could account for the difference. I've yet to see any variance in reported rogue threat levels, so I'm not really worried that rogues are being misrepresented.

Edit: Thanks, Fireye. Please let me know. If you want to chat about it in realtime, feel free to hop over Alliance side and ping me - char info's under the name. Any observations, screenshots, or bug reports are more than welcome.

Having a fairly major issue with Omen/Threat-1.0 on Hydross.

Engage, tank shows as building to ~ 9k threat very quickly, and then ... stalls, for lack of a better word. No threat gen being shown, healers rapidly outthreat him, all dps is ahead of him ... yet he's clearly tanking, and we're not pulling aggro.

Everyone in the raid has the latest push (42232 & 41334).

Any ideas?

Bah. I still haven't been able to replicate that one.

I'm keeping an eye out for causes, but I still haven't identified a reason for it. That's...one of the last remaining showstoppers, and I'm hoping to track it down soon.

Is there any chance of Spell Reflection threat being added? It'd be a bit difficult to get the required information (since the mob is essentially damaging itself), so I can understand if the answer is no, but I thought it couldn't hurt to ask.

Well, reflected spells -should- register as threat from you, I suspect. Is there additional threat on top of the damage caused?

I had the "tank stall" phenomenon yesterday too. Latest build.
Omen was completely useless, as on every prince try, the tank stalled for me on about 9k threat. On several other pulls too - perhaps it could be related to misdirection...

Edit: strange that it seems always be at about 9k threat.