El Fuego
Member
- Joined
- Jun 18, 2013
- Messages
- 298
- Reaction score
- 2
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.
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.
