Edit, if a moderator could remove this post please, it was a double

Yes - until Omen and Threat get full releases I found it's better not to use standalone libraries for it. I always download Omen with externals and delete the Threat 1.0 folder in the wow\interface\addons directory.

I'm up to date, some random person probably isn't. This could be quite the challenge to track down. Thanks for the tip though.

Shouldn't be, theres a function in Omen to show party revisions(which is all in raid etc). Latest is 41729

I fixed this last night actually; there was a condition that could show up if two boss mods were activated within a short time of one another, which would effectively make the two boss mods fight forever to become active - the implementation was really, *really* stupid on my part. This has been fixed, but it may persist until your whole raid has updated, unfortunately. I sincerely apologize for the problems caused.

I checked in code that basically does this last night. New mobs to a fight should be handled rather cleanly now. Testing is, as always, appreciated.

Out of curiosity, are any of your tanks using a non-enUS client?

I made a number of bugfixes to global threat handling in the past 24 hours that I -think- should resolve most of the shadowpriest problems.

Display problem, actually. Threat was being calculated properly, but was being relayed to GUIs incorrectly in most any fight with a threat adjustment. I think I've gotten all the relevant bugs worked out; please let me know if your folks continue to complain.

Which revision are you using? I made a fix to this last night...I think. If you're running the latest, I may not have gotten it fixed correctly.

antiarc, first off, great mod, if theres any help you need, let me know.


have you implemented stuff such as boss kicks resetting tank aggro? just curious

Isharm, what raid frames are you using in your screenshot?

I'm pretty sure that all language translations are well defined. In other words, the PlayerTextToDemonic() function will always produce the same outputs provided you give it the same input text. If that's the case, there should be nothing wrong with searching for "xix klaq neqtku" or whatever it reads.

The only possible problem would be getting localization translations. It's possible the demonic translated text would be different on a German client than an English, for example. Or they could be the same.

Too bad we can no longer do SendChatMessage with the other languages.

I think that the issue with addons and CoT might be worth mentioning to Sluoken? Maybe it has and I missed it, but it seems like a reasonable query.

Ok so I made it to page 8 reading and looking for my question but I just don't have time to finish the rest of the (looks... holy crap... 38 pages atm). I love the look and idea behind Omen however when explaining it to others in my guild and getting them to try it, I have come across the following issue:

When a large number of healers are healing, they target the person they are healing and then cast. (I personally use clique + grid). This breaks... well not breaks... but renders Omen ineffective for checking personal threat on a boss or for a raid leader to check threat things (over zealous dps, the current OT, or whatever). Is there currently a way (or could I make the suggestion to have a way) to "lock" Omen on a certain target. This functions very much like KTM's master target setting but allows for a lot of user freedom. Just a thought, other then that, <3 and looking forward to the evolution of this mod.

I'll be adding target locking, yes. I'm mostly focusing my efforts on tracking down and fixing the showstopper Threat bugs right now (new one for you all to watch out for - "odd" threat clears/reductions in the middle of a fight, probably related to the new mob code I put in yesterday). Once it's solid and performing up to expectations, I'll be polishing up the GUI.

Awesome. That is good to know and will help me sell it. Thanks again.

I believe if you target a friendly target, Omen shows the threat list for their target in turn. This is just from looking at the Lua, I could be wrong.

Interesting, how does this work for targeting a healer who has someone else targeted (and such chains). This still doesn't necessarily give the desired functionality though as the person you are healing could be targeting adds or such when you want to see the boss as an RL (or various other examples).

Nope, unless there's a new Canadian client!

That's great news, we're doing a TK clear tonight, so we'll get quite a few chances to check this out and get back to you.

Will do, in order to get rid of some problems which we've been having I've had everyone disable KTM. It seemed that anyone who had it running wouldn't get their threat cleared properly when switching between mobs. Originally I was thinking that it was KTM data getting into the threat lib system and 'corrupting' the data, but since you know about it already that's good to hear.

Thanks a lot for the quick responses you've had to everything in this thread, it's great to have access to the actual mod developer.

I discovered a second bug today that might have possibly have explained it; keep an eye out and see if it seems more accurate.

Excellent. Please keep an eye out for wrong threat levels in multi-mob pulls; I had one report of some problems today (likely related to my "new enemy joined the fight" code) that I've drycoded band-aids for, but I haven't tested them.

This was the case until...Sunday or so, I think. Make sure everyone's up to date and you should be able to use KTM and Omen side-by-side.

Heh, I'm getting the better end of the deal - it's great to have access to people that are willing to put up with your bugs and stupidities while developing this kind of thing. The feedback and testing and observations you all have provided to me have been absolutely invaluable. The whole community has been well beyond patient with me as I've slogged through this thing, and I am extremely grateful for that.

i would read it if it wasn't buried somewhere in the 30ish pages that this thread has turned into. and of course the first page with all the details i read this and didn't see anything the next 10 pages i was reading about

anyway, if its been implemented, can someone point me to the exact thread number?

Hey Antiarc, one more bug we noticed tonight. Did a quick Leo run waiting for late TK tanks, and when our Spriest was battle rezed, it never counted anymore threat he did.

This shouldn't have been an issue with him just not doing enough threat to matter after a full wipe as Leo is constantly resetting agro. Just something to look into, thanks!

gonna throw in something, on the moroes fight, our paladin tanks aggro fluctuated immensely until i loaded up threattoktm where it was syncing correctly, by itself, it didnt show his aggro correctly

Al'ar doesn't reset aggro on phase 2 start. It keeps the same aggro list.

Al'ar doesn't reset threat on the transition from stage 1 to 2.