I thought this would be resolved with the recent fixes to the Pilgrim set, but apparently not.
I am still seeing instances where I finish with a set of mobs, and my companion will take off and attack the next closest set of mobs, none of which should be in agro range. I've tested it just to verify proximity might set them off, but it doesn't. You have to have been in combat, and killed the last mob - before the companion will go off in search of more enemies to fight. It also doesn't happen consistently.
I've seen it with two of my characters - several times in Omu, and a couple times in Dwarven valley. The character in Omu has a chultan tiger summoned, whereas the other character in Dwarven valley has an Air Archon. Both characters have the Pilgrim set in common.
1
Comments
Sometimes I have to grind through 3 or 4 mob packs until my companion finally calms down.
Lillend and pilgrim set
What I do have is Chultan crafted weapons, or other Chultan equipment. So it seems to be a wider issue with either all the Chult stuff or a wider issue with something else entirely - companion AI perhaps? - that just happened to correspond with a lot of people getting the Pilgrim weapons.
Joking aside I feel your pain, when I was much lower iL this would lead to insta death in the Batiri village quite often
Blood Magic (RELEASED) - NW-DUU2P7HCO
Children of the Fey (RELEASED) - NW-DKSSAPFPF
Buried Under Blacklake (WIP) - NW-DEDV2PAEP
The Redcap Rebels (WIP) - NW-DO23AFHFH
My Foundry playthrough channel: https://www.youtube.com/user/Ruskaga/featured
Sure out in zones I dont care because I can take down the adds no problem but in tong it becomes an issue because well someone in group may die and it will be my fault due to my stupid companion.
So devs stated it was fixed but I know it wasnt.
These things should be looked into.
Here is another example. Assume your in cradle and at the boss and someone in party trying to re summon their companion but hey your companion decided to hit the boss and start the fight.
Oh another example tong orcus fight when the companion starts the fight and people die at the start from the cleave.
Anyways I can go on this all day long.
The point is a companion should not decide when to fight.
In fact it should stay passive until something hits me.
There appears to be two issues, the unsummoning/dying/randomly disappearing issue and the aggro issue when we talk about companions post-Omu. I have no idea about the unsummoning but I'm wondering if the increase in our companions willingness to go out and "make friends" have anything to do with aggro being fiddled with in the Omu expansion. Because about the first thing I noticed in Shoshenstar River upon logging in on launch day was that the dinos there now had normal aggro range rather than their very excessive one prior to Omu expansion. And now I'm just wondering if fiddeling with that aggro somehow, in some weird fashion and thanks to the fact that this game has spaghetti code - as do all mmos - have affected our companions' aggro in reverse?
Makos on my wizard (who has the Chult weapon set) is especially bad, with his meteors apparently having a 300-foot aggro radius. But after Omu expansion, even when he's using his regular fireball, he'll just run at some random mob 40-60 feet away and attack them as well...even if I'm busy fighting a different mob... (Normally, it's just his meteor that will do this.) On the same character, the Will-O'-Wisp has the same issue as all the other companions.
My paladin doesn't even have artifact or relic weapons atm, is a 9k lvl 70, and while I was tomfooling around in Ebon Downs (nowhere near the dragon), his Stalwart Lion companion would randomly chase down and attack zombie mobs. I mean, thanks for the entertainment, but there's absolutely zero reason for a comp on a lvl 70 character to go after mobs meant for level 31-35 characters.
I've also seen a lvl 69 rogue, with no fancy weapons, whose dog companion chased after mobs in Fiery Pit.
Haven't had issue with the Lillend on my cleric.
Would be nice if companions were set to attack only if there was something attacking you or if it was within 10 feet of you - and nothing else. And if all of their attacks were hard-locked into this, so that there would, say, be no more indiscriminate meteoring of enemies nearly outside of visual range on a mostly flat map...