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

Mattrix

New Member
Joined
Sep 8, 2015
Messages
26
Reaction score
0
hello ppl i keep having this in DB and my char die after 5 / 6 secs it wont moove , it wont teleport to town after colpleting grfits , it wont speek to urushi at the end to lvl up gems

this is the message it keeps repeeting

Trinity 2.13.35] NavServer Issue: MainGridProvider is empty, unable to calculate avoidance position
[Trinity 2.13.35] Waiting for Navigation Server...

anione knows a solution for this problem, or a etimated time +/- for a solution ty all in advance
 
The not teleporting to town issue a number of people (myself included) had after the last update. It was a Adventurer issue that was quickly patched. Assuming you're using it make sure it's up to date (1.2.0.118) from here

Hope that fixes your problems, it did for me. :)

As for the Navigation issue. It was apparently fixed but I'm still getting the errors on both of my bots. It doesn't seem to be preventing them from functioning though.
 
The not teleporting to town issue a number of people (myself included) had after the last update. It was a Adventurer issue that was quickly patched. Assuming you're using it make sure it's up to date (1.2.0.118) from here

Hope that fixes your problems, it did for me. :)

As for the Navigation issue. It was apparently fixed but I'm still getting the errors on both of my bots. It doesn't seem to be preventing them from functioning though.

Well, that would explain it. Thanks for this post.
 
Well, that would explain it. Thanks for this post.

NP, it's possible the Navigation issue is slowing things down a little by the way. Watching my bot completing GRs about a minute slower then usual, only just noticed now. :)
 
isent it possible that blizz has patched DB , using a antibot or something since they banned a bunch of ppl including gabinater wudijo etc etc for using macros and bots
 
The not teleporting to town issue a number of people (myself included) had after the last update. It was a Adventurer issue that was quickly patched. Assuming you're using it make sure it's up to date (1.2.0.118) from here

Hope that fixes your problems, it did for me. :)


As for the Navigation issue. It was apparently fixed but I'm still getting the errors on both of my bots. It doesn't seem to be preventing them from functioning though.


ty i will try it but wen i started DB it has updated himself, will tru to manual update it .
 
isent it possible that blizz has patched DB , using a antibot or something since they banned a bunch of ppl including gabinater wudijo etc etc for using macros and bots

As I understand it they were banned for the hellfire exploit, while there's always a risk I don't think it's in Blizzards best interests to put much effort into D3 bot banning since we're not really hurting anyone. :)
 
As I understand it they were banned for the hellfire exploit, while there's always a risk I don't think it's in Blizzards best interests to put much effort into D3 bot banning since we're not really hurting anyone. :)

well it was just an ideia since this as just start after the patch
 
hello ppl i keep having this in DB and my char die after 5 / 6 secs it wont moove , it wont teleport to town after colpleting grfits , it wont speek to urushi at the end to lvl up gems

this is the message it keeps repeeting

Trinity 2.13.35] NavServer Issue: MainGridProvider is empty, unable to calculate avoidance position
[Trinity 2.13.35] Waiting for Navigation Server...

anione knows a solution for this problem, or a etimated time +/- for a solution ty all in advance


http://www.thebuddyforum.com/honorb...-how-attach-your-hb-db-log-file-pictures.html
 
still receiving the error that folows

[Trinity 2.13.35] Waiting for Navigation Server...
[Trinity 2.13.35] NavServer Issue: We're not moving because SearchGridProvider is empty, nothing we can do!


here is the log file maybe it will help.

View attachment 232 2015-09-23 01.51.txt
 
So are they doing it early? Because 7AM UTC on september 25th isn't for another 8 hours
 
its already done and we are polishing things right now
 
Back
Top