I tried very hard to push a switch to Omen on my guild, given the memory issues plaguing KTM and what I feel is a pretty impressive feature list. We made the switch and got using it, but my guildmembers eventually became frustrated by the fact that they needed to update it so often in order to maintain universal compatibility among our raiding group.

Personally, I update my mods with WAU several times a day, but I'm guess many of our players are not as interested or as techsavvy when it comes to mods (or computers in general). The people who only updated their mods maybe once a week or less never got what seems to be almost daily changes, many of them major, and due to the incompatibilities between versions these raiders wouldn't show up on our threatlists at all.

So the mod is wonderful and does everything I could ever ask of it, but I really underestimated the power of human laziness. KTM has one thing going for it as far as the average raider is concerned: version updates are far-between and therefore don't require the kind of daily updates Omen does in order to maintain compatibility between users.

My hope is that the more Omen nears "completion," the less of a problem this will become. In the meantime my guild has switched back to KTM. I'm still using Omen, since for me the updates are not frustrating and the two mods can communicate in a limited fashion.

Thanks for all your hard work on this.

Yes this gets minorly offtopic, but why dont they simply use WAU? Its a 3 click installation, at most you need to change the install directory of WoW and to update its something like pressing f5 then f10.
Someone who uses more than ONE wowace hosted addon who is not using WAU is wasting 5-10 minutes each time considering to update his/her addons.

