Omen - Ace Threat Meter - Page 92

Rifeus · 04/11/08, 11:16 AM

Correct. However I do not know if FD is put into the combat log if it resists.

Marroc · 04/11/08, 8:20 PM

Minor display issue:

Grow up does not seem to function correctly under all circumstances. I can't put my finger on what is causing it, as it usually does not happen, but every so often the frame will grow down into my chat window (by the space of about a bar or two). Toggling Grow Up (after I'm out of combat and there's no bars on the list) seems to fix it.

Again it's minor and seems to be random, but it's annoying when it happens.

[e] As you can see from the screenshot below, omen has grown into my chat frame (it was originally just above it).

alienangel · 04/11/08, 11:26 PM

Originally Posted by Gearknight

From what I can tell, absolutely nothing is getting put into the combat log when we feign death. Is this true or am I missing something?

WWS has no record of anyone feigning death in any of my guild's raids since 2.4, and Ctrl-Fing a few combat logs for "Feign" also results in nothing.

I'm fairly sure no combat log of mine has every had any text for a Feign, 2.4 or otherwise.

As for Feigning, seeing no resist message, seeing omen clear your threat, and then pulling aggro 5 seconds later, that's been happening pre-2.4 as well. See posts ~1 month back in the various hunter threads in the Class Mechanics forums. Since no resist messages are displayed, I doubt Omen is to blame, since as far as the UI report the FD worked. However the target apparently still retains the hunter's threat.

Roana · 04/11/08, 11:41 PM

Has anybody gotten AoE mode working on Omen? Everything else functions like clockwork for me, but AoE mode does not show any bars.

I'm wondering if it's an interaction with another mod (oh god, I hope not), or perhaps a known issue with Omen, but couldn't find anything elsewhere.

tessarji · 04/12/08, 12:08 AM

Aran has a normal threat table. As a rogue with highest threat in group, I would invariably take his melee hits, until I vanished upon which when he would immediately choose instead to melee our fury warrior or charge our very high threat warlock.

This is not one fight, this was his behavior virtually every time we've pulled him. I've actually seen him go chasing a warrior around who was in turn chasing elementals, for the entire time the elementals were up. He never even contemplated changing his melee aggro for that whole period. We pretty much lock him out from all schools with our normal group.

It's real simple, he chooses random targets for his spells, and if he decides to melee it is always the person on the top of his threat list.

Gearknight · 04/12/08, 12:18 AM

Whether or not it's possible post-2.4, I don't know, but Omen is not currently distinguishing which mobs resisted a FD. Whenever any mobs at all resist it, Omen keeps your threat on all mobs. If it's possible, it would be a nice feature to finish, as it's practically impossible to have feign not get resisted by something during, for example, Hyjal trash.

If feign were displayed in the combat log, we could look and see if it generates individual messaging for each mob that resists, but because it isn't, no dice.

Xaoc · 04/12/08, 2:00 AM

FD isnt going to be in the combat log because of PvP. There is no way for Omen to know if FD gets resisted because there is no reference -anywhere- to FD.

Cluey · 04/12/08, 7:07 AM

I got the following error while running in to catch up to the raid after a swap.
I wasn't near the combat yet and had nothing selected, the raid had started on the post Mother trash.

Date: 2008-04-10 19:48:46
ID: 4
Error occured in: Global
Count: 1
Message: ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua line 633:
   attempt to perform arithmetic on upvalue 'aggroThreat' (a nil value)
Debug:
   (tail call): ?
   [C]: ?
   ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:633: ArrangeBars()
   ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:492: UpdateLayout()
   Omen\Frame.lua:22:
      Omen\Frame.lua:20
AddOns:
  Aloft, vr45867
  AlternateBlips
  Atlas, v1.11.0
  AtlasBattlegrounds, v1.11.0
  AtlasDungeonLocs, v1.11.0
  AtlasEntrances, v1.11.0
  AtlasFlightPaths, v1.11.0
  AtlasOutdoorRaids, v1.11.0
  AtlasLoot, vAtlasLoot Enhanced v4.04.00
  ChatSettingsFix, v2.4.1.3
  Chatmanager, v2.3.1
  CooldownTimers2, v2.5
  CooldownCount, v2.1
  DotDotDot, v1.01 r667441
  DruidBar
  EnhTooltip, v5.0.PRE.2963
  EquipCompare, v2.11
  Examiner, v08.03.26
  IceHUD, v1.2 (67817)
  Informant, v5.0.PRE.2963
  ItemRack
  Threat20
  Omen, vOmen r68561 / Threat-2.0 r68842
  pDebuffList, v1.0
  Prat, v2.0 67886
  Recap, v4.05
  StanceSets3
  Stubby, v52
  Swatter, v5.0.PRE.2963
  TinyTip
  TinyTipExtras
  TrinketMenu
  XPerlArcaneBar
  XPerlParty
  XPerlPartyPet
  XPerlRaidHelper
  XPerlRaidPets
  XPerlRaidFrames
  XPerl, v2.4.1
  DBMBlackTemple
  DBMAPI

