What's new
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

"Can't navigate to our corpse. Trying the spirit healer instead!"

adi12

New Member
Joined
Aug 10, 2010
Messages
38
Reaction score
0
I've got a major problem.

I'm botting a 60 dk in outlands using Kicks 58-68 grindning profile.

When I die, the bot can't, no matter what, start walking to it's corpse.

All the log is saying is "Can't navigate to our corpse. Trying the spirit healer instead!", then it ress at the spirit healer. This give me the debuff, which the bot doesn't care about and it starts grinding and dies over and over again.

This has happened at ALL graveyards that i've came along.

WTF is the problem?
 
search a bit the forums and you will find out
 
This is a new feature of the new hb version.
If your corpse is not navigateable it will rezz at spirit healer.
I've run into the same problem and Apoc added the following code to the pull procedure of my CC, so it will at least rest until the buff is gone (marked bold). Ofc you can also just downgrade to an older version.

public override bool NeedRest
{
get
{
if (Me.HasAura("Resurrection Sickness")) return true;
if (!SSSettings.Instance.UseRest)
{
return false;
}

if (Me.HasAura("Food"))
{
return false;
}
if (SSSettings.Instance.UseRest)
{
if (Me.HealthPercent < SSSettings.Instance.restHealth)
{
if (!Me.IsSwimming && !Me.Combat)
{
return true;
}
}
}
return false;
}
}
 
I'm a lazy one and the fastest way is to search, and so I did. But I didnt find any good answer, so I took my time to post a new thread.

Is this a HB bug or am I doing something wrong? Is the Worgen class bugged? It's working fine with my other characters.
 
I'm a lazy one and the fastest way is to search, and so I did. But I didnt find any good answer, so I took my time to post a new thread.

Is this a HB bug or am I doing something wrong? Is the Worgen class bugged? It's working fine with my other characters.

they are working on it. will become an update they did tell me :p
 
This is a bug that was present in the previous build of Honorbuddy. Download the latest build (3895), this bug has been resolved.
 
Back
Top