[The Eye] Void Reaver

[KayleeFrye1]

Description:

Tanks are top threat, averaging 1000-1500 TPS. After knockback- seemingly random players get aggro whereas those tanks on 2nd and 3rd @ threat can't get aggro.

How it works:

https://puu.sh/CKK5E/a7414bee92.mp4

There seems to be an issue with the spell "Knock Away" on Void Reaver as he will suddenly chase/target a random player who is below the 2nd and 3rd tank on threat. Several people have reported here on the Sunwell Bugtracker that the use of both Omen Threat Meter and Diamond Threat Meter didn't make any difference in the threat result. This leads us to think that the problem is the boss ability and not the threat display addons.

The ability reads:

Knock Away: Single Target knock back vs. the highest aggro target, reduces aggro, and 30 sec cooldown. Can miss, be dodged, or parried to avoid the threat reduction. (Source: https://wow.gamepedia.com/Void_Reaver)

We suspect that either the Knock Away ability does too much threat reduction for the tanks, or that he completely wipes threat table several times during the fight, confusing the Threat Meters used. In the clip linked in the report here, one can see that Christucker (1st Tank on threat) and Klapperslang (2nd on threat) is on seemingly 220 k Threat and 171 k Threat. Suddenly Void Reaver swaps and targets Qlu (130 k threat) Shadow priest.

• Straight before Void Reaver Changed target: https://gyazo.com/5fffee2fbcd942fc9cd1cc0f6428d94e
• Right After he changed target to Qlu and the threat meter goes wild: https://gyazo.com/a2c96e2b2fd234f02bd3cba891d8ec93
• Keeps chasing Qlu til he dies from Melee Attack: https://gyazo.com/1f53f8f322d02e908d1e762cded2a4fe

As we can see Christucker, who was the first tank on threat dropped down to 179 k Threat from 220k. Yet Qlu is still on 132 k Threat but continues to have aggro. This is confusing as Either Christucker or Klapperslang (2nd tank on threat) should be the one having aggro after Christucker seem to have been hit by "Knock Away" - reducing his threat.

How it should work:

Something is wrong regarding threat! We had 3 tanks rotating heroism and spamming drums, that should be WAY overkill! "Knock Away: Single Target knock back vs. the highest aggro target, reduces aggro, and 30 sec cooldown. Can miss, be dodged, or parried to avoid the threat reduction." Most likely the threat reduction is waaaay to big @knockbacks

Source (you should point out proofs of your report, please give us some source):

https://wow.gamepedia.com/Void_Reaver

[kyotpls]

This clearly needs to be adressed as the whole boss mechanics is based around managing threat for tanks and never surpassing them on threat. It's extremely confusing how he can suddenly target random ranged (only ranged, not other melee's) when they are barely even 2/3 of the tanks threat.

[Ironjudgment]

Killed it yesterday and it was working fine. (maybe some update broke somthing?) Check threat with .debug threatlist command to display server aggro information instead of using an addon.

Also for your sources you should use articles from before March 2007 (pre nerf timeframe). (https://wow.gamepedia.com/index.php?title=Void_Reaver&oldid=565232)

[kyotpls]

@Ironjudgment What tactic did you go with? Having all ranged within Pound range and 1 designated Arcane orb kiter or spreading out like we did in the video? We have a suspicion that the tactic we used might be causing the problem not having people closer to the boss for some wierd reason. I've seen videos from other guilds using the other tactic with Arcane Orb kiter and having the rest in melee range but below tanks on threat, and it worked fine for them.

[Ironjudgment]

@kyotpls We have used the tactic where everyone stacks in melee range and we had a designated kiter for orbs. [3 Tanks] https://youtu.be/ZehJqsGXDNc?t=10374

[kyotpls]

Thank you for clearing that, still seems to not be blizzlike. But we'll try to do it your way, and the way many others have done him and see if the same issue persist.

[neheri]

Boss seems to be working fine.

Knockback reduces aggro by 25% which is a lot and the longer you fight him, it hurts more.

Clearly DBM, Omen and KTM are not 100% accurate with threat situation. You can use .debug threatlist command to see real data queried from the server.

Priest was generating a lot of threat due to aoe heals, warrior was below him (despite what DTM said) and void went after priest. Try taking 3 or more tanks. The more tanks are getting knockback the less effective it is.

[KayleeFrye1]

@neheri Did you spread out when you killed him? Do you by any chance have a video to maybe help us understand what went wrong? :)

[neheri]

We were stacked and fought him in between his legs, but that increases tps from healers greatly.

There were some problems with losing aggro from tanks because of that knockback, but we did nothing special, used 3 tanks and the raid let us fight him without dpsing for some time and he sticked to tanks until few % of his hp left last week.

Use .debug threatlist command to get real aggro amounts from the server and if you see that someone is having too much threat tell him to stop dps. Use salvation and MD on offtanks. Dodge/party/defense from tanks helps a lot (knockback can be avoided - no threat loss). Just take your time killing him and you will be fine, 10 min enrage is a lot.

[flapse32]

Did voidreaver here, and did the .debug threatlist command. top 1-2 is dps/healer who has highest threat yet dont have aggro whatsoever.

The command itself might be fucked/bugged. So its not useful at all. OR the boss itself is bugged....

[flapse32]

Raids in general really need to be priotiesed on bug fixes. Vashj, Voidreaver, Al'ar pathing, etc etc etc. Majority of players are playing for pve on this server.

[neheri]

Command is working fine.

Ranged needs 130% to take over aggro, melee 110%. If your healer/dps had more than tank and the boss was still hitting the tank that's completely normal. After the moment tank loses aggro boss goes for number 1 in threatlist then 2nd and so on.

The boss is quite hard with the knockback, but with 3 or more tanks can be easily one shotted.

Knockback is reduicing threat by 25% which is a lot, especially during later stages of the encounter. It can be parried/dodged so extra avoidance helps.

What can possibly be incorrect is the ability's CD, but that needs research. At the moment he seems to be using it every 20 seconds.

[mchayes]

Big issue with its ability handling. It's very often that Void Reaver interrupts his pounding channeling with either Arcane orb or Knockback. Below you can see a coincidental 'extreme case'. First marker he didn't get a single Pounding tick off because he cast an Arcane Orb. 2nd he got 1 tick off and was interrupted by using another Arcane Orb.

From what I can see in the logs VR is forced to use Arcane Orb every 17sec and Knock Away every 14sec It's not uncommon that he casts knock/orb at the same time as an interrupt to his pound mechanic.

[xethra89]

Your issue is you are using a threat meter than works off combat log, and doesn't always account for aggro drops (or sometimes fails to calculate feign death resists, so it looks like you drop aggro but you don't). All client side threat meters on Nightbane have this issue. DTM, Omen, etc all have the same problems from time to time. That's why some fights your threat seems fine, and some fights the aggro tables is wacky.

You need to get Timed. The addon is a threat meter that works by querying the server for the threat meter using the .debug threatlist command and displaying it in a GUI. This addon is never wrong, because it is pulling directly from server side, rather than calculating through combat log on client side. People dont like to use it though since the addon only shows top 4 of list by default, and because it only works on private server cores that allow you to .debug threatlist. In retail (or Felmyst for example) it didn't work.