Caryna · 04/14/08, 6:55 AM

We had an issue with Omen at Nightbane last friday. People who showed up at 20k threat below the MT managed to pull aggro. The only thing we noticed was that people kept their threat values after the flight phase. Isn't that supposed to reset?

Marroc · 04/14/08, 10:19 PM

Originally Posted by Marroc

Minor display issue:

Grow up does not seem to function correctly under all circumstances. I can't put my finger on what is causing it, as it usually does not happen, but every so often the frame will grow down into my chat window (by the space of about a bar or two). Toggling Grow Up (after I'm out of combat and there's no bars on the list) seems to fix it.

Again it's minor and seems to be random, but it's annoying when it happens.

[e] As you can see from the screenshot below, omen has grown into my chat frame (it was originally just above it).

Tracked down the issue. It appears that the Grow Up value is not initially set when omen is loaded. By this I mean the value is stored, and it's checked in the options, but it doesn't seem to actually be in effect until after it's been clicked off and then back on again.

Gearknight · 04/14/08, 11:34 PM

Originally Posted by Marroc

Tracked down the issue. It appears that the Grow Up value is not initially set when omen is loaded. By this I mean the value is stored, and it's checked in the options, but it doesn't seem to actually be in effect until after it's been clicked off and then back on again.

I'm experiencing the same bug in a slightly different way, which I posted about, a page or so ago. Omen always grows up upon logging in or /reloadui, until I either move the window, check and uncheck the option, or run /omen display barlist growup off. Not that much of an inconvencience, because I have to run /script ChatFrame_RemoveMessageGroup(DEFAULT_CHAT_FRAME, "GUILD") every time I log in due to blizzard's broken options too.

StatiK · 04/16/08, 1:51 AM

Originally Posted by Caryna

We had an issue with Omen at Nightbane last friday. People who showed up at 20k threat below the MT managed to pull aggro. The only thing we noticed was that people kept their threat values after the flight phase. Isn't that supposed to reset?

Had this same issue with Nightbane and Mag.

• sp00n · 04/16/08, 7:01 AM

Originally Posted by Gearknight

Not that much of an inconvencience, because I have to run /script ChatFrame_RemoveMessageGroup(DEFAULT_CHAT_FRAME, "GUILD") every time I log in due to blizzard's broken options too.

[OT]
I think I've noticed that if I do a /reloadui, the options to the main chat window are applied.
Or you can manually select the options you have deselected, close and open up the options again, and then deselect them again.
[/OT]

Back to topic, I still sometimes have issues where threat of a pet isn't cleared on a new attempt.
Also, when I had such a situation, I clicked on "show test bars", and after that clicked on the previous target and received an error message from Omen. Didn't write it down though, going to think of it next time.

Also, do you have any time schedule when pulling out threat bars will be available again? Really miss that feature, especially on Bloodboil.

Gearknight · 04/17/08, 7:29 PM

Originally Posted by Gearknight

Whether or not it's possible post-2.4, I don't know, but Omen is not currently distinguishing which mobs resisted a FD. Whenever any mobs at all resist it, Omen keeps your threat on all mobs. If it's possible, it would be a nice feature to finish, as it's practically impossible to have feign not get resisted by something during, for example, Hyjal trash.

If feign were displayed in the combat log, we could look and see if it generates individual messaging for each mob that resists, but because it isn't, no dice.

Originally Posted by sp00n

[OT]
I think I've noticed that if I do a /reloadui, the options to the main chat window are applied.
Or you can manually select the options you have deselected, close and open up the options again, and then deselect them again.
[/OT]

Those all sound like much more complicated ways to fix 1 problem than pressing 1 macro to fix 2 problems.

Anyway, I just downloaded an update via WAU which supposedly fixed the grow/up down memory behavior... but didn't.

Spink · 04/17/08, 11:29 PM

