Hey mate. It's because some private servers handle pet death differently I have tried to fix it for as many different servers and different methods they use as I can over time.
It has been an issue since the beginning of private servers.
Hmm
The thing is. It's set to check the range between you and the target. if it's too close it should move out. But for some odd reasons, it seems that the range checker is off. Usually, it's because of the target size. But apparently that didn't change anything.
So if your char is in the deadzone and the pet gets aggro it doesn't move away? Because that should be handeled by the backtracking code. 😮
HOWEVER the backtracking code is actually checking for a safe spot to stand. If it can't find any it won't move.
Perhaps for some odd reason that code is severely slowed down or somewhy canceled. It used to just walk backwards. But that often resulted in backpedeling into other mobs. etc. which is why i changed to look 360 degrees around itself to find a safe spot to run to. This is actually one of the cool features of vanilla version vs TBC version. But seems to be bugging for you.
I will see if I can revise the code for you and remove the check safe spot. However it does come with the caveat that it might run into danger and pull even more.
That is sooo weird.
I am not sure how to fix it though. As I am using the distance checker made by wrobot. And It's something I have not ever heard of before.
Apparently there is some incompatibility with the server you are playing on.
Pm me your email that you used to buy it, and I will refund you.
Now I think I understand what you mean by deadzone.
In advanced settings of wrobot there should be a button to change something with hitbox sizes.
I think the hitbox sizes are different on the server you are playing than wrobot thinks. I am absoultely positive there is a setting in there to change how it calculates the hit-boxes I just can't remember what it is called.
That sounds really weird. Is this a cave that is not on all other servers? Perhaps it's not meshed by wrobot? Movement control is not controlled by the fightclass. But by wrobot.
The only moment my fightclass overrides the movement is to move away from the mob if it gets in melee range and you do not have aggro on the mob.
Otherwise it's 100% cotrolled by the bot.
Edit: Try turning off backtracking or change the combat range see if it makes any difference.
Personally I do a ton of my 'heavy' checks in tasks that aren't looped. But rather fires once every loop over my overall rotation. Do care about how many threads you open though especially if you plan to keep more than one on a loop.