Authors CurseForge

Reposting from the Omen2 thread, seems to fit better here:

Feature Request:

Is it possible to have a Print Out in Chat Window 1 after every fight? (Or Bossfight?)

Like this:

You spend XX Sek. in Combat and generated YYY threat for a average of ZZZ TPS.

Would like to have this, just for improvements in my tanking.

Thanks!

I'm having an issue on version Omen-r70687. The threat meter itself is resetting (stats) but the flashing red aggro indicator will not go away.

For instance, I was in Heroic Shattered Halls (as a Mage) and I pulled aggro on the last boss just before he went down (Bad Mage!). When I pulled aggro, Omen made my window flash red which is normal. After we killed the boss we all ported to shatt. I flew all the way to Netherstorm and my screen was still flashing red (never stopped). I had to log to get the flashing to stop.

Last night on Hydross we were having a problem with Omen's aggro dump. Using version 70687, whenever he would change phases our aggro wouldn't dump, and my aggro stayed at 7k threat. Don't know why I didn't take a screenshot, but me being a destro lock, that topped the meters for that fight, I'm sure I had a hell of a lot more than 7k threat. It only did this on Hydross though, later on, on Leo, it reset aggro on phase changes fine.

currently whenever i click on one of the resize triangles on the bottom of omen it compeletely locks up WoW to the point of having to CTRL ALT DEL and restart

I also noticed something weird with the threat wipes on Hydross on Wednesday night. One of our rogues would immediately get over 5k threat after the transition, way above the new phase tank, but not pull aggro. I think they might have been Shadowstep specced (yes, I know, but they were a fill-in). I believe their Omen was fairly up-to-date, certainly not incompatible.

Nope, all enUS users in the raid as far as I know, including the rogue I mentioned.

I loaded Version 71088 yesterday afternoon. Made no other updates to wow, addons, or my system. Immediately after loading the addon, and relogging into wow, I continuously get disconnected from server. Today I discovered I can not complete any newly acquired quests (when I get an item for the quest, it dfoes not give me credit in the quest for acquiring that item such as multiphase readins, etc.) and I have difficulty getting into battlegrounds. I keep getting an errro saying instance is unavailable for warsong gulch 1.

I removed the omen folder from my addons folder. I no longer get disconnected, I can complete the quests, and I can get into battlegrounds with ease.

I am *extremely* frustrated by the fact that Omen2 is not letting me select my desired bar texture because I have enough bar textures registered in SharedMedia that the list is higher than my screen, and there's no way to scroll the list or show it in multiple columns >:(

Also, the profile system seems to be nonfunctional, as it's not adjusting to look like it does on any of my other toons when I switch profiles.

This may be a bit premature before I can get exact revision #s, but we've been seeing some strangeness with threat on the Flames at Illidan. We've been playing it fairly conservatively, but are seeing players pulling aggro when well below the tanks; 10k below seems to be about the spot where it happens, but it's hard to give an exact number. There has also been times when the displayed threat was tank, lock #1, lock #2 and the 2nd warlock would pull aggro instead of the first (among other variations, such as a druid at #3 pulling over lock at #2, etc). Melee have also pulled aggro "out of order" as it were.

As a rule we all keep our Omens updated, although not necessarily the same versions, and are all enUS. We havn't noticed any similar threat issues on any other boss, seems to be confined to the flames.

Quote from Xinhuan »

Have you considered not registering/loading so many bar textures? You probably only use 2 or 3 out of the 50 plus. All wasting memory.

How do I throw away the textures I'm not using?

Quote from Xinhuan »

Have you considered not registering/loading so many bar textures? You probably only use 2 or 3 out of the 50 plus. All wasting memory.

Addons are doing it automatically, and I have no desire to hack addons every time WAU updates them to remove the extra textures. I really resent that you are blaming me for having so many textures that it's making Omen behave poorly when other addons handle it fine.

Errors occurred tonight. Omen r71628, embedded Threat r71636, embedded LibGUIDRegistry-0.1 r68639, other libs standalone. On a 70 priest in a Kara raid, changed into "Healing" mode from "Overview" out of combat.

10 errors occurred over about 30 seconds. All of them are long, many repeat and a couple are likely the same as others. Don't have time to go over the list, so include the full thing in the text file below.

I don't have LibDropdown-1.0 installed (in Branches, referenced in the TOC), if it makes any difference.

EDIT: One other major problem. Accessing the Omen options via Blizzards Interface (ESC, Interface, Addons), they don't fit in the window properly. The text and other things are all cut off on the right side of the window; many drop down lists can't be accessed and so on. This is the identical issue as what I reported on Curse with an earlier Ace3 revision of the Simple Range Indicator mod. It was fixed in v2.4.1 of that mod (it was changed to override the Ace3 default behavior).

There is no issue accessing Omen's options via the FuBar icon/text (or the minimap icon, if no FuBar); its options window appears properly scaled when opening it from there. Only when accessing it through Interface do the options size improperly.

Quote from licwid »

currently whenever i click on one of the resize triangles on the bottom of omen it compeletely locks up WoW to the point of having to CTRL ALT DEL and restart

still having the issue, but it gave me an error once before crashing!

Date: 2008-04-27 22:36:15
ID: 58
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\Bar.lua line 341:
  C stack overflow
Debug:
  [C]: (for generator)()
  Omen\Bar.lua:341: ResizeBars()
  Omen\Frame.lua:12:
   Omen\Frame.lua:11
  [C]: Show()
  Omen\ModuleBase.lua:245: MaybeAutoHide()
  Omen\ModuleBase.lua:207: AddBar()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:630: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11
  [C]: Hide()
  Omen\ModuleBase.lua:253: MaybeAutoHide()
  Omen\ModuleBase.lua:140: ResetBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:551: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11
  [C]: Hide()
  Omen\ModuleBase.lua:253: MaybeAutoHide()
  Omen\ModuleBase.lua:140: ResetBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:551: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  ...
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11
  [C]: Hide()
  Omen\ModuleBase.lua:253: MaybeAutoHide()
  Omen\ModuleBase.lua:140: ResetBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:551: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11
  [C]: Hide()
  Omen\ModuleBase.lua:253: MaybeAutoHide()
  Omen\ModuleBase.lua:140: ResetBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:551: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11
  [C]: Hide()
  Omen\ModuleBase.lua:253: MaybeAutoHide()
  Omen\ModuleBase.lua:140: ResetBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:551: ArrangeBars()
  ...ce\AddOns\Omen\Modules\SingleTarget\SingleTarget.lua:497: UpdateLayout()
  Omen\Frame.lua:13:
   Omen\Frame.lua:11