I'm getting a weird issue that may be Omen or WAU related. I have Omen r70244, but other people in my raid have Omen r70265 - I've refreshed WAU, checked the changelog ( http://fish.wowace.com/changelog/WowAce/trunk/Omen ) and I can't find any reference to 70265 anywhere but atleast 4 people in this raid have it D:

Gearknight · 04/18/08, 12:44 AM

Originally Posted by Spink

I'm getting a weird issue that may be Omen or WAU related. I have Omen r70244, but other people in my raid have Omen r70265 - I've refreshed WAU, checked the changelog ( http://fish.wowace.com/changelog/WowAce/trunk/Omen ) and I can't find any reference to 70265 anywhere but atleast 4 people in this raid have it D:

Omen is currently version 70244, and Threat-2.0 is currently version 70265. Omen displays the version number of Threat, not of Omen, in-game, as that's what really matters for compatibility between you and your raidmates. Whether or not you use externals, the WAU will update both of them when you either update Omen or "update all addons." It's an unfortunate coincidence that their revision numbers have been hovering close together, causing this sort of confusion.

Roywyn · 04/18/08, 8:18 AM

Currently, when taunting, Omen seems to change the threat of the taunter to the threat of the person with the highest threat.
It should however change it to the threat of the current aggro target.

( Brutallus ran over to gank a warlock last night just a few seconds after a warrior taunted him off a druid. That happened 2 minutes into the fight. )

Roywyn · 04/19/08, 9:57 PM

Just did a quick test in Blasted Lands.
Taunt functionality is definately broken.

A warrior builds 23k threat. The ranged aggro ceiling is 30k.
I build 29k threat from ranged, no aggro yet.
The warrior taunts the mob that is still on him.
Omen wongly changes the warrior's threat to 29k. The warrior's real threat is still only 23k.

I do a little more damage and get aggro from range at 31k like expected.
Omen shows the warrior threat as 29k and the threat ceiling as 37k.
The real threat is 23k, and the ceiling is 30k.

Screenie

The issue is basically that when taunting, Omen should take over the threat of the current target, and not the highest threat in the threat table.

Antiarc · 04/19/08, 11:05 PM

Thanks for the testing, Roywen. I'll get a fix in tonight.

Polleke · 04/20/08, 8:28 AM

What would happen if you taunt during a RTST? I've not seen Brutallus yet, but I believe it targets secondary targets for burn. Now what would happen if the MT taunts when a mage at 120% threat gets targeted for burn?

Pagarth · 04/20/08, 5:03 PM

I have a few Omen questions that mostly pertain to looks. I'm not really hardcore raiding and just do 5 mans and maybe the odd Kara but I don't like to pull aggro! Anyways, I have been working on my UI this past weekend and everything is looking great except Omen has two issues that really bug me.

1) Is there a way to hide that new version listing? I don't need to see it. It covers the percentages in my Omen window, here is a screenshot:

. I plan to keep Omen updated and this is just unnecessary . Do I have to go into the .lua files to fix this or is this an option that I'm just not seeing?

2) The padding between the bars and the modules bar and the threat bars is too high. Here is an example screenshot:

. I can easily fit two extra bars there. I do want to keep the modules there but I don't want to have to deal with the really high padding. I've looked in the options and didn't see anything for this either.

I appreciate any help. Thank you.

♦ Praetorian · 04/20/08, 5:56 PM

I notice the most recent WAU build has the following change note:

added Illidan P5 (Shadow Prison) Reset

Illidan definitely does not reset threat on the Maiev arrival/speech. This is why bringing him to 30% as a demon is ugly -- because his transformation out of demon form DOES reset threat, meaning that he will come out of the Shadow Prison speech with a fresh aggro list and likely run for someone with DoTs or HoTs ticking rather than the tank. If you bring him to 30% as a humanoid to begin with, his threat list definitely does not change.

Arnath · 04/20/08, 6:21 PM

EDIT: Never mind, this wasn't really a useful comment

Pagarth · 04/20/08, 6:27 PM

Another issue with Omen, I want it to show when I'm in a party or raid. I have that checked in the "Show when" options but it doesn't show when I invite someone to a party. It also doesn't show when I join a raid. I tried checking Show when in a dungeon and that doesn't work either. Anyone know what's up with that?

Daboran · 04/20/08, 7:23 PM

Originally Posted by Praetorian

I notice the most recent WAU build has the following change note:

Illidan definitely does not reset threat on the Maiev arrival/speech. This is why bringing him to 30% as a demon is ugly -- because his transformation out of demon form DOES reset threat, meaning that he will come out of the Shadow Prison speech with a fresh aggro list and likely run for someone with DoTs or HoTs ticking rather than the tank. If you bring him to 30% as a humanoid to begin with, his threat list definitely does not change.

This.
We always pop Bloodlusts just after the speech in normal form and no-one ever pulls aggro, which they would do if he reset aggro at this point.
As mentioned. 30% at Demon can get ugly really fast because Demon to Normal transition always resets aggro and we hold all dps if there's any danger of hitting 30% in Demon. The best timing for a kill is always to get him to 30% just before he goes Demon, so you get a non-changed threat list and another full normal phase to dps on him.