Omen - Ace Threat Meter - Page 61

Antiarc · 07/26/07, 7:17 PM

Yes, Eject is handled.

Vonwen · 07/27/07, 3:55 AM

Their threat most probably has not been reset after the 1st add, as it happened for me with people using KTM (this never happened with someone using omen), and seeing the stars in your screenshot it's probably this.

trost · 07/27/07, 1:18 PM

Quick question: does Omen pull it's warnings from the oRA and/or CTRA MT target lists or does it pull them based on class? I'm not sure how it works.

Either way, I would love to be able to tell Omen "Only show warnings if I exceed the threat of: <insert player name>". Or to tell Omen: "Only show a warning if I exceed the threat of my target's current target".

As it is now, it seems like I get threat warnings if I exceed the threat of anyone on the MT target list. Or maybe it's all the warriors. Like I said, not sure how it works.

Basically, I'd like to be able to customize the warnings a little more.

Thanks!

Antiarc · 07/27/07, 1:29 PM

Omen deteremines warnings by comparing your threat versus the threat of the person that currently has aggro, be that warrior, druid, or priest. If you're over a certain percentage, it yells at you.

Vectivus · 07/27/07, 2:09 PM

Originally Posted by trost

Or to tell Omen: "Only show a warning if I exceed the threat of my target's current target".

That is the inherent functionality of Omen. If you're concerned about exceeding the threat of specific classes or players (off-tanks, etc.)... look at the pretty colored bars?

Kyth · 07/27/07, 2:21 PM

I believe he's talking about things like Vashj, where when she's targetting people for forked lightning in P2, omen constantly helpfully informs you that you're over the X% of so-and-so's threat =).

• sp00n · 07/27/07, 3:01 PM

Just wanted to report a weird behavior on yesterday's raid (but not only limited to, it has happened on other occasions as well).
On Al'ar our shadow priest AND our 3rd tank were having problems where their threat were not cleared between tries, so that after several tries they ended on silly amounts of threat in the hundred thousands as soon as they engaged Al'ar, whereas the try just had begun.

Now, both of them were using a newer Threat version than I did, and since relogging on my side didn't fix the problem, it wasn't a simple display error on my side either.
I talked to the shadow priest and asked him to update *all* of his Ace addons via the WoWAceUpdater, and he replied that he had done so just yesterday.

So my question is, what can cause such erroneous behavior? Multiple instances of Threat installed with conflicting version numbers of Threat? Even if he had run the updater?
Was there a bug somewhere?

I've just found a screenshot of the problem. It's not from yesterday but from Tuesday, but the problem is basically the same (although not as present as when just having started a fresh try and seeing a 500k aggro bar.

Antiarc · 07/27/07, 3:12 PM

I suspect it is, again, related to this lib upgrade issue. Once I track that down, I expect most all of these problems to go away.

trost · 07/27/07, 6:33 PM

Originally Posted by Kyth

I believe he's talking about things like Vashj, where when she's targetting people for forked lightning in P2, omen constantly helpfully informs you that you're over the X% of so-and-so's threat =).

Exactly. I wasn't sure what the cause of the multiple warnings for multiple people was, but I think it's this.

Whenever a boss targets someone else for a random spell, does Omen give a warning if I'm above whoever was targeted for that random spell?

Xejin · 07/28/07, 3:37 AM

This is slightly off-topic, but I thought Antiarc might like to hear it. I managed to finally get one of the other officers in my guild to give Omen a shot today and now he's going on and on about how much cleaner and efficient it is compared to KTM, that we're making Omen policy for raids. Great work mate - it really is one of the nicest addons out here. Oh, and the code is nice and clean too, for somebody like me (professional coder) clean code is saintly.

Vonwen · 07/28/07, 6:47 AM

Just got this error after i updated :

