• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Questbot takes a long time to "stop" the bot when "Stop" button pressed

    Discussion in 'Honorbuddy Support' started by El Fuego, Dec 17, 2013.

    1. El Fuego

      El Fuego Member

      Joined:
      Jun 18, 2013
      Messages:
      298
      Likes Received:
      2
      Trophy Points:
      18
      This issue cropped up in 708/709 and continues in 711.

      When the bot is questing and the "Stop" button is pressed, massive FPS spikes start happening while the bot continues to try to do what it was doing. HB becomes non-responsive where no other buttons (Class Config, Plugins, etc) can be clicked. Often this goes on for 1-3 minutes. Eventually the Bot finally stops, HB becomes responsive again, and the FPS spikes stop.

      This only seems to happen with the Questbot. Combat Bot and Dungonbuddy do not seem to have this issue in my experience. I have experienced the issue on multiple PC's with multiple attempts to install fresh copies of HB.

      In the below example, you can see where the user clicked the stop button and where it took a while (15 seconds) to actually stop the bot with multiple "Stucks" while the bot was stuttering and hanging before it actually shut down. This is generally pretty quick in comparison to the 1 minute plus that it sometimes takes to shutdown. Even still 15 seconds is too long.
      There are times when I use LogMeOut and the plugin hearths, sends the stop, and then the bot makes it all the way to the Flightpath and takes off trying to get back to the questing location, before the "shutdown" actually happens.


      [23:53:41.099 N] Stopping the bot!
      [23:53:41.100 Q] Bot stopped! Reason: User pressed the stop button
      ...
      [23:53:54.703 D] Activity: Honorbuddy Stopped

      [Logfile]

      View attachment 320 2013-12-17 15.50.txt

      You can imagine that if someone started talking to me and I was trying to stop the bot, that this "Stuck" handler behavior would look pretty strange. Or if I just ran off questing in the middle of the conversation because the bot wouldn't stop for 30 seconds. It could easily be an alert that I was botting.
       
    2. CodenameG

      CodenameG New Member

      Joined:
      Jan 15, 2010
      Messages:
      38,369
      Likes Received:
      231
      Trophy Points:
      0
      get rid of your anti-drown and drink potion plugins, also remove your wow addons to see if that helps.
       
    3. El Fuego

      El Fuego Member

      Joined:
      Jun 18, 2013
      Messages:
      298
      Likes Received:
      2
      Trophy Points:
      18
      I will try that, however I can tell you that I've always used those same plugins as well as almost all of my addons and never had this problem until recently. Something changed in HB.
       
    4. Slite62

      Slite62 Member

      Joined:
      Oct 16, 2013
      Messages:
      494
      Likes Received:
      2
      Trophy Points:
      18
      Ummm... if it is Anti-drown and DrinkPotions that might be causing this issue... why are they still suplied as core plugins? And instead of saying "get rid of them", why not fix them?
       
    5. Beringtom

      Beringtom Member

      Joined:
      Mar 7, 2010
      Messages:
      278
      Likes Received:
      0
      Trophy Points:
      16
      "get rid of them" is used as a way to suggest that you disable them, leaving only the most needed things for HB and wow to run.
      Troubleshooting 101.
       
    6. CodenameG

      CodenameG New Member

      Joined:
      Jan 15, 2010
      Messages:
      38,369
      Likes Received:
      231
      Trophy Points:
      0
      ^^This. if you guys need help open your own threads, NEVER post in someone elses thread.
       
    7. El Fuego

      El Fuego Member

      Joined:
      Jun 18, 2013
      Messages:
      298
      Likes Received:
      2
      Trophy Points:
      18
      After trying various things one at a time like disabling plugins, and addons... I found that even with all plugins and addons "Disabled" the bot still takes 5-10 seconds to "Stop". The only way it was (close to) instant, was if the Addons folder (WoW) and the Plugins folder (HB) were completely empty, not just disabled.

      That lead me to examine the Kicks profile I was using.

      I've discovered that it's not an HB component that is causing the issue. It's the Kick's profile itself. It appears that each time the "Stop" button is pressed, the profile wants to take an inventory of the WoW client's UI Addons, as well as the HB Plugin's being used. While I'm sure this is useful information for Kicks and Apoc to troubleshoot, it is causing problems with the bot shutdown. Especially if there are many addons/plugins to inventory.

      Once I switched to Cava's profiles, the issue is gone and the "Stop" button works instantly.

      I'll post this in Kick's Thread. Thanks for the Help!
       

    Share This Page