Issues with Omen?
I gave a preview of Omen 2 awhile back before patch 2.4 hit, and we saw just how popular the addon is the other night. It has become almost necessary in the WoW community, and when it isn't working right, it really has an effect.Everyone that has downloaded Omen 2 has noticed that there are some... issues. The author is aware of most of these, so fixes are on the way, but there's only so many hours in a day. Bugs and issues can crop up in strange places though, so it never hurts to report them. There are some minor things you can do yourself to make sure things work smoothly and be confident the problem isn't on your end, so take a look behind the jump for some tips.
First off, if you're having any issues at all and didn't do this before upgrading to Omen 2, my recommendation is to log off of WoW, go into your Addons folder, and delete the Omen folder entirely. This will be sure that no old files remain in the Omen folder from Omen 1.0. Some things, like the threat library Threat-1.0 are obsolete in patch 2.4. This may not have been removed in your original update, and has been reported to cause issues with Omen 2.0. Just wipe out the folder for now.
To simplify: Threat-1.0 is bad. Threat-2.0 is good. If you have Threat-1.0, kill it with fire.
Next, download Omen if you had to clean out the Omen folder. If you didn't need to clear out that folder, check your version by looking at the upper right hand corner of the Omen box. You automatically get notifications if your version is outdated when someone in your guild or raid has a newer version, but if you're checking on this prior to a raid, you can just compare it to the latest posting on WoW Ace. Make sure you have the most recent version each time you encounter a bug, because there's a possibility that has already been fixed in an update. The author has been working day and night to solve everything he can.


If your Omen looks like that up above upon logging in, you can do one of two things. One, click on the little 'button' my arrow is pointing to, and drag it somewhere. Omen will snap back into shape. Two, you can log off and update Omen, because this was fixed in one of the very first revisions. You shouldn't have this issue anymore.
The most crippling bug that has been in Omen 2.0 so far is the immense CPU usage by the AOE and Healer Modes. This has been fixed, and you shouldn't need to worry about that issue anymore. It has been throttled properly now, so no more lockups or crashes. If you still see this issue, report it!
The most crippling bug that has been in Omen 2.0 so far is the immense CPU usage by the AOE and Healer Modes. This has been fixed, and you shouldn't need to worry about that issue anymore. It has been throttled properly now, so no more lockups or crashes. If you still see this issue, report it!
Many of the intended features for the UI have not yet made it into Omen 2.0, but rest assured that many of them are still on the way. It can't hurt to submit suggestions to the author, but many of the old features that we've grown to love simply haven't been implemented yet, though the intent is there. Patience is a virtue.
It may be frustrating to bump into so many bugs, but remain vigilant. If at all possible, do not become frustrated. Document what went wrong, write down any errors, and report them to the author. You can either do so over at WoWAce, or leave them right here for me at WoW Insider in a comment to this post, and they'll be passed along.
Keep in mind that all mods run into bugs, especially when they've just been built from the ground up. Omen and its predecessors had extensive testing on the Live servers before they were put out to the public. Omen 2.0(and Threat-2.0) was built from the ground up and wasn't able to have as much development time or play testing, as it was limited to the Fury of the Sunwell PTR and the content being explored on the PTR. The playtesting we, as a community, are currently doing with the mod will insure bugs are found and solved quickly and easily. Though it's a bit of a pain now, it's all going toward making Omen 2.0 better than it ever was.
Follow the few simple steps above, update Omen 2.0 often, document what goes wrong, and come on back to report it. You'll run into some hitches, but keep at it. Things will settle down, it may just need more than the two days it has had so far.
Oh, right! If you don't like the sound that comes with the threat warning, you can turn that off. Open the Omen configuration menu(click the wrench), go to Modules, then Single Target, then Warnings. Voila!
Patch 5.2 interview with Dave Kosak
Inside an old alt's vault
The latest patch 5.2 news
All of the latest Mists of Pandaria news





Reader Comments (Page 2 of 2)
Kaething Mar 28th 2008 3:18PM
I'd suggest updating Omen before you start playing for the day -- or especially before jumping into any raids.
Seriously, Antiarc is updating Omen INCESSANTLY. I was running a heroic Magister's Terrace w/ him yesterday where he was telling our MT to relog to update Omen to get some fixes that unfortunately couldn't be backwards compatible. I didn't update at the same time, and made a comment about updating it now that we were done with the run.
He told me to hold off for another 10 minutes because he was checking in another change to {developer goobledygook cache something blah}.
Seriously, update that thing like a fiend! And make sure you have the Ace3 Library, as Omen requires it, not Ace 2. (You'll probably need both, as a lot of mods still sue 2)
Rahrnok Mar 28th 2008 11:55PM
ACE 3 was the key for me. Thanks for that tip!
MartinC Mar 28th 2008 8:25PM
I see Omen 2.0 versionchecks (actually Threat-2.0 checks) were added in after my earlier comment. Thanks much!
zeq Mar 29th 2008 8:47AM
My question is what happened with "Disable when tanking". In earlier versions of Omen you could disable warnings when tankning (in Bear form, defensive stance or with Righteous Fury). I can't find that in new Omen, which is really annoying. I don't want to get warnings when I pass others threat when I'm the tank!
Does anyone know? Is this going to be fixed?
Except for that Omen is still extremely instable, was in a group yesterday, everyone had the latest version, but the threat bars only showed in 1 in 5 fights. I'm sure this will be fixed though, I'm more worried about not being able to avoid warnings when tanking...
bogota Mar 29th 2008 6:48PM
I am having terrible problems with Omen. I am the MT but I am not displayed on anyone's Omen and I only see myself.
Where do I get this Ace3 library? I can't seem to find the download site by googling.
Skywise Mar 31st 2008 4:38AM
I have updated version and, yes, I moved all the other icons to be sure it's not hidden.
I even deleted the old directory and all omen.lua and .bak files before installing again, but it didn't work.
Omen appears in my installed addon list and in key binding there's the toggle omen option, but it doesn't work.
Even the /omen and /omen toggle commands are not recongnized.
What can I do?
Takiena Apr 9th 2008 2:37PM
Is there a way to stop Omen from giving me a warning when I'm passing anyone in threat who ISN'T the highest? I get warnings sometimes, "Passed 90% of Talbot's threat!" Well, Talbot's a friggin' healer, not to mention 8th or 9th down the threat list at the moment. I'd hope I'm higher than he is in threat, but to be honest I don't care if I'm higher than he is in threat - all I want to know about is who currently has the highest threat on a mob and whether or not I'm going to pass that person. @_@