[2007/07/28 11:30:20-1288-x1]: Threat-1.0\Threat-1.0\ThreatKLHTMSupport.lua:241: attempt to index upvalue 'TailoredBinaryCheckSum' (a nil value)
<in C code>: in function `pcall'
AceAddon-2.0-44196 (Ace2):24: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:23>
AceAddon-2.0-44196 (Ace2):999: in function `ManualEnable'
AceAddon-2.0-44196 (Ace2):927: in function <Interface\AddOns\Ace2\AceAddon-2.0\AceAddon-2.0.lua:920>
<in C code>: ?
AceEvent-2.0-44693 (Ace2):262: in function `TriggerEvent'
AceEvent-2.0-44693 (Ace2):955: in function <Interface\AddOns\Ace2\AceEvent-2.0\AceEvent-2.0.lua:948>

  ---

Qrt · 07/28/07, 9:35 AM

Originally Posted by trost

Exactly. I wasn't sure what the cause of the multiple warnings for multiple people was, but I think it's this.

Whenever a boss targets someone else for a random spell, does Omen give a warning if I'm above whoever was targeted for that random spell?

This happens to us in SSC as well I think - when we do the initial trash and the Hate-Screamers target a random player with their sonic attack - if I'm above that player on the aggro list I get a warning. That would at least explain some of the warnings I get there.

Antiarc · 07/28/07, 1:43 PM

Vonwen: Update again, that's been fixed, I believe.

Vonwen · 07/28/07, 3:38 PM

Thanks

Tehehe · 07/29/07, 9:38 AM

Originally Posted by Tehehe

Today during Al'ar (using Threat r44250) I Soulshattered at the beginning of Phase 2. It was resisted, but my threat was still halved on Omen. This shouldn't be!

Any word if this was fixed recently or not? I really hate having to try and notice resists in my combat log as it scrolls by rather fast.

Marroc · 07/29/07, 11:28 AM

Feature Idea:
Hide omen when not in an actual instance.

Not really a huge problem, but it can be annoying if you're in a raid group, but not actually in the instance (say on standby waiting to go in or something).

Just a thought :P

• Slake · 07/30/07, 12:37 PM

World bosses.

Marroc · 07/30/07, 12:44 PM

Originally Posted by Slake

World bosses.

Thus you make it so it can be turned off and on like everything else? Antiarc is good at what he does, and he knows better than to hard code anything that can be made into a user option :P

Apate · 07/30/07, 3:31 PM

How about "Disable Menus in combat"?

Marroc · 07/30/07, 3:36 PM

Originally Posted by Apate

How about "Disable Menus in combat"?

I don't see how it's really needed, but I don't see how it could hurt either.

Just out of curiosity, is there a specific reason as to why you want this?

I've been running it for months and never had any trouble with the menus while in combat.

edit:
@Antiarc:

Just remembered, could you please add an option to open the waterfall config from the right click menu? I know it's already there in the fubar plugin, but people (like me >_>) might not remember to shift click the fubar icon to get it up, and a simple "Open Waterfall Config" in the right click menu would fix it :P

Rinced · 07/30/07, 8:22 PM

After installing MainAssist I just figured out that there might be a way to differentiat between mobs with the same name by keeping track of people targeting the unit.
It won't completly solve the problem but it might help sometimes.

World bosses.

Exception for specific zones. But of course make it optional.

Antiarc · 07/30/07, 8:28 PM

I still can't correlate a log message against a target, even if I can get a unit path to the target.

Dovucoe · 07/31/07, 4:08 AM

Originally Posted by Tehehe

Any word if this was fixed recently or not? I really hate having to try and notice resists in my combat log as it scrolls by rather fast.

If I'm not wrong, Soulshatter has to occur while A'lar is still around for it to take effect. Shattering while A'lar is respawning at the start of Phase 2 does not take effect for some reason.

Tehehe · 07/31/07, 4:41 AM

Yes, that is correct - I waited until he had respawned. However when a mob resists Soulshatter Omen still reduces your threat by 50% on that target.

Base · 07/31/07, 6:04 AM

First off, my compliments on a great addon! I love it and I am trying to convince my guild to switch over, and I am slowly getting there.

Yesterday on gruul we were having some buggs with our elemental shaman. I was too busy tanking our first kill (yaay) so did not want to divert attention to take screenshots. I asked the Shaman to write down what he experienced:

Stomped totems (ooc)
Tank charges and we engage in combat
I throw a lightning bolt, when it lands I get the bug and am on the top of omen till I /reload.

It was normal when I threw a bolt then stomped totems.

We have a combo of KTM and Omen going round. I exclusively use Omen/Threat, the Shaman was also running Omen/Threat. I had downloaded the latest version yesterday around 20:00 Game time (European server) and the Shaman had a version the day before. I'll ask him if he can recall his version number.

Hope this info is of any use. We had this happen on 2 tries, after that the shaman placed totems after the first bolt.