Maintenance for the week of January 6:
• PC/Mac: No maintenance – January 6
• NA megaservers for maintenance – January 8, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• EU megaservers for maintenance – January 8, 9:00 UTC (4:00AM EST) - 13:00 UTC (8:00AM EST)
• PC/Mac: No maintenance – January 6
• NA megaservers for maintenance – January 8, 4:00AM EST (9:00 UTC) - 8:00AM EST (13:00 UTC)
• EU megaservers for maintenance – January 8, 9:00 UTC (4:00AM EST) - 13:00 UTC (8:00AM EST)
Taunt counter and immunity
camrenis
✭✭
Hello all,
After having issues with keeping taunt up on the shade in vCR the other day and killing a few group members because of this (at a fault of my own not understanding that Untaunted conveniently tells you when something is taunt immune) I started to look into more detail about why taunt immunity was proccing in these situations. I asked around in a couple of guilds and a friend mentioned Taunt counter and pointed me to a post on ESO-U that explains how it works and provided two examples of how taunt counter/immunity function together. What I could see in various logs matched the first example, however the second example did not match the logs. It implies that the taunt counter starts at the first taunt, and lasts for a static 12s without any change by future taunts, and after this 12s the counter should reset (I also came across this description in a tank mechanic explainer on YouTube). This however (as shown by the log snip below) is not the case. I also came across varying descriptions of how others believed it worked, such as 3 taunts within 15s by at least two people (maybe an old mechanic according to UESP?), but none of them matched what I was seeing in logs.
I then started discussing this with another guild who were also having issues maintaining taunt in the shade, but also in other places where tanks swap semi-frequently (e.g. Navi), and every case came back to Taunt Immunity. After some testing with some friends I believe that Taunt counter/immunity actually works as follows.
Taunt counter is a stacking buff on any target that has a taunt debuff active. The buff lasts for 12 seconds, and refreshes every time a new stack is applied. The maximum amount of stacks that can be reached is three. Only two stacks can be applied by a single player - the third stack must come from another player. All three stacks can come from three separate players. The third stack procs taunt immunity, and taunt immunity will then end at the same time that the taunt counter buff with three stacks ends.
In the examples below, timer refers to the amount of time remaining on the targets taunt counter buff after the taunt is applied. Each of these examples we tested on a dummy and verified in logs (albeit with ever so slightly different taunt times as we're not robots).
Thanks for reading, and any further input/understanding/correction is of course welcome.
After having issues with keeping taunt up on the shade in vCR the other day and killing a few group members because of this (at a fault of my own not understanding that Untaunted conveniently tells you when something is taunt immune) I started to look into more detail about why taunt immunity was proccing in these situations. I asked around in a couple of guilds and a friend mentioned Taunt counter and pointed me to a post on ESO-U that explains how it works and provided two examples of how taunt counter/immunity function together. What I could see in various logs matched the first example, however the second example did not match the logs. It implies that the taunt counter starts at the first taunt, and lasts for a static 12s without any change by future taunts, and after this 12s the counter should reset (I also came across this description in a tank mechanic explainer on YouTube). This however (as shown by the log snip below) is not the case. I also came across varying descriptions of how others believed it worked, such as 3 taunts within 15s by at least two people (maybe an old mechanic according to UESP?), but none of them matched what I was seeing in logs.
I then started discussing this with another guild who were also having issues maintaining taunt in the shade, but also in other places where tanks swap semi-frequently (e.g. Navi), and every case came back to Taunt Immunity. After some testing with some friends I believe that Taunt counter/immunity actually works as follows.
Taunt counter is a stacking buff on any target that has a taunt debuff active. The buff lasts for 12 seconds, and refreshes every time a new stack is applied. The maximum amount of stacks that can be reached is three. Only two stacks can be applied by a single player - the third stack must come from another player. All three stacks can come from three separate players. The third stack procs taunt immunity, and taunt immunity will then end at the same time that the taunt counter buff with three stacks ends.
In the examples below, timer refers to the amount of time remaining on the targets taunt counter buff after the taunt is applied. Each of these examples we tested on a dummy and verified in logs (albeit with ever so slightly different taunt times as we're not robots).
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P1 TAUNT at 6s (COUNT=2, TIMER=12s). P1 TAUNT at 9s (COUNT=2, TIMER=9s). P1 TAUNT at 12s (COUNT=2, TIMER=6s). P2 TAUNT at 15s (COUNT=3, TIMER=12s, TAUNT IMMUNITY PROC FOR 12s). Counter and immunity fade at 27s.
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P1 TAUNT at 2s (COUNT=2, TIMER=12s). P1 TAUNT at 12s (COUNT=2, TIMER=2s). P2 TAUNT at 15s (COUNT=1, TIMER=12s). P2 TAUNT at 20s (COUNT=2, TIMER=12s). P2 TAUNT at 25s (COUNT=2, TIMER=7s).
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P2 TAUNT at 11s (COUNT=2, TIMER=12s). P1 TAUNT at 22s (COUNT=3, TIMER=12s, TAUNT IMMUNITY PROC FOR 12s). Counter and immunity fade at 34s.
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P2 TAUNT at 6s (COUNT=2, TIMER=12s). P2 TAUNT at 12s (COUNT=3, TIMER=12s, TAUNT IMMUNITY PROC FOR 12s). Counter and immunity fade at 24s.
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P2 TAUNT at 6s (COUNT=2, TIMER=12s). P3 TAUNT at 12s (COUNT=3, TIMER=12, TAUNT IMMUNITY PROC FOR 12s). Counter and immunity fade at 24s.
- P1 TAUNT at 0s (COUNT=1, TIMER=12s). P1 TAUNT at 3s (COUNT=2, TIMER=12s). P1 TAUNT at 8s (COUNT=2, TIMER=7s). P1 TAUNT at 12s (COUNT=2, TIMER=2s). P1 TAUNT at 16s (COUNT=1, TIMER=12s). P1 TAUNT at 20s (COUNT=2, TIMER=12s). P1 TAUNT at 24s (COUNT=2, TIMER=8s).
Thanks for reading, and any further input/understanding/correction is of course welcome.
1
-
zvavi✭✭✭✭✭
✭✭✭✭✭All I know that taunting by taunting 3+ times by more than one player within 12 seconds period will invoke overtaunt. And taunt won't be able to be refreshed till previous one runs out.Edited by zvavi on April 6, 2021 12:10PM1 -
JoSePHRiNG✭✭✭Thanks for the information, now I understand why my taunts sometimes do not work.Jorvuld's Guidance and SPC all the way down.0 -
Fennwitty✭✭✭✭✭
✭✭Does your group have more than one person trying to taunt the Shade of Z'maja? Maybe with abilities or armor sets? Start with that issue.
Bosses don't always stick to the taunt target, they frequently do one or more 'random' attacks even though taunted. Then they come back. Don't remember specifics about Z'maja right now.PC NA0 -
BXR_Lonestar✭✭✭✭✭
✭Honestly, I just use the fracture symbol to help time my taunts. When I see that debuff go down to around 4 seconds, I know I need to prepare to taunt, and it keeps me from overtaunting.0 -
Vevvev✭✭✭✭✭
✭✭✭✭✭I go to Settings > Combat and then scroll down to the bottom that lists buffs and debuffs. I set it to automatic so it's only shown in combat and then turn on debuffs I apply to my targets. The taunt icon is a broken shield and just having that turned on is a great help finding out what is and isn't taunted. Highly recommend doing that unless you have an add-on that does that already.PC NA - Ceyanna Ashton - Breton Vampire MagDK0 -
Magdalina✭✭✭✭✭
✭✭✭Tl;dr - several people applying 2+ taunts within 12 seconds causes overtaunting
Sounds about right, except for some reason I did indeed think it was 15 seconds and not 12. 0 -
camrenis✭✭
Yes we have two people taunting the Shade back and forth in execute, it's a mechanic in vet (i don't think you swap in normal?).Does your group have more than one person trying to taunt the Shade of Z'maja? Maybe with abilities or armor sets? Start with that issue.
Bosses don't always stick to the taunt target, they frequently do one or more 'random' attacks even though taunted. Then they come back. Don't remember specifics about Z'maja right now.
Problem is if you taunt while it's above 3 seconds, you risk proccing taunt immunity because you'll add an extra stack of taunt counter as I described above, assuming there's at least two people taunting of course.BXR_Lonestar wrote: »Honestly, I just use the fracture symbol to help time my taunts. When I see that debuff go down to around 4 seconds, I know I need to prepare to taunt, and it keeps me from overtaunting.Tl;dr - several people applying 2+ taunts within 12 seconds causes overtaunting Sounds about right, except for some reason I did indeed think it was 15 seconds and not 12.
I'm well aware this is how it is written on on various support websites, but I've clearly posted observational evidence above that shows this to be incorrect. I'll provide another example here - where three taunts have occurred, each about 10 seconds apart, and this still manages to proc taunt immunity.All I know that taunting by taunting 3+ times by more than one player within 12 seconds period will invoke overtaunt. And taunt won't be able to be refreshed till previous one runs out.
0