• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic

    • Navigation failing for all hotspots

    Discussion in 'Rebornbuddy Support' started by themarketguy, Jul 7, 2015.

    Tags:
    Thread Status:
    Not open for further replies.
    1. themarketguy

      themarketguy New Member

      Joined:
      Jun 24, 2015
      Messages:
      117
      Likes Received:
      0
      Trophy Points:
      0
      As the subject states, navigation is failing for all hotspots when using the questing 1-50 profile for gridania 1-15.

      Was working fantastically earlier, then began failing maybe 30 minutes ago, approximately.

      Pastebin to the log:

      http://pastebin.com/jXKKBBps

      Last attempt shows:

      Code:
      [01:19:50.200 V] [Poi.Clear] Reason: Current behavior changed to MoveToTag: LineNumber: 2597, XYZ: <-141.4556, -3.154888, -166.775>, Name: Aetheryte, Distance: 3, UseMesh: True, IsDone: False, HighPriority: False, InCombat: False, QuestId: 0, StepId: 0, PostCombatDelay: 0, QuestName: null, IsDoneCache: False, Behavior: TreeSharp.PrioritySelector, .
[01:19:50.200 D] Replaced hook [ProfileOrderBehavior_Hook] 5df4d784-a9c3-4f7f-9691-5489e0cede49
[01:19:50.202 D] Requesting path on 130 from <-19.07914, 10, -60.44868> to <-141.4556, -3.154888, -166.775>
[01:19:50.642 D] No viable path from <-19.07914, 10, -60.44868> to <-141.4556, -3.154888, -166.775> in 00:00:00.4393032 ms
      I guess the short question is, are others experiencing issues with navigation? If not, what advice do you have? I've tried restarting the bot, though I see no reason why that would change anything. It APPEARS to be making a connection, just not getting paths back.
       
      themarketguy, Jul 7, 2015
      #1
    2. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,343
      Likes Received:
      383
      Trophy Points:
      83
      1)Always post a full log, you can post snippets as well but the full log is required.
      2)Any issues with a profile need to be posted in the profiles thread.
      3)You stopped and started the bot, something the profile doesn't handle very well, so its probably attempting to request a path and expecting you to be on a different map, hence the failure to find a path.
       
      mastahg, Jul 7, 2015
      #2
    Thread Status:
    Not open for further replies.

    Share This Page