So, I've been playing pet sorc for a long time. When I take my pets into a dungeon or something, the Twilight Matriach will usually be the first one to aggro the boss, but as soon as the Volatile Familiar hits the boss, aggro shifts to the Familiar and remains on him through the fight as long as the Familiar stays alive. At least, that's how it used to work before Homestead. Now, doing the exact same fights (take Infernal Guardian from CoA1 for example), the boss just completely ignores the Familiar and goes straight for me as soon as I hit him. Since this wasn't a nerf to pet aggro spelled oit in the patch notes, I'm inclined to call it a bug. I reported it, but wanted to let others in the ESO community check it out for themselves. If you find yourself having a similar experience, please bug report it and comment here.
Because Twilight is a better healer then dps pet and because the Familiar's pulses are amazingly strong, stronger than Liquid Lightning in terms of dps when attacking a target with Daedric Prey on.
I will say that the Familair did hold aggro for me today against an Air Atronach at a Craglorn Focus Point. There were a couple times he didn't, but one time for sure he did. So, findings so far have not been 100% conclusive.
RavenSworn wrote: »it might have been a ninja change. My clannfear has been holding aggro as usual. If the familiar is not, then i think they might have changed the pet mechanics abit since the familiar is not meant to be a tank.
SmalltalkJava wrote: »I submitted a bug report on the forums. https://forums.elderscrollsonline.com/en/discussion/320781/volatile-familiar-is-not-holding-agro/p1
Ok. I did some controlled testing in CoA1 today. It appears that the problem is with the Familiar TAKING aggro from me, not establishing aggro himself. Example, the fire dude at the top of the south platform. I sent the Familair in first, let him actually whack the guy with his normal melee attack, then began to fight. I was not using the Twilight at all during today's test, so dunno if she would have stolen aggro from him. The Familiar held aggro through the fight. Then I reset the fight before killing him and this time I just went right into attacking him. Normally this is what I would do pre-Homestead and as soon as the Familiar would hit him, he'd forget about me. NOT THIS TIME. Boss kept attacking me and ignored the Familiar. So I just stopped attacking and kept shields up. 5-10 seconds later, the boss switches to fighting the Familiar and stayed on him after I resumed attacking.
In trash pulls, the Familiar was only aggroing the target he was melee attacking. His damage pulses do not count as aggro for him. If I sent him to tap every mob, they would stop attacking me and start attacking him. I believe that pre-Homestead, sending a pet in to fight a pack of mobs, they all would aggro him. Now, just the one he hits aggros him and the others come to me.
So, until ZOS confirms this is intentional behavior or fixes it, SEND YOUR FAMILIAR IN FIRST AND WAIT FOR HIM TO ENGAGE BEFORE ATTACKING if you care about him holding aggro.
@ZOS_GinaBruno Any input would be great.
I encourage others to test with the Clannfear and Twilight in the same way and post your results here.
Ok. I did some controlled testing in CoA1 today. It appears that the problem is with the Familiar TAKING aggro from me, not establishing aggro himself. Example, the fire dude at the top of the south platform. I sent the Familair in first, let him actually whack the guy with his normal melee attack, then began to fight. I was not using the Twilight at all during today's test, so dunno if she would have stolen aggro from him. The Familiar held aggro through the fight. Then I reset the fight before killing him and this time I just went right into attacking him. Normally this is what I would do pre-Homestead and as soon as the Familiar would hit him, he'd forget about me. NOT THIS TIME. Boss kept attacking me and ignored the Familiar. So I just stopped attacking and kept shields up. 5-10 seconds later, the boss switches to fighting the Familiar and stayed on him after I resumed attacking.
In trash pulls, the Familiar was only aggroing the target he was melee attacking. His damage pulses do not count as aggro for him. If I sent him to tap every mob, they would stop attacking me and start attacking him. I believe that pre-Homestead, sending a pet in to fight a pack of mobs, they all would aggro him. Now, just the one he hits aggros him and the others come to me.
So, until ZOS confirms this is intentional behavior or fixes it, SEND YOUR FAMILIAR IN FIRST AND WAIT FOR HIM TO ENGAGE BEFORE ATTACKING if you care about him holding aggro.
@ZOS_GinaBruno Any input would be great.
I encourage others to test with the Clannfear and Twilight in the same way and post your results here.
Ok. I did some controlled testing in CoA1 today. It appears that the problem is with the Familiar TAKING aggro from me, not establishing aggro himself. Example, the fire dude at the top of the south platform. I sent the Familair in first, let him actually whack the guy with his normal melee attack, then began to fight. I was not using the Twilight at all during today's test, so dunno if she would have stolen aggro from him. The Familiar held aggro through the fight. Then I reset the fight before killing him and this time I just went right into attacking him. Normally this is what I would do pre-Homestead and as soon as the Familiar would hit him, he'd forget about me. NOT THIS TIME. Boss kept attacking me and ignored the Familiar. So I just stopped attacking and kept shields up. 5-10 seconds later, the boss switches to fighting the Familiar and stayed on him after I resumed attacking.
In trash pulls, the Familiar was only aggroing the target he was melee attacking. His damage pulses do not count as aggro for him. If I sent him to tap every mob, they would stop attacking me and start attacking him. I believe that pre-Homestead, sending a pet in to fight a pack of mobs, they all would aggro him. Now, just the one he hits aggros him and the others come to me.
So, until ZOS confirms this is intentional behavior or fixes it, SEND YOUR FAMILIAR IN FIRST AND WAIT FOR HIM TO ENGAGE BEFORE ATTACKING if you care about him holding aggro.
@ZOS_GinaBruno Any input would be great.
I encourage others to test with the Clannfear and Twilight in the same way and post your results here.
This matches the behavior i was seeing today in spindleclutch and crypt of hearts. the pulses do not create aggro at all as far as i can tell and a lot more bosses stayed on me over and over again which was drastically different than soloing them before homestead. And you are correct it seemed the twilight gathered aggro more often than the scampi.
May have to rethink the AoE scamp option if this is confirmed and going to stay...
BlackSparrow wrote: »Yep, Even if you send them in manually, the Twilight gets aggro first, because its long-range attack hits first.
What's worse, I was fighting some 3-enemy groups today, and waited until the familiar had hit each mob at least once before using my standard AoE opener. Immediately after using the AoE, any bad guy who was not currently being attacked by the pets turned and started coming at me. This is very different from what it was pre-patch.
This seriously messes up pet play. They gave us a patch buffing them, only to make them stop doing what we were using them for in the first place.
Can anyone confirm whether Clannfear has functionally changed, or is it just the Volatile Familiar?
So, I've been playing pet sorc for a long time. When I take my pets into a dungeon or something, the Twilight Matriach will usually be the first one to aggro the boss, but as soon as the Volatile Familiar hits the boss, aggro shifts to the Familiar and remains on him through the fight as long as the Familiar stays alive. At least, that's how it used to work before Homestead. Now, doing the exact same fights (take Infernal Guardian from CoA1 for example), the boss just completely ignores the Familiar and goes straight for me as soon as I hit him. Since this wasn't a nerf to pet aggro spelled oit in the patch notes, I'm inclined to call it a bug. I reported it, but wanted to let others in the ESO community check it out for themselves. If you find yourself having a similar experience, please bug report it and comment here.