Pet Won't Attack Mobs Bug

[Mohee]

<p>All the Mobs in the basement area of Sebilis. All of them.</p><p>All the "Void" creatures and the Heroic ^^^ named on the Eye of El'Arad island in Stonebrunt Highlands</p><p>None of these mobs you can send your pet in to attack them. You recieve the message "You can not send your pet to attack the implied target"</p><p>Happens 100% of the time.</p><p>Please address and fix this issue as soon as possible. Thanks.</p><p>Anyone else that knows of NPC's/Zones/Spots in the game where this occurs, please reply to this post with that spot.</p><p><img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /></p>

[Adir]

<p>I've run into that bug in a few places.  It always seems to be either indoors or when the mob is inside something (a tent, a tunnel, etc.).  The only specific spot I can remember is in the Kylong Plains in the tunnel approaching Varis.  I know I've encountered it in quite a few other places, but that's the one I remember the exact location.</p>

[Mohee]

<p>*Note* All mobs on Eye of El'Arad island in Stonebrunt Highlands have this issue, not just the "void" creatures.</p>

[TSR-JoshuaM]

<p>Please /bug this as these are not client side issues that we can troubleshoot together.</p><p>Opening a follow up petition wouldn't be a bad idea for your own tracking as well.</p>

[Rarrum]

<p>I /bug'd it before after it got me killed a couple times a a while back. It happens when the mob is in a "tight place".  The beastlord pet will refuse to attack that mob and give you that message.  It doesn't matter where you or your pet stand, it's all about the mob's location.  In many cases you can pull the mob out of the tight area after which the pet will attack it normally again.</p><p>I've seen it in a lot of places while leveling up.  Butcherblock mountains for the quest that spawns tiny bugs really close to rocks was the first time I noticed it.  Then later the mining tunnels under Zek on the bottom floor were all that way too.</p>

[TSR-JoshuaM]

<p><cite>Rarrum wrote:</cite></p><blockquote><p>I /bug'd it before after it got me killed a couple times a a while back. It happens when the mob is in a "tight place".  The beastlord pet will refuse to attack that mob and give you that message.  It doesn't matter where you or your pet stand, it's all about the mob's location.  In many cases you can pull the mob out of the tight area after which the pet will attack it normally again.</p><p>I've seen it in a lot of places while leveling up.  Butcherblock mountains for the quest that spawns tiny bugs really close to rocks was the first time I noticed it.  Then later the mining tunnels under Zek on the bottom floor were all that way too.</p></blockquote><p>I have a good idea about what causes these situations so I'll do more testing as well and put in my own reports.</p>

[Therendil]

<p>I have seen this and the comment about the spiders under the rocks in BBM makes me realize that these may be mobs that also give a "You cannot see your target" error. I know the problem with the spiders happens on every one that spawns from a rock that is partly buried below the surface. It doesn't seem to take much of an obstruction to trigger the state. I could easily see it happening to mobs in corners, partly behind something, etc.</p><p>I'll try to remember to check both conditions if I see either one.</p>

[Mohee]

<p>The spots I listed are a little bit more weird. Like on the Eye of El'Arad island. The void creatures are constantly roaming around. No matter where they are, or which void creature it is, you can't send your pet in to attack. Even after you pull the mob, no matter your location, even if you standing right on top of the mob, you still  can't send the pet in to attack.</p><p>This is the same for the bottom part of Sebilis. Even the roaming mobs, you can't send in the pet. After engaging and moving the mob around, you still can't send it in.</p><p>Weird eh?</p>

[TSR-JoshuaM]

<p><cite>Therendil wrote:</cite></p><blockquote><p>I have seen this and the comment about the spiders under the rocks in BBM makes me realize that these may be mobs that also give a "You cannot see your target" error. I know the problem with the spiders happens on every one that spawns from a rock that is partly buried below the surface. It doesn't seem to take much of an obstruction to trigger the state. I could easily see it happening to mobs in corners, partly behind something, etc.</p><p>I'll try to remember to check both conditions if I see either one.</p></blockquote><p>The same creature your pet won't attack should also trigger You cannot see your target errors if my theory is correct.</p>

[MrWolfie]

<p><cite>TSR-JoshuaM wrote:</cite></p><blockquote><p><cite>Therendil wrote:</cite></p><blockquote><p>I have seen this and the comment about the spiders under the rocks in BBM makes me realize that these may be mobs that also give a "You cannot see your target" error. I know the problem with the spiders happens on every one that spawns from a rock that is partly buried below the surface. It doesn't seem to take much of an obstruction to trigger the state. I could easily see it happening to mobs in corners, partly behind something, etc.</p><p>I'll try to remember to check both conditions if I see either one.</p></blockquote><p>The same creature your pet won't attack should also trigger You cannot see your target errors if my theory is correct.</p></blockquote><p>Try the last named in Charasis: Vault of Eternal Sleep (Praetor of the Phylactery). I believe you can cast on him, but your pet won't attack.</p><h1></h1>

[Therendil]

<p>Well, things are never simple. <img src="/smilies/3b63d1616c5dfcf29f8a7a031aaa7cad.gif" border="0" alt="SMILEY" /> I have gotten the "cannot send you pet" error on occasion for a long time, and I have seen mobs that I believe are deliberately flagged that you cannot attack them first with your pet. Asphyxia in Lavastorm is a case in point. This critter sits fairly well in the open, but you cannot send a pet in to attack it. You have to go in there and whack it or pull it out to you.</p><p>We may be looking at two separate events here, once of which is a bug that is likely based on geometry.</p>

[TSR-JoshuaM]

<p>Playing around with it in testing and trying to isolate the occurrences.</p>