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

Navigation issue?

Status
Not open for further replies.

Juggernaut

New Member
Joined
Nov 19, 2011
Messages
21
Reaction score
0
Hello,

I am using the most recent DB with updated plugins and when running Bounties (All) to level my Monk the bot keeps transporting itself back to the same way-point without exploring the area.

When trying to run just Act 4 bounties I get the following message "Bot thread did not end within 5 seconds" and the bot stops even when I leave and join another game. Same issue in Act 5 as well. Also will get a strange message in red across the game screen something like " To close to waypoint to transport"

The first log file shows the bot just transporting my monk back to the same spot over and over again.

I am sure its something small I overlooked so any help would be greatly appreciated.
 

Attachments

Last edited:
Hi Tony, I updated everything and continue to have issues like before. I have it in this log file hopefully. The message coming across the screen is "Unable to teleport because the target waypoint is too close" I have attached a new log to hopefully show the problem.
 

Attachments

Yes this is an in-game message when using DB, now that I have reached 70 I get "Bot thread did not end within 5 seconds in DB" so its both bounties and joining nephalem i ma having issues with. I am sure its something simple I just cant figure it out. log attached
 

Attachments

Try a fresh install of everything. As in fully delete the whole folder including everything inside.

Fresh install and try that out with all updated Trinity & Adventurer. Usually that solves like 99% of the problems I see on here lol.
 
Hello uljimah I have done that 3 times already with the same issues. Even updated everything before I even started DB up and no luck.
 
use Adventurer's default profiles instead,sound like a profile issue
 
Please close this thread I figured out the issue. Profiles I was using did not get updated when I updated DB so it was using old default profiles. Sorry about this, but I did say it was most likely a small issue. :)
 
Status
Not open for further replies.
Back
Top