Suesse

Presumably the offtank has such a massive threat lead that you couldn't pull aggro if you wanted to. In reality, it doesn't matter if you taint the 2nd mob's threat level because it's already wrong due to the fact that you already took down one mob of the same name.

 

chase

Well in essence you are saying that you know better than Omen what your threat values are better than it can display. (Which is true in the case you are talking about) So by turning off publishing in the threat lib you are not "tainting" everyone elses meter. The fact that your Omen is showing bad numbers should not be a downside since by activating the macro to turn off publishing you have declared "I know what I'm doing".

So as long as you turn publishing back on once the same name mobs are down how does this not work for you?

 

• Adoriele

Because your publishing setting only controls whether Omen sends data to others, not whether it flashes and goes crazy on your screen. The idea isn't to tell others you know what you're doing, but rather to tell Omen to stop going crazy.

 

Silverstorm

The only solution is to do what we did before KTM/Threat1.0 were developed and play without the mod telling you what your threat is for those pulls.

In theory (I haven't looked at the code), a hack to add a "disable/enable" hook is possible, and you could wrap disable/cast/enable in a macro.

 

Whiteknight

The last couple of days I've been noticing an odd glitch in Omen. During tanking a boss, my TPS number will periodically 'glitch out' and show something absurd like 3billion threat per second, and then exponentially decay back to a more reasonable number. Absolute threat seems steady though.

On asking the raid, it seems other folk are seeing the same issue, but it seems to only affect the display of *your own* threat per second. I.e. mine only ever glitches out on my screen - for other players it's their own char's threat display that has issues.

I'll see if I can isolate it a little better, and try see if there's any updates today.

 

• Daboran

Same problem here. Also most of the raid got an Omen/Threat meter Ace error as soon as Phase 3 of Reliquary started last night.

 

Pillion

I remember reading or being told that it is possible to pull a mob even through it's current target is well ahead in threat.

This may be based on TpS (threat per second). For example the mob's current target is producing 100 TpS and a casters TpS is 131 TpS, so it may be possible to pull the mob from it's current target.

This would support current occurances we've seen recently, but I've been unable to find a confirmation of this theory.

Can anyone confirm or discredit this theory, and if confirmed offer proof? Or does any one know what is happening?

As I understand there is suppose to be a complete revamp of how threat is calculated in patch 2.4.So could this be unpublished changes to threat that Blizzard has made to get ready for 2.4?

 

◊ Penguin

Source? There's never been any indication that the threat model is being changed in 2.4, or that it was even up for review in any way. The only thing being revamped is how the combat log presents its data to both the player and to addons that call the combat log.

No. You have to pass the actual threat number of the person with aggro in order to pull. If you are in melee range that value is 110% of the aggro target's threat, if you are not in melee range it's 130% of the threat value. Your statement that it's possible to pull because of a higher TPS but not a higher actual threat value is just plain wrong.

You've offered no descriptions at all of what happened, making it impossible to tell you anything useful.

There's not some hidden "but he tries really hard" variable built into the game. -Slake

I always love the "it doesn't fit my style of play" line. There are only two styles of play; Correct, and Incorrect. The only people that ever use this line are people with the incorrect style of play. -Sebudai

 

Pillion

Sorry, let me explain the situation that we've had. Last week we were fighting Prince during phase 3 with the tank 20k threat above any one else our hunter pulled agro from the tank and Prince 1 shot killed him, and ran back to the tank. This happened seconds after the hunter feigned death. Due to bad infernal placement we wiped.

During a later attempt the same thing happened again I don't recall what phase it happened, but the tank had a comfortable lead in threat and the hunter feigned death each time it was up. We thought that Omen wasn't accurately reporting threat and had everyone go and get the current version of Omen since a few people didn't have it.

It happened a third time, but feign death had cooled down and the hunter was able to avoid being killed.

Last night we are doing Nightbane. This time it was a different hunter, and he pulled Nightbane when he was at about 15% health. The hunter said that he had missed a feign.

This has only happened with hunters, and both are in guild and play their class well, and has never happened before last week.

As for the "complete revamp of how threat is calculated in patch 2.4" rumor that was posted by one of the hunters who has been had this happen to him, so since I cannot offer any other sources please ignore that.

As for my statement "that it's possible to pull because of a higher TPS but not a higher actual threat value" I was actually trying to get confirmation or discredit that statement, which has been be discredited.

I hope that this will provide some insight as to what may be happening.

 

Docjowles

Maybe one or more of their feigns got resisted? Or someone is using a really spammy addon like older versions of DoTimer and Recount? There has never been any evidence of being able to pull aggro based on your TPS instead of your raw total threat, as Penguin stated.

 

Pillion

I would assume that if a feign was resisted that it should appear in the combat log?


As for the older version of recount or DoTimer I assume that others in the group could have had one or both, but the hunter is usually very good with keeping MODS up to date. In fact he and I were the only members in the group a week ago that had the updated version of Omen. Everyone else had a version that was just a few minor builds off.

 

Papajan

I think there's something wonky with hunters in Omen lately, possibly dealing with how Misdirect is handled. We had a hunter pull aggro on Azgalor and he was nowhere near the tank in threat. His FDs weren't resisted as far as he/we could tell, and even if they were, he has Omen anyway, so it should be reported correctly anyway.

 

Pillion

Our Hunter misdirects typically as often as it is up during boss fights. Especially at the begining of phase 2 on Prince, and as Nightbane lands after flight phase.

So maybe there is something wonky with Omen and misdirect.

 

danny26

In regards to your hunters pulling aggro after a FD, it seems that when they FD thier threat is cleared from omen but not in the actual fight. To help solve this just make sure when they FD that they stay down for a couple seconds 2-3 and that will solve the problem.This problem seems to occur when the hunter FD's and pops back up instantly.

 

Uglesh

I'm not sure this is an Omen issue, but in the last 2 weeks I have seen some VERY weird aggro situations inside Kara and SSC. In both cases the player pulling wasn't a hunter (elemental shammy and warlock) but in both cases the player was WELL under the tank and yet they pulled aggro and we couldn't take it off them. In the one case, (on Illhoof) the healers kept the shammy up for about 20 seconds until I remembered that I could taunt him! My bad for forgetting that low level bosses can be taunted!

I wonder if anyone else has seen this sticky aggro in any other instances. I very much welcome any changes to the combat log that will make our Threat Mods work more efficiently.

 

Skyeh

I know this was posted five days ago, but I'm having the exact same issue, and it seems to have just started recently. I was wondering if there was a solution. I can try and supply some more information if it's an unsolved issue.

 

aclark360

omen owns

 

Hausnfranz

It looks like omen is completly bugging out after I installed HealBot, Natur Enemy Cast Bars, and Proximo. Not sure which mod is giving it problems. Having disabled all three of those addons, it seems that Omen is simply not working now. It will show the healer as highest threat, with everyone else at almost zero threat, and ONLY shows this information after the fight is over.

Did I screw up settings somewhere? Is it enough to just disable other mods, or do I need to completely delete them and re-install to start over?

 

denniz

As of the last few days on my hunter Omen isn't showing any bars anymore when I kill mobs with me and my pet, after I kill a mob it gives me this:

Date: 2008-02-17 17:43:45
ID: 52
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\Omen.lua line 528:
Bad argument #2 to `IterateGroupThreatForTarget`. expected "string", got "nil" (nil)
Debug:
(tail call): ?
Ace2\AceEvent-2.0\AceEvent-2.0.lua:301: TriggerEvent()
SpamMeNot\Main.lua:1170:
SpamMeNot\Main.lua:1164
(tail call): ?
Ace2\AceEvent-2.0\AceEvent-2.0.lua:914:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:907


And when I press the "Clear threat" option it gives me this:


Date: 2008-02-17 18:36:59
ID: 52
Error occured in: Global
Count: 1
Message: ...erface\AddOns\Recount\Libs\Threat-1.0\Threat-1.0.lua line 1469:
AceComm-2.0: `SetCommPrefix' must be called before sending a message.
Debug:
(tail call): ?
[C]: ?
[C]: error()
Ace2\AceLibrary\AceLibrary.lua:122: error()
Ace2\AceComm-2.0\AceComm-2.0.lua:1503:
Ace2\AceComm-2.0\AceComm-2.0.lua:1480
(tail call): ?
...erface\AddOns\Recount\Libs\Threat-1.0\Threat-1.0.lua:1469: RequestThreatClear()
Omen\OmenMenu.lua:89: func()
...terface\AddOns\Prat\libs\Dewdrop-2.0\Dewdrop-2.0.lua:721:
...terface\AddOns\Prat\libs\Dewdrop-2.0\Dewdrop-2.0.lua:660

 

Qrt

Omen showed no bars at all for me during tonights raid, so I had to try to get through our first Azgalor kill very Old School, feigning like a madman and being constantly afraid to get Azgalor in my face!!

I've done nothing to it but update using the normal WoWAceUpdater tool.

Dr. Frederick Frankenstein: Igor, help me with the bags.
Igor: Soitenly. You take the blonde, I'll take the one in the turban.
Dr. Frederick Frankenstein: I was talking about the luggage.

 

wind

Same thing happened to me. Tried updating via wowaceupdater, deleted then reinstalled the addon - nothing worked. If it's a known bug, I'm quite sure it will be sorted in the near future. However, if it might be an issue with some configurations/players/whatever, is there any way to find out what causes it?
I just don't get any bars at all. The /omen showpartyrevs command bugs out, and other people running it report me not running the threat library. Therefore, I assume it's not loading, somehow?!

 

Antiarc

Gah, someone broke something. I'll fix it as soon as I can figure out what's going on.

 

glowacks

This.

When playing my alt hunter I had Omen up nearly 100% of the time due to my pet. I learned very quickly that hitting feign death would clear Omen's threat immediately as long as it wasn't resisted, but I needed to stay down a short period of time to actually clear my threat on the server. I'm not sure on the exact duration necessary, and especially without a mob charging at you it's tough to know exactly how long to stay down. But I do know that you definitely cannot just hit feign death, wait for the cooldown to start, and start shooting again. I haven't played my hunter in months so I don't think its anything new, but it can be something that creeps up on you as a hunter when your gear and DPS get better and the tank generates very little more, if not less, threat. You might have not ever been clearing threat and now its coming back to bite you.

 

f1reburn

I also had some Omen issues yesterday after doing a full all-addon update on Wowaceupdater right before the raid starts. (always a bad thing =_=)

I tried to delete the Omen savedvariables and pasted some old savedvariabes of mine, still failed. Then I deleted both the Omen savedvariables and the Omen addon and downloaded Omen from Curse, which was the 11th Jan. version IIRC. This failed as well.

It finally worked when I just deleted the whole WTF and Addon maps, and replaced them an older copy.

So my guess is that the culprit isn't Omen itself, but some threat library. Aloft was also having issues with it.

 

Elhana

Threat lib got updated with externals for every addon you got - if it's Threat bugging, then downgrading just Omen won't help - you'll need to downgrade Threat in each and every addon folder using it