• Visit Rebornbuddy
  • Bug 4

    Discussion in 'Hearthbuddy Support' started by EmoKlaus, Sep 29, 2015.

    1. EmoKlaus

      EmoKlaus New Member

      Joined:
      Jun 22, 2015
      Messages:
      57
      Likes Received:
      0
      Trophy Points:
      0
      HB NEVER TRIES TO KILL "WARSONG COMMANDER" !!!!!!!!!

      Destroying that minion MUST HAVE HIGHEST PRIORITY !!!!!

      Look at the last turn....

      PS: I didnt get feedback to "Bug 3"
       

      Attached Files:

    2. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,252
      Likes Received:
      290
      Trophy Points:
      83
      Issues are noted and looked into, so you won't get a reply to every single post. If more info is ever needed for something though, we'll ask for sure.

      A lot of times, people make requests for the bot to make decisions the same way they would, but we might not agree with that line of decision making. We're not going to debate every single request and why or why not it'll be changed though, so for the most part, we'll let those posts just sit.

      Actual "bugs", such as a minion being totally ignored (if that's what is actually happening), will be given more priority and thought compared to other non-bugs in which people simply disagree with the decision route being used.
       
    3. EmoKlaus

      EmoKlaus New Member

      Joined:
      Jun 22, 2015
      Messages:
      57
      Likes Received:
      0
      Trophy Points:
      0
      But u actually understand, that a Warrior with "Warsong Commander" will kill u next turn, when its not instantly removed ?

      I watched the Bot ignoring that minion more then once and the result was always losing during the enemies next turn.
       
    4. Coolmaster

      Coolmaster Member

      Joined:
      Aug 16, 2013
      Messages:
      709
      Likes Received:
      3
      Trophy Points:
      18
      EmoKlaus, your log also contains some other errors.
      Thank you. The problem has been fixed, and you will get the solution in the next update.
       

    Share This Page