Game restarting after trying to persuade

Question

Game restarting after trying to persuade

Opened this issue 4 years ago · 11 comments

The game is restarting after trying to persuade a familiar. It's happen when the new feature (auto persuade) is actived. The game acts faster then bot. Maybe any way to deactive AUTOBRIBE?

The logs:
[DungeonThread] AUTOBRIBE com.github.ilpersi.BHBot.BHBotLogger - Familiar encountered
[DungeonThread] WARN com.github.ilpersi.BHBot.BHBotLogger - Count for familiar squib is 0! Temporary removing it form the settings...
[DungeonThread] ERROR com.github.ilpersi.BHBot.BHBotLogger - Impossible to find the decline button, restarting...
[DungeonThread] WARN com.github.ilpersi.BHBot.BHBotLogger - Doing driver emergency restart...

Desktop:

OS: Windows 10 Home Single Language (x64)
Browser: Chromium
Version: BHBot v46.1 build on Wed Dec 31 21:00:00 GFT 1969 started.

settings.zip

Answer 1 · 2020-08-09T16:56:02.000Z

Try to comment out the familiars settings and to set persuasionLevel to 0. This should completely disable the auto-bribing and the auto-persuading features.

Answer 2 · 2020-08-09T21:16:13.000Z

I commented the familiars settings and set the persuasionLevel to 0 and the bot continued restarting the game :(

It looked like this:

persuasionLevel 0
#bribeLevel 0
#familiars squib 0
#familiarScreenshot 1
#contributeFamiliars 1

I also tried to comment on persuasionLevel, but got the same result. Is there any other setting for commenting?

settings.ini:
settings.zip

Answer 3 · 2020-08-12T12:23:46.000Z

I am able to reproduce this and I am still thinking about the best way to fix this.

Probably, as the feature is built in the game, we do not need it anymore so more code refactoring is required. If you want to run the bot I suggest disabling the game feature while I try to find a better solution.

Answer 4 · 2020-08-12T14:26:55.000Z

Yes, I have currently disabled the game feature and am using the bot's AUTOBRIBE, but this makes a dungeon rush slower.

I'll be waiting for news. Thank you very much for your attention! <3 :)

Answer 5 · 2020-08-12T18:48:51.000Z

I would prefer if we keep this open. It helps me remind things to do and it may be useful for other people having the same issue.

Answer 6 · 2020-08-23T15:31:07.000Z

Is any possibility to add a choice switch in front of all above the capture logic procedure to decide bot going to handle the capture or not ?
If chose let game build-in handling, bot complete ignore the capture window.
Otherwise, user can use now bot capture process but must close built-in option first.

Answer 7 · 2020-09-09T19:56:24.000Z

@tengen-toppa as one of the bot features is overlapping with a built-in one I am going to remove the unnecessary function from the bot otherwise it may be misleading for users.

Answer 8 · 2020-09-10T06:50:05.000Z

@tengen-toppa as one of the bot features is overlapping with a built-in one I am going to remove the unnecessary function from the bot otherwise it may be misleading for users.

Appreciate your hard work on BH bot.

Answer 9 · 2020-10-27T22:11:44.000Z

@igoramd I just released the new v46.4: it does not solve this issue, but it has many improvements and optimizations for encounter management that now is much faster than it used to be.

Check it out. 👍🏻

Answer 10 · 2020-10-28T14:02:10.000Z

Hey, it's incredibly faster now! It was really good.

I will have no more problems with that. Should I close this now?

Answer 11 · 2020-10-28T15:51:42.000Z

I still need to make the bot work with built-in settings so l let's keep this open even if I consider it a low priority. :)