• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • multiple errors

    Discussion in 'Hearthbuddy Support' started by stewiethecat, Mar 12, 2016.

    1. stewiethecat

      stewiethecat Member

      Joined:
      Feb 4, 2011
      Messages:
      454
      Likes Received:
      0
      Trophy Points:
      16
      Each time I start the bot using the quest plugin, I have to re cache custom decks over again without making any custom deck changes. It doesn't recognize that I have a the deck available for the quest.

      Also bot stops randomly while using quest plugin.
       

      Attached Files:

    2. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      2016-03-12 09:54:34,789 [22] ERROR CustomLogger (null) - [Quest] Now stopping the bot, because there are no quests we can complete with the current custom decks since [OnlyUseCustomDecks] is enabled.
       
    3. stewiethecat

      stewiethecat Member

      Joined:
      Feb 4, 2011
      Messages:
      454
      Likes Received:
      0
      Trophy Points:
      16
      I know that is the odd thing, I have cached custom decks that have been scanned and I have the quest available. But at times it will still give the error causing the bot to stop because it doesn't recognize that I have the proper deck available. After a restart everything works okay for a while then the bot stops after the quests have completed. I don't have "Stop after all quests are completed" checked. Shouldn't HSB continue to farm even after the quests are completed? Maybe I am mistaken..

      It's something I can work around but more of an annoyance to have to check on the bot every 10 minutes or so to see if it has stopped while the questing plugin is enabled. Not a big deal
       
    4. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      we will check it
       
    5. stewiethecat

      stewiethecat Member

      Joined:
      Feb 4, 2011
      Messages:
      454
      Likes Received:
      0
      Trophy Points:
      16
      Thank you Tony
       
    6. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,252
      Likes Received:
      290
      Trophy Points:
      83
      I'm going to re-explain how the bot is setup so you can see if you're seeing intended behavior or actually seeing a problem.

      Each time you startup the bot, it must cache your custom decks (users have to press that button to make it do it). The reason for this is because you can modify your deck and change things around, and there's no way for the bot to know what cards are in your deck or if the cached deck data is still valid or not. We stuck with that design to avoid issues resulting in things breaking because users changed their decks or names, even though it is a bit inconvenient at times. This is just a side effect of how the game worked, and the best way to handle it was recaching decks each bot startup.

      The option OnlyUseCustomDecks is when you want to only use your custom decks, but you also have a custom deck for each class, so the bot has something to choose from. Otherwise, by default, it will use your basic decks to grind out quests with. because basic decks are good enough at the lower ranks (as in rank 20+) with the AI to do finish your quests. HSB is more or less a gold farming bot, which takes away the tedium of grinding gold to buy more packs or adventures, but some people use it for ranked play and climbing the ladder.

      Anyways, after you complete a game when doing quests, the bot will re-cache your current quests by going to the quest log to make sure it still has the current data. This is because you can re-roll a quest, so once again, the bot tries to keep the most up-to-date info rather than trying to assume the cached data it has is still valid.

      Now for your logs, the first error, "Unhandled presence status detected: QUESTLOG." is an unfortunate thing that happens in this game, in which user intervention is required. There are times where the client/server state gets out of sync, and the bot doesn't know what to do because it requires the client and server to be in sync. The best way to fix that is to restart your client and bnet, or manually enter a different game mode, then back out and try again.

      The second error, "[Quest] Now stopping the bot, because there are no quests we can complete with the current custom decks since [OnlyUseCustomDecks] is enabled." was because your bot didn't re-cache quests the second time you started it after the first error, so it didn't know about your custom decks anymore. If you trigger a deck recache it should work again.

      Hopefully that clears up your issues, but if you still don't understand please let us know. :)
       
    7. stewiethecat

      stewiethecat Member

      Joined:
      Feb 4, 2011
      Messages:
      454
      Likes Received:
      0
      Trophy Points:
      16
      Not a problem, Thanks for the rundown. Everything seems to be working as intended besides "Unhandled presence status detected: QUESTLOG." Only happens every once in a while.
       

    Share This Page