Authors CurseForge

There is a huge bug with the values of Lifebloom threat generation. I tested it extensively to verify this. Lifebloom's regen portion generates half normal healing threat for the druid who cast it (so 0.25 threat per point instead of the normal 0.5 threat per point). On top of that, the ending heal involved with Lifebloom generates 0 threat across the board. Right now Threat 1.0 is treating all Lifebloom healing as normal healing threat levels.

Quote from Dolphin »

On top of that, the ending heal involved with Lifebloom generates 0 threat across the board. Right now Threat 1.0 is treating all Lifebloom healing as normal healing threat levels.

Doesn't Lifebloom's bloom give threat to the person it heals? Like Prayer of Mending or Earthshield?

Shaman get a new LO in which there's a 20% chance to cast a second lightning bolt that will cause 0 threat and 50% of a normal LB's damage.

Will Omen be able to know that it causes 0% threat? Otherwise this is going to make this addon near useless for me ><.

Quote from brotherhobbes »

Doesn't Lifebloom's bloom give threat to the person it heals? Like Prayer of Mending or Earthshield?

That was part of the point of my post. It gives no threat anywhere. I tested PoM at the same time, and it definitely gives normal healing threat to the receiver of the PoM heal. Lifebloom's ending heal just gives nothing. I did these tests on latest live build. I should test them again with 2.3, but I am pretty sure the result will be the same.

...PitBull\libs\Threat-1.0\ThreatMobNameTrandsation.lua:149:Conflicting translation for 潮行者深淵先知 in dnUS:old is "Tidewalker Depth-Seer",new is "Tidewalker Hydromancer".Please report to Antiarc.:

I too have the problem that my party member is not showing up in Omen. We both downloaded exactly the same version (from here http://files.wowace.com/sw-o.html) at the same time. We both get the message 'not using a Threat1.0 or compatible agent" when we chose Party Revision. When she is using KTM instead however, she shows up in my Omen just fine.

As stated before, please add more info to be saved in the profiles.
X,Y coords, scaling, etc. everything.

Also, it'd be nice if you could set bar colors "per class" rather than per individual person as it is now.. that's just too much of a hassle currently.
I like having all bars a darker color, except those of the tanks and myself.
Also, please make the default profile, the.. well. default. instead of the personal profile being default upon install.

I took a brief glance at the latest build and it seems as though the innate threat for Devastate is still listed as 101. From what I've read empirical testing has shown it to be 116/131/146/161/176 innate threat per application of sunder, plus an additional 301 while it's stacking the sunder armor debuff. Are the changes just not going into SVN until it's been tested on live?

It also appears that sunder armor shows up in the combat log as being applied when I use devastate. Does that mean that it's going to add in sunder threat each time I do that?

I just went ahead and set it to 176 on my client for now.

I've noticed that our Prot Warrior is generating far less threat according to Omen after the patch. It may be the Devastate threat numebrs as described by Roktar.

2.3 patch included per-mob tracking right? or was that still in teh pipeline?

anyway, if it does, does omen track threat on mobs with the same name separately now?

Thanks :)

No, that is not available in WoW yet.

I'm not sure if this is a threat or omen bug but I'll post it here.

The problem is this: I'm a ret pally and my threat shows up fine on my screen, but everyone else in the raid sees my threat way higher, like it's not taking into account the new 30% threat redux.

For example on Void Reaver tonight my Omen showed myself way bellow everyone else at like 100k threat while the top tank had like 250k. But everyone else in the raid said that I was 2nd on their displays....

Now, that sounds like a lot more than just 30% so I don't know which number is correct, but I do know that I was able to go all out on VR and not pull agro the whole fight. And VR was switching targets to the top tanks just fine, so if I really WAS 2nd on his agro table I would have been dead.

I also had Salv (I don't know if I had tranquil air, there WAS a shaman in my group and I didn't have windfury) and Subtlety on my cloak.

Hello,

it also appears that the change to the Enhance Shaman's "Spirit Weapons" talent is not reflected at the moment (from 15% to 30% threat reduction in 2.3).

Expd something with Omen last night, values were crazy :/ no other words to describe

Screenshots, or it didn't happen!

I've been noticing a bug when our warlock tanks leotheras. Threat is all over the place and early on when the warlock is picking him up, omen resets all threat values several times, so it's really impossible for anyone to tell what their threat is compared to the warlock tank.

Not really sure if Omen is the cause. But we started using Omen and i mean everyone in our raid last nite for the first time. Threat values etc seemed fine or close enough until the new devastate/sunder gets set exact and a few other new things. The only problem all of us experianced was a fps hit. For some it wasn't too bad. For me i dropped down to single digit framerate. I know other addons were causing this a few days back. For example Bongos2 was killing my framerate. Did update prior to raid. Just want to make sure it isn't a Omen thing or if it is then fix it please.

My question right now is how often should Omen be getting threat updates. It was set for 0.05 seconds by default. Some in our raid increased the time to 0.5 and this seemed to help a bit with our fps issues. Should everyone in the raid set it to 0.5 second and or is there an optimal setting that people have figured out for raid use?

BTW yes everyone in the riad was using the latest version of Omen and none were using KTM. We did check before we started and had people update and or disable ktm.

Quote from OttoDeFe »

There's been a bit of debate about the frame rate hits in 2.3 - read some of the debate on the forums at the Blizz site. It seems the code to spread the processing load across both cores of a dual core processor seems to hinder FPS, not help. A couple people said the set WoW to only use one core and their fps went up. The blues said to examine your addons for anything using pre-patch code, but several were of the opinion that wasn't the issue. I know I've taken a small FPS hit.

Bottom line, I don't think it's prolly Omen.

I don't use a dual core cpu. But ty for feedback. I've read a bit of Slouken's posts. They're looking into fixing/changing a few problems. But further reading modders show that most of the problems they found were because they needed to update thier code. The authors that did do this have fixed a lot of thier issues. I'm more of the opinion with blizz in that you need to fix/look into the coding and fix it. I'm not saying it's all Omens fault. I'd guess every single addons i have contributes to the fps loss. Adding the loss up cumulatively causes a huge fps loss which frankly is unacceptable. I can't play at 8fps while i MT stuff in a 25 man raid. To say it prolly isn't Omen is like ignoring the issue. The GUI code needs to be updated like everyone else imo or at least looked at real good.