I agree with you in my post above - I'm just mostly wanting to make sure that there's no specific case anyone can think of where this behavior would cause problems.

Okay talked to the raid abit and this is what people seemed to remember.

P1 END: "I don't want to go back!"

P2 start: "I can grant you anything you want, for a price"

P3 start: "Beware I live!"

This might not be 100% correct though, as this was just what people could remember when asked on ventrillo.

P2 edit: "I can grant you anything you desire, for a price"

since its Essence of Desire ^^

VE/VT cannot generate threat on a mob that hasn't spawned yet. When a Strider spawns and the Shadow Priest targets it, the thousands of threat he sees is not correct.

I don't see the harm in just keeping the extra mob lists until dropping combat, so if you do generate threat on something, can't mouse over it for awhile, but then mouse over it again later, the list sticks around. Moroes would be an example.

The global list seems a bit odd to me, it would make more sense in my mind to just add whatever threat healing generates to all the mob tables that we currently know about at any certain time, rather than maintaining a separate global list. However, you probably did it for reasons that elude me, so I'll just shut up and appreciate your hard work.

No kidding?!?!? I never knew that mobs that are non-existent don't have threat tables!

I was explaining why the incorrect threat info appears/how Threat handles things, not trying to say that that's how it actually works for the game.

Maybe I'm missing something here as people are saying that Void Reaver works fine for them with Threat/Omen but it didn't seem to work well for my guild or myself last night. I'll apologize in advance as I don't have the version number offhand, think it was 41330ish. I had downloaded it around 6pm PST last night using WAU.

Basically the original MT was showing as having aggro throughout the entire fight regardless of who was actually tanking Void Reaver at that time. In reading this thread it seems clear that there is a hardcoded reduction between 20 and 30% of the tanks current threat on knockback. Yet for all 5-6 attempts we did not once did this seem to be applied as all 3 tanks kept the same position on the threat meter for the entire fight. Therefore the ranged dps had no real idea of where they stood threat wise vis-a-vis the tanks and we had constant threat issues which ruined at least half of our attempts.

Therefore I guess what I'd like to know is if there is something I need to do to trigger the boss module to run? I believe I saw the Threat1.0 warning in the chat frame that "Void Reaver" module enabled but I'm not totally positive. If that is correct then does the knockback just apply to the "Aggro Gain" bar?

Thanks again for all the hard work you've been doing, most of my guild members like it so far though situations like last night are always a bit of a headache

Hm. If you saw a "module enabled" message, you're using a really old version. Last night's build should have been just fine.

I did Void Reaver last night, and behavior seemed okay - were there any errors or anything that popped up?

Nope, nothing in the BugSack. And I might have been just imagining the "module" enabled warning from Thursday or even earlier. Like I said I'm not positive on that.

I am positive though that on all 5 or 6 attempts tank threat did not appreciably move and that the MT would always be way ahead on threat no matter who was actually tanking at the time. I was one of our OT's and usually I'd be #2 on the list even though for half the attempts I only ever had aggro once or twice with it bouncing between our MT and another druid (who was consistently #3) the majority of the time. Our 2nd attempt we had a warlock and two mages pull aggro while not even visable on the meter because of all the tanks/melee bunched at the top. People then got all tepid and we fell behind on dps consistently.

Have you observed this kind of behavior on any other encounter? It seems really odd that this would only show up on VR, which is really a very straightforward fight threat-wise, knockback not considered.

Did you set a special VR knockback multiplier or anything (anything over 1.0 would have caused, uh massive problems)?

Nope, I didn't set any modifier myself as I figured it was already hardcoded in per the comments in this thread.

Overall Threat/Omen have been fine for us all week though it's not like we have a ton of 25 man content on farm. Just Maulgar, Gruul and Magtheridon currently. The only other oddity I've consistently noticed is on Maulgar.

For Maulgar we have a 2nd tank go in and taunt at 60 or 70% for the sub 50% phase, he then goes and sits back by the casters after the taunt wear's off and the MT has aggro back. His threat does not go into 2nd place though even though Maulgar consistently runs to him after a fear happens.

I haven't noticed any issues on Gruul or Magtheridon so far though I missed our Mag kill so I can't say with any certainty there.

I will say again though that I'm positive tank threat was not being reduced last night as every guild member using Omen commented today on the issue that arose for our attempts last night.

This behavior consistently happened to me on Void Reaver - every time I pulled aggro it was right after being targeted for Arcane Orb, even when there were people ahead of me on the threat list.

