Open Xadras opened 8 years ago
#!c++
Righteous Fury is working correctly until relog. Then the buff is no longer owned by the player ( UnitBuff() doesn't return a duration anymore). This seems to break the threat increasing effect.
Original comment by John (Bitbucket: Jonghyunnie, GitHub: Unknown):
I think paladins are the ones having issues with threat. Warrior tanks seem like it works to many others.
Original comment by Anon X (Bitbucket: Anonx, GitHub: Anonx):
Totem != Tank -> https://bitbucket.org/looking4group_b2tbc/looking4group/issues/406/totem-threat
Original comment by Charm (Bitbucket: Charmagon, GitHub: Unknown):
maybe certain classes?
Shamans totems seem to produce crazy threat, especially mana spring.
Original comment by Charm (Bitbucket: Charmagon, GitHub: Unknown):
Did durn hold and threat was fine for me as a warrior. Bm was also fine.
It feels like this is certain instances.
But I will say it is off putting. In one Alcatraz drop my group gave me time to build aggro, I had 3 sunders from devastate on the target and at least 2 revenges and a few shield slams.
It took one mortal strike to completely loose aggro.
That is not working as intended!!!
Original comment by Muh Dik (Bitbucket: Bananawrangler, GitHub: Unknown):
Haven't had a single problem with threat as a paladin until yesterday evening. Shattered halls went perfectly and after a dc (update?) i kept losing threat in Ramparts & Slave pens HC. This is ridicolous, even judgment of righteousness and avenger's shield could'nt overaggro a previously cc'd mob from the healer. I refuse to tank under these circumstances.
Original comment by Anon X (Bitbucket: Anonx, GitHub: Anonx):
no explicite Threat changes, only thing i know of what was changed what can have impact on this topic was spellpower modifiers for spells ( Corruption Consecration and Holy Nova ) but they were increased so it should benefit palatanks and they were minimal )
Original comment by John (Bitbucket: Jonghyunnie, GitHub: Unknown):
I don't even want to dungeon anymore, kinda demotivated cause i'm afraid of constantly losing threat. Stupid right
Original comment by Freeznfire (Bitbucket: Freeznfire, GitHub: Unknown):
I ran a heroic tonight with a well geared prot paladin, I pulled off him constantly as my offspec. Normally a paladin can hold aggro no problem off me, something may be wrong.
Original comment by hitpoint (Bitbucket: hitpoint, GitHub: hitpoint):
Why are you taking this personally? I didn't attack you or suggest anything like what you're saying. And I absolutely do not want RF to be nerfed. I want everything to work correctly. I just stated exactly how this bug report could be perceived. I said that this could be a bug, you just have to show it. And I said it's probably paladin only because I think warriors are fine.
My post was just to point out that to get bugs fixed as fast as possible, you should provide evidence. Invite someone to your group, build agro, and have them build agro until they pull. Then show what omen says about it. If you really want this to be fixed, that's a good way to go about it.
You said the RF bug (where it caused too much agro) was fixed? The bug report can be marked as corrected then? I've seen nothing about it, and haven't grouped with a prot pally since so I really don't know.
Original comment by Codey Choi (Bitbucket: Qundo, GitHub: Qundo):
I mained pally tank in vanilla all the way through Warlords so I know the difficulties. As for Omen, I raid, of course I have it. Have you been playing and/or not around ? The righteous fury bug has been corrected. Despite wiping 10+ times, no relogs, I still can't hold aggro. Yes, I know fury warriors pull aggro a lot, but not from a geared kara paladin when the warrior is FRESH 70 in greens. It seems like even when righteous fury is fixed from the bug, you're still constantly trying to nerf threat on them. Do you even play a paladin? If you do, you would have realized the threat change and that the righteous fury bug does NOT work anymore. Don't believe? Go test it out yourself. All i'm saying is, perhaps the 50% additional threat from the talent tree MAY not be working correctly?
Original comment by hitpoint (Bitbucket: hitpoint, GitHub: hitpoint):
Are you guys using threat meters? So far this thread reads like this: either a lot of tanks don't remember how hard it was to tank in TBC, or a lot of dps don't understand that they have to watch their threat on every pull. These accounts of difficulty holding agro are all anecdotal until you have evidence. Fury warriors pull agro, all the time, that isn't uncommon. You may have to use taunt a lot in your groups, that's why you have it. That said, there is definitely a bug with RF pulling WAY too much threat in some cases, so I believe there could be a problem with RF pulling too little threat in others. But this would be for paladins only. I still haven't found a problem with warrior threat since my post here a month ago.
If this is being caused by a bug, then you need to get a proper version of omen, and watch it. Omen is not correct 100% of the time (it can be fooled by taunting taunt immune mobs etc.), but it's better evidence than what you have right now. So watch your omen. If people are pulling off you when you are above them on threat, and you are sure it isn't due to a mob mechanic, then report that. Omen just calculates the threat value of spells + the damage of them, and puts them in a chart. So, Omen is telling you how much threat you SHOULD have if everything on this server is working correctly. If people are pulling threat when Omen shows you above them, then something is wrong. It's a very easy test.
Original comment by Codey Choi (Bitbucket: Qundo, GitHub: Qundo):
Same issue, feels recent to me. Was doing kara and had everything on CD. Guildies were asking me if I kept dropping aggro and was kinda embarrased lol. Our DPS kept dying cause they kept ripping it off of me with consecrate; they all had salvation. Did heroics right after, same issue. Couldn't really hold aggro for anything. Did righteous fury/pally threat take a beating? It's a pain in the ass to tank right now with everyone taking aggro. Infuriating cause it seems like I can't tank or something.
Original comment by Andrew (Bitbucket: alogsdon, GitHub: Unknown):
A recent change must have taken pally threat below where it should be. On curator tonight, my threat was too low for players to deal even ~700 dps (with salv on them). I had about 240 spell power, crusader was judged on the boss, and kept my judge(righteouss), holy shield, and consecrate on CD.
Original comment by John (Bitbucket: Jonghyunnie, GitHub: Unknown):
Yeah i'm doing heroics now and shit is ripping off of me left and right. I'm not generating threat enough. I even tried canceling and reactivating righteous fury but after 2 seconds, even with crusader judgement on under my consecrate, single targets are ripping off of me like crazy. Something seems undertuned for pally threat. I have all the recommended spell power and whatnot. Happens in normal too, thought it was just normals.
Original comment by Charm (Bitbucket: Charmagon, GitHub: Unknown):
Another factor I have noticed.
If mobs cast an ability which would make you loose aggro (such as mind control). Regardless to weather the ability actually manages to go off or not, the threat is still lost.
For example
In Sethic Halls, the time lost controllers drop a mind control totem. Normally you have a few seconds to kill it before it takes affect, but it seems to cause the aggro to reset regardless if it is successful or not.
Is it possible that other mobs have similar mechanics which are causing threat resets when they shouldn't? It would explain why the threat seems "wonky" as it would be more a situational thing that doesn't apply to all mobs.
Original comment by John (Bitbucket: Jonghyunnie, GitHub: Unknown):
But then again, I never did kara yet. Only regular 70 dungeons
Original comment by John (Bitbucket: Jonghyunnie, GitHub: Unknown):
Hmm I've had problems holding aggro as a pally tank, never really witnessed the crazy threat holding.
Original comment by Anon X (Bitbucket: Anonx, GitHub: Anonx):
maybe connected to https://bitbucket.org/looking4group_b2tbc/looking4group/issues/2343/massive-paladin-threat
http://wowwiki.wikia.com/wiki/Kenco%27s_research_on_threat?oldid=1491085
http://wowwiki.wikia.com/wiki/Paladins_as_tanks?oldid=1600628
http://wowwiki.wikia.com/wiki/Righteous_Fury&oldid=1563278 , http://wow.gamepedia.com/index.php?title=Righteous_Fury&oldid=1563278
spell_threat
Original comment by Charm (Bitbucket: Charmagon, GitHub: Unknown):
as a warrior tank and feel it's not correct.
I am experiencing the same as the original poster.
Although it seems to vary with instance. Alcatraz seems really weird, and I am not talking about the sentinals
Originally reported by: Anonymous
I've noticed lately that threat has been a bit wonky. Firstly, I main prot pally, I usually have everything covered in terms of threat. I have Omen and I keep track of every target, but my friend (shaman) even waited before DPS'ing on targets and one stormstrike pulls off aggro instantly. I had him on blessing of salvation on check to make sure he always had it, but it still posed as an issue. There shouldn't be that huge of a disruption of threat even after waiting. I realized even some of his white damage was pulling aggro on targets I had full control of.
At first, I thought I just sucked maybe? Second occurrence was me playing a mage. I was pulling aggro in two frost bolts, despite even waiting a couple of seconds. The whole group was pulling aggro super easily too. The tank was a druid and he was properly spec'd since I inspected him. Which leaves me wondering if the threat has somehow diminished on tanks through some patching or maybe an issue arose? Either that or perhaps Improved righteous fury broke again? I checked bitbucket for it but it says it disappears upon relog or something. Whether or not it be righteous fury, I think it's just threat in general that's having some issues.