• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic

    • Order Bot problem: No viable path from XY. Finished checking gear in ...

    Discussion in 'Rebornbuddy Support' started by exodia, Oct 5, 2016.

    1. exodia

      exodia Member

      Joined:
      Nov 12, 2012
      Messages:
      148
      Likes Received:
      3
      Trophy Points:
      18
      exodia, Oct 5, 2016
      #1
    2. mastahg

      mastahg Administrator Staff Member

      Joined:
      Feb 27, 2011
      Messages:
      5,343
      Likes Received:
      383
      Trophy Points:
      83

      This is a known issue with profiles where if you start them where they don't expect, it can't handle that. Looks like this profile wants you to talk to Baderon in the upper section of limsa lominsa. If you manually move there and then start it should work. A better fix is currently being worked on, but it won't ready for the immediate future.
       
      mastahg, Oct 5, 2016
      #2
      exodia likes this.
    3. exodia

      exodia Member

      Joined:
      Nov 12, 2012
      Messages:
      148
      Likes Received:
      3
      Trophy Points:
      18
      Okay, thanks for your reply! How did you find out where this location is? through the developer console? because i don't want to ask you everytime i get this error :D so i want to look it up myself.
       
      exodia, Oct 6, 2016
      #3
    4. y2krazy

      y2krazy Community Developer

      Joined:
      Jun 21, 2011
      Messages:
      2,803
      Likes Received:
      70
      Trophy Points:
      48
      Code:
      [16:21:15.125 V] [Poi.Clear] Reason: Current behavior changed to [COLOR="#FF0000"]MoveToTag[/COLOR]: [COLOR="#FF0000"]XYZ: <20.27917, 40.19993, -6.118958>[/COLOR], [COLOR="#FF0000"]Name: Baderon[/COLOR], Distance: 3, UseMesh: True, IsDone: False, HighPriority: False, [COLOR="#FF0000"]LineNumber: 1836[/COLOR], InCombat: False, QuestId: 0, StepId: 0, PostCombatDelay: 0, QuestName: null, IsDoneCache: False, Behavior: TreeSharp.PrioritySelector, .
[16:21:15.125 D] Replaced hook [ProfileOrderBehavior_Hook] 975910fc-3401-4105-b581-92b539a6083b
[16:21:15.142 D] Requesting path on 148 from <14.1653, -1.187969, 28.63723> to <20.27917, 40.19993, -6.118958>
[16:21:15.705 D] [COLOR="#FF0000"]No viable path from <14.1653, -1.187969, 28.63723> to <20.27917, 40.19993, -6.118958> in 00:00:00.5632367 ms[/COLOR]
      ;)
       
      y2krazy, Oct 6, 2016
      #4
      exodia likes this.
    5. exodia

      exodia Member

      Joined:
      Nov 12, 2012
      Messages:
      148
      Likes Received:
      3
      Trophy Points:
      18
      Thanks! :)
       
      exodia, Oct 6, 2016
      #5
      y2krazy likes this.
    6. exodia

      exodia Member

      Joined:
      Nov 12, 2012
      Messages:
      148
      Likes Received:
      3
      Trophy Points:
      18
      sorry for the gravedigging.
      i want to reactivate my subscription, but only if the questing works. is the "No viable path error" still there or can i hit start and watch the bot doing the quests?
       
      exodia, Dec 5, 2016
      #6
    7. y2krazy

      y2krazy Community Developer

      Joined:
      Jun 21, 2011
      Messages:
      2,803
      Likes Received:
      70
      Trophy Points:
      48
      I responded to another post a minute ago regarding this. No viable path errors simply mean you are currently in the wrong zone for what the profile is trying to do (in another zone). Moving to the proper zone for the quest behavior and hitting Start will fix the error. Once the profiles have been updated on my SVN, you will not get this error any longer.
       
      y2krazy, Dec 5, 2016
      #7
    8. exodia

      exodia Member

      Joined:
      Nov 12, 2012
      Messages:
      148
      Likes Received:
      3
      Trophy Points:
      18
      okay, thank you for your response. i will wait for the update of the profiles :)
       
      exodia, Dec 6, 2016
      #8

    Share This Page