Mobs used to drop their target when they were CC'd by things like fear, meaning that they had no current aggro target when they were taunted while CC'd, thus taunt would do nothing with respect to threat. Mobs keep their targets now, and presumably taunt will now inherit the threat that target has (assuming the taunter doesn't already have higher threat).

I've also pulled off void reaver when I don't believe I had enough threat to actually pull off either MT immediately after being targeted for an Orb

Regarding Reliquary of Souls phase triggers: there is a small problem with the mentioned phrases, as our local BigWigs crack noticed while writing a mod for this encounter. The essence can either yell the demonic phrase or the 'normal' one. I think he ended up simply adding both as triggers for the next phase.
Unfortunately, I don't have any of these phrases at hand, at least not until next reset.

Just a thought, but if it is a common practice to keep CoT on a mob, wouldn't it be good to watch for the demonic emotes as well?

I don't happen to know the mechanics of CoT as far as how it changes the text, but if it is a static translation I would imagine it would be worth the relatively minimal effort to add it to a list of triggers for bosses where it may be used.

I'd like to add in that we most definitely have not been seeing proper results as far as Void Reaver goes as well. Mainly the issue that the tanks are not seeming to have any agro taken away. Not a big deal as it's easy to know which ones have had 50% of their threat taken away, but each week we hope for it to work out!

Next, our shadow priests are continually complaining about how much they hate omen. It seems as if their threat is just never correct. It works really well for every other class, yet for example on tonight's BT raid, our SP pulled Na'jentus at what omen read as 85% MT threat.

It seems as if for some stuff Omen is right on the money for them, but other fights they're just either showing extremely high threat, or pulling at far lower than 130% tank threat.

Could this have anything to do with our MT still using KTM along with Omen to continuously compare numbers between each new revision? Or is this a problem with threat lib's calculations of SP threat?

This is going to keep happening over and over if you don't deal with the "new mob" thing a bit better.

Here is a suggestion:

If combat has been longer than 10 seconds, and a mob is new, then set its individual threat per person equal to the negative of their global threat (so that it reports 0 to start).

The "new mob delay" might need some tweaking, but most of the time, if its been a little while you can assume the mob hasn't been there the whole time without a single threat action against it.

Hello, i was using Threat metter untill one day ago, when we decided( the warrior from my guild) to step onto Omen.So we download it, for some of us is working perfectly,but, i get the following error when i open wow log in), and also during fights, randomly.

Date: 2007-06-26 12:23:24
ID: 51
Error occured in: Global
Count: 1
Message: ..\AddOns\Omen\Libs\Threat-1.0\Threat-1.0.lua line 437:
AceComm-2.0: Cannot set prefix to "Thr", it is already in use.
Debug:
Ace2\AceLibrary\AceLibrary.lua:33:
Ace2\AceLibrary\AceLibrary.lua:31
Ace2\AceLibrary\AceLibrary.lua:679: Register()
...e\AddOns\Omen\Libs\Threat-1.0\Threat-1.0-Cleanup.lua:40: in main chunk

Date: 2007-06-26 12:23:27
ID: 52
Error occured in: Global
Count: 1
Message: ...dOns\Threat-1.0\Threat-1.0\ThreatClassModuleCore.lua line 439:
attempt to index field 'BuffModifiers' (a nil value)
Debug:
...dOns\Threat-1.0\Threat-1.0\ThreatClassModuleCore.lua:129: ToggleModuleActive()
...dOns\Threat-1.0\Threat-1.0\ThreatClassModuleCore.lua:155:
...dOns\Threat-1.0\Threat-1.0\ThreatClassModuleCore.lua:150
[C]: ?
Ace2\AceEvent-2.0\AceEvent-2.0.lua:232: TriggerEvent()
Ace2\AceEvent-2.0\AceEvent-2.0.lua:931:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:929
[C]: ?
Ace2\AceEvent-2.0\AceEvent-2.0.lua:329:
Ace2\AceEvent-2.0\AceEvent-2.0.lua:310

I hope someone can help me with that, im not an pro with this kind of things, thank you!

was using omen and recount last nite in SSC to test out during a raid. KTM was disabled and I noticed a 50% loss in FPS when omen was activated. Shut down omen, turned ktm on, fps shot back up.

Was not the only one noticing massive fps loss like this. Normally in 5mans it's fine but in my 25mans it was going bonkers.

3 of us were using omen with latest build. 1 was using .100 versions behind. Was this the cause?

Ya know, I wasn't confident enough that it was Omen/threat, so I hadn't posted, but since you opened the Pandora's box....:

I've had huge framerate losses on bosses (not trash, at least not sufficiently noticable) when I've had omen/threat enabled. I relog, disable omen/threat, and it doesn't happen on the next boss. I've only tested this on 2-3 raids though, so I'm not certain it's not something else (perhaps just logging out and logging in again.)

More specifically, the lag got worse for me as the encounter progressed.

Hmm, try deleting your threat-1.0 addon.


Try updating to the latest version (and your guild) there was a syncing bug involving enabling modules that could be the cause.