Pet control box

[TalonEQ]

<DIV>Hello I'm a 54 Conjurer on Nektulos and was wonder if anyone is having my problem or did I just miss a update but sind Update 16 I have trouble when I click on the attack button on the control box for my pet that if I'm not facing (ie turned around) the mob or close enough to it my pet will not attack it. </DIV> <DIV> </DIV> <DIV> </DIV> <DIV>TIA</DIV> <DIV> </DIV> <DIV>Dadiib</DIV> <DIV> </DIV>

[Xecr]

I've noticed this has well. I've noticed that whenever my pet refuses to attack a target, I also can't cast a spell on it.I'm not sure exactly what the problem is, but it is a problem. I hope it gets fixed soon though. It's rather annoying.Xec

[sati]

<P>This problem I have noticed a few times, most of the times it happens the mob is often on a different ground level from myself (ie. up some steps) </P> <P>This can be fatal for myself when raiding because it means I have to run into AE range to be on same ground lev as the mob to make my pet attack, not a big deal but by time I done this and run back I dont have much time to get many spells off before its time to call pet back to avoid the AE</P>

[XtremSummo]

<DIV>I think Xalmat posted that this is due to changes that mean that you have to have line of sight to the mob for the pet to attack now. It's to stop certain behaviours like Invising through long twisting corridors to get a target lock on a mob, then going way back to a safe spot and using the pet to pull that mob and other such things. Unfortunately, all sorts of things can count as not having line of sight, like a chair being in the way or a very small step etc... so it kills all sorts of other valid behaviours too.</DIV> <DIV> </DIV> <DIV>Personally I think it's a really bad implementation.</DIV> <DIV> </DIV> <DIV>X</DIV>

[wullailhuit]

<span><blockquote><hr>XtremSummons wrote:<div>I think Xalmat posted that this is due to changes that mean that you have to have line of sight to the mob for the pet to attack now. It's to stop certain behaviours like Invising through long twisting corridors to get a target lock on a mob, then going way back to a safe spot and using the pet to pull that mob and other such things. Unfortunately, all sorts of things can count as not having line of sight, like a chair being in the way or a very small step etc... so it kills all sorts of other valid behaviours too.</div> <div> </div> <div>Personally I think it's a really bad implementation.</div> <div> </div> <div>X</div><hr></blockquote>From observing my pet , it appears to me that it't the <b>pets</b> LOS that dictates this as a few times I've been able to cast on a mob but the pet wouldn't attack till I moved him a bit. </span><div></div>

[GSOO]

it is that the pet can not find a suitable path to the mob. It is frustrating, but usually the easiest way is to  solve this issue is to move as it was posted, or pull the mob with a low damage nuke then the pet auto engages.

[Raybour]

I've heard what Wull said from others, and think that the pet's line of sight indeed may be what counts.  However, I think there are some significant bugs or issues with that system.  Here's what's happened to me: Sometimes, when I'm just out of aggro range of a mob and looking right at a mob with my pet behind or beside me, I'll hit pet attack and nothing happens, over and over.  Then, I cast a dot or DD spell, and it goes off.  Seems to happen when the mob is under a rock overhang or something of that nature, so it might be a line of sight issue, or might be that the system doesn't believe that the pet can engage in melee with the target.  When it has happened to me, though, I and my pet have always had an apparently clear line-of-sight to the mob.  Also happened to me once a bit ago when assisting a friend in one of the Grozmag instances in the Zek mines - pet wouldn't attack the group of mobs that were right in front of us.  Maybe there was a table in the way, I don't know, but it seemed a clear line of sight.  (That turned out to be serious, as I was trying to pull with the pet and could not - buddy attacked with his Warlock before I could engage, pulled major aggro, and we got owned.)  Dunno what's going on, but I find it extremely annoying and have "bugged" the problem. Anyone know if I'm dealing with the same issue, or something else? J Wellington Wells, L52 Conjurer, Steamfont Server <div></div>