Omen is in active development still. That is to say, major changes can happen at any time. If your guild can't update daily then it's probably best for those users to stick with KTM (omen WILL display their data long as they're running one of them).

I know that it's already known, but I figured I'd add a datapoint: It's still acting very wonky for a Shadow Priest in my guild. The main issue that had annoyed him was that it didn't reset for him after having left combat, but there also seems to be inconsistent accurate threshold and overall threat tracking.

This was in Gruul's Lair on pre-HKM trash, for point of reference.

Whoops, double post using Quick reply. Delete plx.

This was exactly what I suggested myself, but I can't make people do it, and a lot of them were either really uninterested in the process and/or didn't want to learn how.

Like I said, my problem has little to do with Omen's strengths as an addon - it's fantastic, and I love using it - it has more to do with getting a guild full of people of varying computer skills, temperaments, and intelligence to all do the same thing at the same time. That's a pretty huge challenge with the kind of frequent updating Omen is undergoing, so my guess is I will have to wait until the addon leaves the beta stage.

Ran Omen last night on Voidreaver and karazan, had a couple issues that may or may not be related to omen:

1. I was tanking the fight and would report that I was number 2 on threat list on KTM and number 1 on Omen. I would never be bounced back and lose my spot and would scale far past the other 2 tanks but VR would never come to me even though Omen was reporting I had 20% more threat into the mobs than other 2 tanks.

2. Was tanking in karazan and the latest build was not reporting to KTM in there for some reason. I made sure to check and double check that yes Omen was sending reports to KTM clients and I was recieving them but it did not come through. I had to run KTM at the end so rogues would know when to vanish.

3. The INCOMPATIBLE version. what does that entail? I saw that several peoples clients were showing that. What exactly does that entail?

Regarding translation, it's done on the fly for mob names, as the vast majority of trash translations don't exist in Babble. Basically, deDE targets a mob, enGB says "I don't have a deDE translation for deDE's target", asks deDE about it, deDE replies with their mob name and both store the translation. I overhauled this system yesterday due to a number of problems resulting from race conditions; I'm -hoping- you should find it a lot more stable as of r42552.

masanbol, I'd recommend that your folks hold off on updating till a 1.0 Final release is made if the current development schedule is too aggressive for them - my own guild has made the same determination, and really, I think it's better for everyone. There's no sense in having people running out of date versions that likely contain critical bugs and which invalidate most of the test results

Void Reaver's module seems to not be working; I observed that myself on Sunday. I was working on translation stuff last night, but I'm planning to get the VR module fixed up tonight.

I haven't heard reports of Threat failing to report to KTM, but I'll also test that tonight; any additional info you can provide would be useful.

The "Incompatible" flag is set when I check in a change that contains significant bugfixes that affect the interoperability of Threat clients. Basically, if you're running r300 and I set the incompatible flag on r325 because I made a change in 325 that means that 300 may or may not properly talk to 325, then 300 is flagged as "incompatible" as a warning that that user should upgrade, as their client may contain bugs that will hinder your ability to work with your client.

Any idea when the 1.0 RC will be released yet?

Awesome mod, though

When the major showstoppers are fixed. That is:

- Hunter pet support is complete
- Warlock pet support is complete
- Automatic translation problems are fixed
- Outstanding boss module problems are fixed

I was doing Al'ar yesterday, and on P2 (when he comes back from the dead), it seems threat is wiped (except for some Warlock DoTs that last thru his death).

Does Threat take this into account (or am I just wrong)?

He most certainly doesn't wipe threat. Our last A'lar fight he came and smashed my face and I didn't have a DoT up at all. I did have about 200% more threat than any tank though...

We managed to switch my guild to Omen so except more reports to come
The main reason was that we are on Gurtogg Bloodboil and Threat treats the Insignificance debuff. We noticed that after a rogue had Fel Rage and made insane damage he had insane threat as well. He was at 100% threat and the main tanks were at like 29-30% of his threat. After the Fel rage phase the boss turned to the main tanks so I suppose Fel Rage has similar effect than Insignificance has.

Is there any way you could make Threat/Omen completely ignore really old versions? A bunch of people in my guild still run the versions that make your whole raid lag if someone has them and I can't seem to convince people that it's worth updating. I'm pretty sure some of them don't even realize they have the mod or something.

I'm considering adding in a switch to allow people to manually filter data from old versions, but I'm hoping to not need to add that after a 1.0 Final release.

Got some Errors while doing TK tonight.
Omen 42522 / Threat 42522
I'm using enGB Client, the errors seem to depend on some issues with German localisation.

TK Trash:



Kael:

There seems to be some kind of issue with Threat and multi-mob fights. I'm in Heroic UB and keep getting someone ahead of the tank/aggro bar when they don't have aggro at all and there's only 1 mob with that name in the fight. I'll try to get a screenshot next time it happens.

EDIT: According to Party Revisions, they all have incompatible versions which is probably what's causing this.

Yesterday at Teron it happend again, we stay to the border right next to him but out of LoS so i can engage quick (note i was MT).

I target Teron.

I press Bloodrage (start seeing me on Omen), give myself Commanding Shout and wait a few more seconds (Bloodrage does NOT run out) to get Shield Block up and engage.

-------------------------------------

I run out of LoS and engage, right before this it can happen that some other warrior also Bloodrages, or i receive a small heal from someone due to losing some HPs with Bloodrage.

I see those ppl on Omen as well and i am usually still first there.

--------------------------------------

I receive the first hit from Teron and are knocked to -130TPS and never make it back up.

This is compeltly wired, because there seems to be a pattern with Bloodrage and myself getting put in Combat with others making it into the Threatlist while in this Bloodrage-combat but not in combat from the actual mob.
Anyway its kinda hard to reproduce this but usually it has something todo with usuing Bloodrage (to get Commanding Shout + Block up) before engaging.
Someone has seen similar things?

note: Version used, 1 day ago.

Could I throw in a small request for Jaws music to be added as one of the options for the audible threat warning?

Thanks

Copying this from my post on the wow forums.

I would really like to see a feature freeze and work on getting a stable release out the door that I can give to our raid. The reality is most people just install something when they're told to and don't update reguarly and if there was a bug in a dev release that would affect everyone else and one person didn't upgrade then it would cause problems so having a release that is stable and relatively bug free would be great. (not saying it isn't at the moment, but "officially" :P)

I do update mods daily though so it's not an issue for me.

As was said above there are some major issues that are still being worked on.

Really all you need to do is get your people to get wowaceupdater and take 5 minutes to update it before the raid. Even while you are all zoned in ready to go take the break. There is also the nice feature that tells you if anyone has a newer version.

If you are using any ace add ons you should probably update them daily anyways, this will just give you incentive. It really is pretty simple.

Features are mostly frozen at this point; my focus very much is the remaining bugs.