Isn't there a /threat clear command available now? Should do the job.
We did Bloodboil last night and had the same issues as reported above by songster: The first attempt, everything was perfect, on the subsequent attempts, people would start disappearing from the threat lists, and other people's threat wouldn't be updated any more past some initial threat value (for example, I, as main tank, would get a certain amount of threat from the misdirect, but then nothing else on top of that, so healers would quickly overtake me).
/omen clear did not resolve this issue, I used it before every pull after the first. However, it did reset any threat values that remained on the boss for some reason (some pet still had a few thousand threat).
If anyone's doing Bloodboil tonight and happens to wipe on the first attempt, can they try getting people to /reloadui in between pulls and see if that solves the problem? If so, we can use that as a workaround until Antiarc or Blizzard fix whatever the real problem is :-)
Our tanks were reloading after wipes on Bloodboil last night, and it seemed to fix it for them. (I wasn't on the raid, but the tank channel had more reminders to reload UI than anything else.)
Originally Posted by Brookston Beer Bulletin
“Beer brewers shall sell no beer to the citizens, unless it be three weeks old; to the foreigner they may knowingly sell younger beer.” — German beer law, 1466
- A fix was made to ThreatLib this afternoon to hopefully fix the Bloodboil issue
- Misdirection -seems- to be working for me, but I'll test it more.
- Thanks for the Invis logs. I'll get right on that.
- LibFuBarPlugin-3.0 is directly embedded (rather than referenced as an external) because it's a modded version designed to work without the Rock framework coming along for the ride. That version only lives in branches.
- Backwards compatibility hasn't been broken for about a week now. Of course, it's always best to be using the latest, but as long as people are running 67658 or later, they SHOULD be comms-compatible with current and future versions.
Edit: On one pull, I found I got no bars at all if I used the default Omen skin, while using the "Classic" or "Compact" skins showed the bars as usual.
This is likely because the Default skin doesn't have Autocollapse on, while the Compact and Classic skins do. You'll need to extend to size of the Omen window to your desired size to actually see bars. I'll see about adding a warning message if you have autocollapse off and the window is too small to show any bars.
Regarding the invisibility problem, I'm pretty puzzled as to how you're getting that behavior. Omen should:
- When Buff ID #66 is gained, start a timer, ticking once per second, which reduces all the mage's threat by 10% per tick.
- If Buff ID #66 is lost, stop the timer.
- If Buff ID #32612 (full invis) is gained, reset all threat to 0.
According to those combat logs, it SHOULD be behaving properly.
I obviously need to borrow a guild mage to test with!
Sorry if this is covered some other place but I couldn't find anything.
Would it be possible for "/omen center" to also reset the config window's position? Not quite sure how, but a guildie of mine managed to get the config window halfway outside the upper part of the screen and unable to move it. Another way would be to add more drag points I guess.
2 Issues i'm having on the interface side of things:
1. Every time I log out and back in, Omen moves a little, because threat bars will start stacking upwards instead of downwards until I move the window. I have the following settings:
Skin: Classic, Mode: Single-Target
Show when: In a group, in a raid, you have a pet
Clamp to Screen: Yes
Bars Window: Autocollapse
Grow up: No
Modules Window: Hide
Title Window: Hide
What it seems to be doing is loading in "grow up" mode (despite the options being set to grow down), and only beginning to grow down once I manually move the window back into the position where it's supposed to be. It happens the same whether Omen is locked when I log out or not.
2. The configuration GUI doesn't allow you to scroll the list of bar textures. This means those of us with SharedMedia can't access about half of our textures form the drop-down menu. Can be worked around by simply changing it in the WTF folder, but it's a pain.
Sorry if this is covered some other place but I couldn't find anything.
Would it be possible for "/omen center" to also reset the config window's position? Not quite sure how, but a guildie of mine managed to get the config window halfway outside the upper part of the screen and unable to move it. Another way would be to add more drag points I guess.
I don't know how well-known it is yet, but Omen is now taking advantage of the ability Blizzard added to allow Mod authors to integrate their config windows into the Blizzard Interface options window. Open it up, and at the top there should be a tab for Omen which acts just like the omen-specific config window. Now if only all of the Ace addon authors would support this...
In healer mode, Omen only wants to let me get tank data from Blizzard main tanks. The problem is that, since sometime recently, I can't set Blizzard main tanks (no idea why). I'd like to be able to let it take data from oRa/CTRa again.
Regarding the invisibility problem, I'm pretty puzzled as to how you're getting that behavior. Omen should:
- When Buff ID #66 is gained, start a timer, ticking once per second, which reduces all the mage's threat by 10% per tick.
- If Buff ID #66 is lost, stop the timer.
- If Buff ID #32612 (full invis) is gained, reset all threat to 0.
According to those combat logs, it SHOULD be behaving properly.
I obviously need to borrow a guild mage to test with!
I talked to other mage after our brutallus fristkill tonight ( :> ) and they reported the same problem, so it's supposedly not a problem with my client or my addons.
Add Shade of Aran and Priestess Delrissa's crew to the threat-blacklisted mob IDs
Shade of Aran absolutely has a normal threat table and follows aggro rules. He's a caster who prefers to cast but he won't ALWAYS cast, especially if you lock out all three schools. That's why he likes to run around the room sometimes -- it's entirely aggro-based. Have a dual-wield devastate prot war on him and he'll melee the prot war sometimes. Have a hunter or mage atop the aggro list and he'll run off to one side towards that player sometimes. Threat is relevant on Aran. I'd limit the "blacklist" to mobs that truly don't have conventional threat lists at all.
The mobs involved with the Priestess Delrissa encounter also follow conventional aggro rules to some extent. I can actually tank one or two of the mobs involved in the encounter at a time until DPS starts on them; every so often a mob will turn away from me, but a quick Judgement of Righteousness, Avenger's Shield or Exorcism is all it takes to get them to immediately turn back and start attacking me again. One mob is pretty reliable to keep on me with 8 second Judgements, a second mob is somewhat trickier as it depends both on the target being a Demon and the moves I have available for the second target are on longer cooldowns.
The behavior of the mobs seems closer to their threat clearing very often then them not using a conventional threat list.
buff /bʌf/ Pronunciation[buhf]
–verb (used with object)
- to reduce or deaden the force of
Shade of Aran absolutely has a normal threat table and follows aggro rules. He's a caster who prefers to cast but he won't ALWAYS cast, especially if you lock out all three schools. That's why he likes to run around the room sometimes -- it's entirely aggro-based. Have a dual-wield devastate prot war on him and he'll melee the prot war sometimes. Have a hunter or mage atop the aggro list and he'll run off to one side towards that player sometimes. Threat is relevant on Aran. I'd limit the "blacklist" to mobs that truly don't have conventional threat lists at all.
I've had a few people argue this change with me, and I'm hesitant to revert it for two reasons:
1) Threat shouldn't matter on the fight.
2) I suspect he wipes aggro very often, which would make threat data pretty useless. I've seen him run off and chase a caster doing 800 DPS when I'm pulling 1500+ DPS on him with my rogue, without Salvation.
I can still be convinced to revert it, but I don't think that threat data is useful on the fight.
One thing that the dps in my guild has noticed is that they can never see our prot paladin on Omen during Brutallus. They can see me (warrior) just fine but when the prot pally taunts after the three slashes have gone off he doesn't show up on Omen.
One thing that the dps in my guild has noticed is that they can never see our prot paladin on Omen during Brutallus. They can see me (warrior) just fine but when the prot pally taunts after the three slashes have gone off he doesn't show up on Omen.
This happened to ours too - do a version check.
Our Pali swears he's got it installed but shows up as not installed/out of date. I'm thinking that either he'll have a copy of Threat2.0 in his addons folder/subfolders that isnt correct or there might be a Pali addon that's conflicting and he's supressed lua errors - those are the directions I'm investigating now anyway.
1) Threat shouldn't matter on the fight.
2) I suspect he wipes aggro very often, which would make threat data pretty useless. I've seen him run off and chase a caster doing 800 DPS when I'm pulling 1500+ DPS on him with my rogue, without Salvation.
Not that Aran matters much nowadays, but I can corroborate that he seems to follow normal threat rules when not casting, which happens occasionally after interrupts and is even a frequent event if you do 3 interrupts in a row and lock out all of his schools. I've always fought him in defstance to make him stay put and he invariably starts running after me if he's interrupted a few times while I go off beating on elementals for 30 seconds or so. Omen has always been an accurate indicator of what he's going to do as well; as accurate as it is with most bosses at least.
Running over to auto-attack someone isn't necessarily proof of a "normal aggro table" - he could be designed to randomly punch just as he is designed to randomly cast frostbolts/fireballs/arcane missiles, its just that casting will always be preferred if he can.
The best way to test it would be to a) get a version of omen that doesn't blacklist this fight, and b) get a group that can always lockdown every schoolspell. It might also help if you only had one guy generating aggro (the tank perhaps, or perhaps test it both with ranged and melee aggro generation) while everyone else stands there and only uses their cs/kick/shock, to help ensure an aggro disparity between them and the intended punch-target. If that one guy gets punched consistently, it would probably be safe to say that its not random. You could try switching the aggro generator halfway through to test if it gets dropped anywhere along the way (the new guy generating threat would get punched much sooner than expected).
Running over to auto-attack someone isn't necessarily proof of a "normal aggro table" - he could be designed to randomly punch just as he is designed to randomly cast frostbolts/fireballs/arcane missiles, its just that casting will always be preferred if he can.
The best way to test it would be to a) get a version of omen that doesn't blacklist this fight, and b) get a group that can always lockdown every schoolspell. It might also help if you only had one guy generating aggro (the tank perhaps, or perhaps test it both with ranged and melee aggro generation) while everyone else stands there and only uses their cs/kick/shock, to help ensure an aggro disparity between them and the intended punch-target. If that one guy gets punched consistently, it would probably be safe to say that its not random. You could try switching the aggro generator halfway through to test if it gets dropped anywhere along the way (the new guy generating threat would get punched much sooner than expected).
The folks above aren't saying he "randomly ran over to punch someone". They are saying he predictably ran over to punch the guy at the top of the threat list, in particular a warrior in defensive stance spamming devestate.
I have to go against those above, honestly. On alt Kara nights, my Shaman (Enhancement, in melee, no Salv) can pull around 900~ DPS where a mage (Who is occasionally moving from Blizzard, etc) in the group was doing about 600-700 at range. Neither had salv, neither had anything to prevent aggro (Such as Invis, trinkets to reduce, etc), and when he was shocked by myself out of Arcane towards the last few percent during a burn, he turned and took off towards the mage and melee'd him once before resuming his casting rotation.
In any event, it may not be definitive, but I can surely say I've seen more random aggro than anything. I honestly doubt he had a consistent static aggro table. As stated before, I bet there are random drops in aggro somewhere in this, such as when he teleports to the center for Blizzards or Explosions or Wreaths. Possibly for a version, would you be able to code in that during any of those events that force his teleport to set an aggro drop? Possibly that is where it's at?
I have to go against those above, honestly. On alt Kara nights, my Shaman (Enhancement, in melee, no Salv) can pull around 900~ DPS where a mage (Who is occasionally moving from Blizzard, etc) in the group was doing about 600-700 at range. Neither had salv, neither had anything to prevent aggro (Such as Invis, trinkets to reduce, etc), and when he was shocked by myself out of Arcane towards the last few percent during a burn, he turned and took off towards the mage and melee'd him once before resuming his casting rotation.
In any event, it may not be definitive, but I can surely say I've seen more random aggro than anything. I honestly doubt he had a consistent static aggro table. As stated before, I bet there are random drops in aggro somewhere in this, such as when he teleports to the center for Blizzards or Explosions or Wreaths. Possibly for a version, would you be able to code in that during any of those events that force his teleport to set an aggro drop? Possibly that is where it's at?
You were doing 900 DPS but assuming you're DW spec enchance you have the Spirit Weapons talent, that reduces the threat you do with melee attacks by 30%. Your TPS would have been ~630, a little higher depending on shock damage. If the mage was arcane spec'd and has Arcane Subtlety then your argument would hold. If he isn't arcane and he was doing more than 630 DPS he can very well "pull" aggro on aran, since his DPS is 1:1 with TPS.
To add to the discussion on Aran omen has always been very accurate on who he runs after depending on their threat. It's always been useful for me as a healer, dps or tank. It let me infer where he might run so I can be sure avoid the 10 second CS.
That said if he doesn't show up on Omen I'm sure I'll manage to live and certainly wont make or break the encounter but it does have its uses.
The folks above aren't saying he "randomly ran over to punch someone". They are saying he predictably ran over to punch the guy at the top of the threat list, in particular a warrior in defensive stance spamming devestate.
And antiarc replied (purely an anecdote yes, but still something to consider) where he DID go to punch someone NOT on top of the aggro list.
Originally Posted by Antiarc
2) I suspect he wipes aggro very often, which would make threat data pretty useless. I've seen him run off and chase a caster doing 800 DPS when I'm pulling 1500+ DPS on him with my rogue, without Salvation.
Regarding the invisibility problem, I'm pretty puzzled as to how you're getting that behavior. Omen should:
- When Buff ID #66 is gained, start a timer, ticking once per second, which reduces all the mage's threat by 10% per tick.
- If Buff ID #66 is lost, stop the timer.
- If Buff ID #32612 (full invis) is gained, reset all threat to 0.
According to those combat logs, it SHOULD be behaving properly.
I obviously need to borrow a guild mage to test with!
Problem: The moment you hit invisibility your threat is instantly cleared instead of when you turn invisibile.
I don't get how what I did fixes things, but:
In mage.lua
function Mage:ClassInit()
-- self.BuffHandlers[32612] = self.Invisibility
self.BuffHandlers[32612] = function(self)
if timers.InvisAggroModifier then
self:CancelTimer(timers.InvisAggroModifier)
timers.InvisAggroModifier = nil
end
self:MultiplyThreat(0)
end
self.BuffHandlers[66] = self.Invisibility
Just changing the order of the BuffHandlers fixes things. (Tested on a fresh copy of omen) I think something further upstream of mage.lua might be broken.
Also, when I was playing around spewing out information I found that you are starting the invisibility function on spellcast rather than when the mage gains the pre-invisibility buff.
This is where the Invisibility function is being called currently. (action, spellID) (gain, 66)
Pretty sure the second is where the threat reduction starts ticking. Probably not a big deal since each happens within a few hundredths of a second apart.
Also, the self.BuffHandlers[32612] function gets called twice. Not sure if there is any significant overhead in doing a threat clear twice. (gain, lose are both valid for a threat clear. As you have the same threat when you have completed invis buff as when you leave.)
Just to note, the latest release seems to have fixed Paladin threat. After some massive Omen weirdness on Gurtogg with a Pali/Warrior/Druid MT team I finally forced the whole raid to log off and update last night.
Once the whole raid was on Omen 68769.2 and Threat-2.0 68842 sanity was finally restored
Huntes seem to pull aggro a little early still, but thats purely anecdotal on my side.
I've been experiencing some problems regarding Omen and Feign Death. This is what I belive is causing it anyway.
What happens is that I pull aggro, even though I'm nowhere near the top off omen, not even in top 8.
I'd guess it could be omen ressting even if my FD resists? If anyone else has had any similar issue please let me know!
04/07/08, 10:44 AM
Similar Threads
