• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Questbot stuck "waiting"

    Discussion in 'Honorbuddy Support' started by d0t1q, Sep 26, 2016.

    1. d0t1q

      d0t1q Member

      Joined:
      Sep 15, 2010
      Messages:
      115
      Likes Received:
      0
      Trophy Points:
      16
      Currently running the quest bot with the profile 'Draenor Explorer'

      Its running a wait timer for no reason, I've cleared my cache according to this wiki page

      specific excerpt
      [21:14:52.257 D] Goal: WaitTimer-WaitTi: In Progress (no associated quest)
      Waiting for 10s
      [Ref: "Draenor Explorer ($Rev: 5668 $)" @line 189]
      [21:14:52.510 D] Activity: Wait time remaining... 9s of 10s.
      [21:14:53.360 D] Activity: Wait time remaining... 8s of 10s.
      [21:14:54.474 D] Activity: Wait time remaining... 7s of 10s.
      [21:14:55.324 D] Activity: Wait time remaining... 6s of 10s.
      [21:14:56.446 D] Activity: Wait time remaining... 5s of 10s.
      [21:14:57.270 D] Activity: Wait time remaining... 4s of 10s.
      [21:14:58.392 D] Activity: Wait time remaining... 3s of 10s.
      [21:14:59.521 D] Activity: Wait time remaining... 2s of 10s.
      [21:15:00.353 D] Activity: Wait time remaining... 1s of 10s.
      [21:15:01.499 D] Activity: Wait time remaining... 0s of 10s.
      [21:15:02.359 D] [WaitTimer-WaitTi(debug)] WaitTimer behavior complete.
      [21:15:02.377 D] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
      [21:15:02.389 D] [WaitTimer-WaitTi(debug)] Behavior completed in 10s
      [21:15:02.419 D] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
      [21:15:02.419 D] Goal: Nothing
      [21:15:02.421 N] [Discovering]: Gorgrond - Evermorn Springs.
      [21:15:02.434 D] Done with forced behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
      [21:15:02.434 D] Starting behavior Bots.Quest.QuestOrder.ForcedMoveTo.
      [21:15:02.434 D] Goal: Moving to Evermorn Springs [Ref: "MoveTo" @line 188]
      [21:15:02.467 D] Done with forced behavior Bots.Quest.QuestOrder.ForcedMoveTo.
      [21:15:02.467 D] Starting behavior Bots.Quest.QuestOrder.ForcedCodeBehavior.
      [21:15:02.469 D] Goal: WaitTimer-WaitTi: In Progress (no associated quest)
      Waiting for 10s
      [Ref: "Draenor Explorer ($Rev: 5668 $)" @line 189]
      [21:15:02.721 D] Activity: Wait time remaining... 9s of 10s.
      [21:15:03.570 D] Activity: Wait time remaining... 8s of 10s.
      [21:15:04.699 D] Activity: Wait time remaining... 7s of 10s.
      [21:15:05.532 D] Activity: Wait time remaining... 6s of 10s.
      [21:15:06.650 D] Activity: Wait time remaining... 5s of 10s.
      [21:15:07.498 D] Activity: Wait time remaining... 4s of 10s.
      [21:15:08.613 D] Activity: Wait time remaining... 3s of 10s.
      [21:15:09.722 D] Activity: Wait time remaining... 2s of 10s.
      [21:15:10.555 D] Activity: Wait time remaining... 1s of 10s.
      [21:15:11.717 D] Activity: Wait time remaining... 0s of 10s.
      [21:15:12.062 N] Stopping the bot!
      [21:15:12.063 Q] Bot stopping! Reason: User pressed the stop button
      [21:15:12.081 D] [WaitTimer-WaitTi(debug)] Behavior completed in 9s
      [21:15:12.083 D] Activity: Honorbuddy Stopped << At this point I stop the bot as it will just infinitely loop
       

      Attached Files:

    2. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      let it run so we can see the loop you are talking about plz
       
    3. d0t1q

      d0t1q Member

      Joined:
      Sep 15, 2010
      Messages:
      115
      Likes Received:
      0
      Trophy Points:
      16
      I mean I posted the loop, see line 518 and line 542 or line 3 and 27 in the post above
      I've attached another log file see lines 3389 through 3760 as the loop goes it sits waiting for a period of 10s for nothing, it will still attack during that time but otherwise wont do anything else. -- Note that this log is older as im not at home to test the bot
       

      Attached Files:

      Last edited: Sep 27, 2016
    4. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      i will check it with Echo
       
    5. Resedahb

      Resedahb Member

      Joined:
      Mar 21, 2013
      Messages:
      113
      Likes Received:
      0
      Trophy Points:
      16
      having the same issue
       
    6. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      open your own thread in that case
       
    7. d0t1q

      d0t1q Member

      Joined:
      Sep 15, 2010
      Messages:
      115
      Likes Received:
      0
      Trophy Points:
      16
      Thanks Tony let me know if you need more info or want me to reach out to echo
       
    8. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      i will let him know
       
    9. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,810
      Likes Received:
      631
      Trophy Points:
      113
      It looks like it's getting stuck while trying to discover Evermorn Springs.
      I believe the ID for this achievement is correct - so I'm assuming the XYZ position the bot is moving you to isn't hitting the 'discover' trigger.

      While it's looping, do you have this location discovered?
       
    10. d0t1q

      d0t1q Member

      Joined:
      Sep 15, 2010
      Messages:
      115
      Likes Received:
      0
      Trophy Points:
      16
      At the time the location wasnt discovered so youre probably right. I re-ran the bot today to see if I could replicate the issue, but I started from spires of arak rather than frostfall and it was able to discover the location.

      So it looks like if the bot was in/around the location "<5236.892, 1365.731, 87.63449>" it wouldn't be able to get the discover notice, the waypoint probably needs to be moved closer to the center of the trigger.

      Since I cant replicate it anymore now that the location is discovered might as well just ignore this, ill msg you directly if I notice the issue in the future.
       
    11. EchoTiger

      EchoTiger Official Profile and Singular Developer Staff Member Moderator

      Joined:
      Nov 28, 2012
      Messages:
      6,810
      Likes Received:
      631
      Trophy Points:
      113
      Alright.
      Profiles like this are a lower priority right now unfortunately since Legion has got my queue maxxed out right now -- but I'll go ahead and mark this down for future testing.

      Thanks for the report!
       

    Share This Page