• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Concede for no reason after latest update

    Discussion in 'Hearthbuddy Forum' started by aquileolus, Jan 16, 2016.

    1. aquileolus

      aquileolus New Member

      Joined:
      Jan 16, 2016
      Messages:
      2
      Likes Received:
      0
      Trophy Points:
      0
      I used hearthbuddy to gain daily 100 golds everyday for several months, it worked well for most time (90%+ winrate)
      But after the latest update, I found the winrate become only 50%, and when I watched it play, I find out that some time when it was able to kill opponent, it just concede and show "Lethal detected. Concede..."
      and sometime with a error:
      System.ArgumentOutOfRangeException:
      at System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument argument, ExceptionResource resource)
      at System.Collections.Generic.List`1.get_Item(Int32 index)
      at HREngine.Bots.MiniSimulator.startEnemyTurnSimThread(List`1 source, Int32 startIndex, Int32 endIndex) c:\Desktop\Hearthbuddy 0.3.1120.208\Routines\DefaultRoutine\Silverfish\ai\MiniSimulator.cs:line 226

      and many more red lines

      so how can I fix it or how can I turn off the auto concede function?
       
    2. tpboi

      tpboi Member

      Joined:
      Mar 27, 2014
      Messages:
      44
      Likes Received:
      0
      Trophy Points:
      6
      the client is broken now...i dropped from tank 5 to 15 after patch.
       
    3. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,252
      Likes Received:
      290
      Trophy Points:
      83
      The AI got some design updates in #217 to try and help keep pace with the massive number of calculations required in the game. There's been a few unintended side effects, and they are getting fixed as soon as enough information is collected.

      Release #220 was just released that should fix the ArgumentOutOfRangeException that has been randomly occurring. If you guys run into any other unexpected behavior or errors, please post in the Support section, attach a full log, and it'll get looked into as soon as possible.
       

    Share This Page