• Visit Rebornbuddy
  • Hearthbuddy Release Thread

    Discussion in 'Hearthbuddy Forum' started by pushedx, Apr 3, 2015.

    Thread Status:
    Not open for further replies.
    1. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,258
      Likes Received:
      290
      Trophy Points:
      83
      Hearthbuddy BM Release Thread

      This thread marks the first Release version of Hearthbuddy since the BM update. "Release" versions are meant to represent "stable" versions that we do not tinker with on a daily basis. This "Release" version represents the best stable build possible at this time. As with any of our bots, it is not perfect, and while we've tried to eliminate as many bugs as possible, users will still encounter them. We'll do our best to address them as soon as we can.

      Getting Started

      If you're new to our BuddyAuth setup, please see the Buddy Authentication Portal wiki page. You can find basic information on our system there.

      If you need any type of support, please use the Support Forum. Users must attach a full log (unmodified) in order to receive support.

      Windows XP is no longer supported. While this change has been in place for a while now, we want to remind users of it here.

      Please run the Buddy Dependency Wizard first. It will update .Net 4.5.1, and all of the Visual C++ Runtimes we use. Some users still experience problems afterwards, and are usually able to solve them by uninstalling all previous versions of .Net and the Visual C++ Runtimes, rebooting, and then running the Buddy Dependency Wizard. Support will ask you to do this if you have any problems running Hearthbuddy, so we encourage users to do it themselves to see if they can solve their problem faster.

      Hearthbuddy Guide

      NOTE: This guide was copied from the previous GvG thread. It has not been fully updated with some of the latest changes, but will be done so at a later date.

      1. Download Hearthbuddy from BuddyAuth. The new version starts with build #144.
      [​IMG]

      2. Right click on the "Hearthbuddy" zip file and "Extract All...".
      [​IMG]

      3. The Window's Extract Compressed (Zipped) Folders dialog opens. Simply click on the "Extract" button to begin extracting the bot.
      [​IMG]

      4. The bot will now begin to extract. This process might take a while for some users with slower PCs due to the number of files that must be extracted. Please wait patiently for it to finish.
      [​IMG]

      5. When the extraction process completes, a new Hearthbuddy folder will open. The directory layout will resemble this.
      [​IMG]

      6. Sometimes, Windows blocks new files on your PC when you download them from the net. Right click on "Hearthbuddy.exe" and choose "Properties".
      [​IMG]

      7. If the file is blocked, you will need to "Unblock" it by clicking on the "Unblock" button, followed by "Apply" and then "OK". Not all users might see this, so this step is only necessary if you do.
      [​IMG]

      8. Hearthstone must already be launched. Run Hearthbuddy by double clicking "Hearthbuddy.exe" or by right clicking on the file and choosing "Open". If you ever have issues on this step, try "Run as administrator" instead.
      [​IMG]

      9. When Hearthbuddy starts, you will see a "Configuration Window". For now, simply click "Select" to use the "Default" configuration.
      [​IMG]

      10. Next, the "Hearthbuddy Key" window will be shown. Enter your Hearthbuddy key and press "Login".
      [​IMG]

      11. Hearthbuddy will now start. Please wait a moment for it to fully load and compile bots, plugins, and routines.
      [​IMG]

      12. Click on the top-most "Config" button. This button will change to the Settings tab for the current select Bot. You can configure the current bot as you need.
      [​IMG]

      13. Click on the bottom-most "Config" button. This button will change to the Settings tab for the current select Routine. You can configure the current routine as you need.
      [​IMG]

      14. After going though the GUI, and changing settings as needed for DefaultBot and DefaultRoutine, click the "Start" button at the top. Hearthbuddy will now navigate it's way to the selected game mode and start botting away.

      DefaultBot Guide

      All Game Modes

      "Deck Type" - The type of deck to select.

      Basic: The bot will use the "Basic Deck (Deck Type = Basic)" field as your deck.
      [​IMG]

      Custom: The bot will use the "Custom Deck (Deck Type = Custom)" field as your deck.
      [​IMG]

      Practice

      "Difficulty" - The AI difficulty.

      Normal: The bot will play practice games against the easy AI.
      Expert: The bot will play practice games against the hard AI.

      [​IMG]

      "Opponent Class" - The AI deck to play against.
      [​IMG]

      Constructed (Play)

      "Mode" - The type of constructed game to play.

      Casual: The bot will play unranked constructed games.
      Ranked: The bot will play ranked constructed games.

      [​IMG]

      "Keep Constructed Rank" - The bot will auto-concede after wins to keep your rank. More information.

      Friendly (Duel)

      "Allowed Name" - The name of the play to accept duels from.
      [​IMG]

      DefaultRoutine Guide

      NOTE: A lot of features and options are not ready to be user configured yet. As a result, they are not shown in the GUI. This includes things like mulligan logic, arena draft logic, and various Silverfish settings.

      "ArenaPreferredClass" - The class the bot will auto-choose for Arena runs if it is available.

      By default, the routine will choose:

      Hunter first if it's available.

      Warlock second if it's available and Hunter is not an option.

      Priest third if it's available and Hunter/Warlock are not options.

      Rogue fourth if it's available and Hunter/Warlock/Priest are not options.

      Warrior fifth if it's available and Hunter/Warlock/Priest/Rouge are not options.

      [​IMG]
       
      Last edited: Apr 5, 2015
      grynf likes this.
    2. pushedx

      pushedx Moderator Moderator Buddy Core Dev

      Joined:
      Sep 24, 2013
      Messages:
      4,258
      Likes Received:
      290
      Trophy Points:
      83
      Changelog
      #401 [09 Oct 17 22:05]
      • Next wave of various internal SF changes.

      [...]
      #394 [28 Aug 17 06:35]
      • Next wave of various internal SF changes.

      #392 [19 Aug 17 01:24]
      • Next wave of various internal SF changes.

      #391 [15 Aug 17 03:39]
      • Updates for 9.0.0.20457.
      • Next wave of various internal SF changes.

      #387 [13 Jul 17 23:10]
      • Updates for 8.4.0.20022.
      • Next wave of various internal SF changes.
      [...]

      #375 [02 Jun 17 22:49]
      • Updates for 8.2.0.

      #371 [26 May 17 08:00]
      • Next wave of various internal SF changes.

      #369 [08 May 17 01:18]
      • Next wave of various internal SF changes.

      #367 [25 Apr 17 18:25]
      • Next wave of various internal SF changes.

      #364 [22 Apr 17 03:15]
      • Updates for 8.0.4.

      #362 [20 Apr 17 22:03]
      • Next wave of various internal SF changes.

      #358 [13 Apr 17 12:43]
      • Updates for 8.0.0.
      • Next wave of various internal SF changes.

      #350 [10 Mar 17 06:50]
      • Updates for 7.1.1.
      • Next wave of various internal SF changes.

      #346 [26 Feb 17 05:54]
      • Next wave of various internal SF changes.

      #344 [05 Feb 17 20:01]
      • Next wave of various internal SF changes.

      #342 [19 Jan 17 05:42]
      • Next wave of various internal SF changes.

      #340 [21 Dec 16 20:57]
      • Next wave of various internal SF changes.

      #339 [15 Dec 16 03:46]
      • Next wave of various internal SF changes.

      #336 []03 Dec 16 17:01]
      • Updates for 7.0.0.
      • Next wave of various internal SF changes.

      #329 [04 Nov 16 20:20]
      • Next wave of various internal SF changes.
      • Deck caching bug fixed where existing decks that changed were not properly updated.
      • The QuestPlus plugin is now included with HSB. Various internal changes made to support new features.

      #321 [21 Oct 16 18:22]
      • Updates for 6.2.0.
      • Next wave of various internal SF changes.

      #318 [20 Oct 16 07:38]
      • Next wave of various internal SF changes.

      (entries missing for some reason)

      #308 [08 Sep 16 04:18]
      • Next wave of various internal SF changes.

      #306 [02 Sep 16 03:24]
      • Next wave of various internal SF changes.

      #304 [24 Aug 16 20:41]
      • Next wave of various internal SF changes.

      #302 [17 Aug 16 07:43]
      • Next wave of various internal SF changes.

      #300 [12 Aug 16 07:58]
      • Next wave of various internal SF changes.

      #297 [10 Aug 16 02:37]
      • Updates for 6.0.0.
      • Next wave of various internal SF changes.

      #294 [26 Jul 16 23:43]
      • Updates for 5.2.2.

      #292 [16 Jul 16 02:59]
      • Updates for 5.0.2.

      #290 [15 Jul 16 04:31]
      • Updates for 5.0.2.

      #287 [14 Jul 16 18:46]
      • Next wave of various internal SF changes.

      #284 [13 Jul 16 15:53]
      • Updates for 5.0.2.
      • BotManager will no longer stop on a GreyMagic.InjectionDesyncException.

      #281 [07 Jul 16 12:06]
      • Next wave of various internal SF changes.

      #278 [28 Jun 16 23:39]
      • Next wave of various internal SF changes.

      #277 [22 Jun 16 04:07]
      • Next wave of various internal SF changes.

      #276 [08 Jun 16 23:00]
      • Next wave of various internal SF changes.

      #275 [01 Jun 16 21:02]
      • Updates for 5.0.1.
      • Next wave of various internal SF changes.

      #272 [21 May 16 06:40]
      • Small bug fix.

      #271 [19 May 16 20:26]
      • Next wave of various internal SF changes.

      #268 [11 May 16 03:24]
      • Next wave of various internal SF changes.

      #265 [03 May 16 02:52]
      • Next wave of various internal SF changes.

      #263 [27 Apr 16 21:41]
      • Next wave of various internal SF changes.
      • The bot now supports switching between wild/standard game modes for Constructed games.
      • The quest plugin has had minor updates to handle the new game modes and 2 new Old Gods quests.

      #258 [21 Apr 16 08:17]
      • Next wave of various internal SF changes.

      #255 [15 Apr 16 07:25]
      • Updates for 4.3.0.
      • Next wave of various internal SF changes.

      #254 [01 Apr 16 22:02]
      • The bot should now be able to handle the basic decks on accounts that do not have all heros unlocked. These decks can be referred to by class name, such as Mage for the mage deck, or the custom name given in the collection manager.
      • Next wave of various internal SF changes.

      #251 [22 Mar 16 16:01]
      • Next wave of various internal SF changes.

      #249 [17 Mar 16 19:36]
      • Due to recent game changes, the concept of deck types (basic/custom) no longer exists. All decks are now custom decks, so a lot of GUI settings have been removed. This means users must always enter a deck name for the bot to use.
      • The bot's model of caching decks has been improved and made less annoying.
        • It will perform a full deck cache the first time you run it. It will only have to do this once per configuration, or your deck cache is manually cleared.
        • It will visit the collection manager on start, or when it needs to re-cache custom decks (user tells it to). This is the best way to handle cache updates, but it won't have to check the contents of each deck each time like before.
        • Cached deck info will now be consistent for everyone, and can be used by the AI for better logic in the future.
      • The Quest plugin now support ignoring up to 17 decks by name.
      • An installer is now available for HSB via BuddyAuth: Buddy Updates
      • Hearthbuddy now uses .Net 4.6.1 and the Visual Studio 2015 runtime: https://www.thebuddyforum.com/the-b...s/241851-buddy-bots-prerequisites-update.html
      • Next wave of various internal SF changes.
      • If you manually stop the bot during a queue, you need to manually go back to the Hub before being able to re-queue with the bot again. This will be worked around in the future, but is due to a client change where the client state is not correct anymore (it's still marked as being in queue).

      #235 [23 Feb 16 23:14]
      • Next wave of various internal SF changes.

      #233 [21 Feb 16 20:03]
      • The bug where the symlink was not found should now be fixed.
      • Startup info is now logged at application start, rather than when the bot window loads.

      #232 [20 Feb 16 13:21]
      • Various bot updates. Reloggers will need to be updated for compatibility.
      • Hearthbuddy now requires admin privileges to run.
      • An autostart parameter has been added to allow users to auto-start HSB. To use it, simply execute HSB with --autostart.
      • An additional parameter --noautorelaunch has been added to allow users to not auto-restart HSB at startup when it needs to.
      • The bot will now log why offsets could not be retrieved. Before, it did not and showed a generic error message.

      #225 [10 Feb 16 20:49]
      • Various internal bot updates.
        • The bot will now correctly log Tripwire events and open the log file to let the user know why it is no longer starting.

      #223 [06 Feb 16 11:08]
      • Next wave of various internal SF changes.

      #220 [17 Jan 16 04:56]
      • Bug fixes for some issues introduced from #217.

      #218 [16 Jan 16 11:25]
      • Bug fix for an issue introduced in the previous version with Mages under certain conditions.

      #217 [15 Jan 16 22:22]
      • Next wave of various internal SF changes.
        • Multi-threaded updates to SF to improve performance and calculations.
      • The spectate quest should now be ignored in the Quest plugin.

      #215 [25 Dec 15 06:52]
      • Next wave of various internal SF changes.

      #213 [05 Dec 15 01:01]
      • Updates for 4.1.0.10956.

      #210 [04 Dec 15 02:51]
      • Next wave of various internal SF changes.

      #208 [13 Nov 15 19:57]
      • Updates for 4.0.0.10833.
      • TritonHs.RecallOwed is now TritonHs.OverloadOwed.
      • Next wave of various internal SF changes.

      #201 [05 Nov 15 02:25]
      • Next wave of various internal SF changes.
      • Project updated to VS 2015 and other internal changes.

      #197 [21 Oct 15 16:45]
      • Updates for 3.2.0.10604.
      • Next wave of various internal SF changes.

      #194 [15 Oct 15 05:51]
      • Next wave of various internal SF changes.

      #192 [30 Sep 15 20:48]
      • Updates for 3.1.0.10357.

      #190 [25 Sep 15 23:01]

      #188 [23 Sep 15 08:38]
      • Next wave of various internal SF changes.

      #185 [27 Aug 15 17:39]
      • Next wave of various internal SF changes. (Grand Arena stuff)

      #184 [20 Aug 15 18:05]
      • Updates for 3.0.0.9786.
      • Next wave of various internal SF changes.

      #181 [31 Jul 15 23:29]
      • Next wave of various internal SF changes.

      #180 [31 Jul 15 08:10]
      • TritonHs.EnemyHeroPowerCard now returns the correct HSCard.

      #179 [30 Jul 15 09:18]
      • Updates for 2.8.0.9554.
      • Next wave of various internal SF changes.

      #177 [09 Jul 15 00:14]
      • Next wave of various internal SF changes.

      #174 [27 Jun 15 08:57]
      • Next wave of various internal SF changes.

      #171 [19 Jun 15 01:44]
      • Updates for 2.7.0.9166.
      • Next wave of various internal SF changes.

      #166 [12 Jun 15 23:09]
      • Cumulative updates for internal SF changes since last version.
      • Global Greymagic changes.

      #152 [15 May 15 23:39]
      • Updates for 2.6.0.8834.

      #151 [10 May 15 10:20]
      • Next wave of various internal SF changes.

      #150 [23 Apr 15 09:00]
      • Next wave of various internal SF changes.

      #148 [15 Apr 15 05:22]
      • Updates for 2.5.0.8416.
      • Next wave of various internal SF changes.

      #147 [09 Apr 15 22:21]
      • Attacking should now function quite a bit faster as expected.
      • Various fixes for reported issues.

      #146 [07 Apr 15 12:09]
      • Various fixes for some exception issues after the update. Please continue reporting logs with any issues.

      #144 [05 Apr 15 11:08]
      • Updates for 2.4.0.8311.
      • Initial changes for Blackrock support.
      • Added a possible fix for some bot/client instabilities by resetting the bot coroutine when the client state changes into something non-usable. Before, the previous executing code would resume executing after a delay when objects in the client might now be invalid.
      • Added an event for FATAL_ERROR processing to DefaultBot. This should help expose some more info to plugins that want to implement relogging with an external program.
      • Added MainSettings.AllowExternalAccess. This is an opt-in setting to allow external relogging programs to close the bot gracefully, to avoid auth issues when killing the bot forcefully. Users can enable this setting from the Main settings tab.
      • The main gui now supports user messages to allow external programs like reloggers to handle managing the bot easier. This is just an early test of a new system to be used in the new GUI. More technical information on this will be discussed later. Right now, programs can poll to see if the bot has fully loaded, is the bot running/stopped, is the client frozen.
      • Added BotManager.OnClientFrozen. This event will be invoked so subscribers will know when a client frozen exception is encountered in the bot.
      • BotManager.ClientFrozen added. This is to store if the client is currently detected as being frozen.
      • If the client is frozen, the bot thread will stop, so external programs can trigger a graceful exit and avoid auth issues. Before, users would have to manually stop the bot themselves.
      • PollForEmotes has been temporarily disabled as it has been identified as a cause of client freezes during the opponent's turn.
      • The bot's current AccessToken is now on the Main settings tab for manual input into external programs that can use it.
      • The Spectate functionality of the bot has been temporarily removed due to client changes. It must be rewritten for new client compatibility.
       
      Last edited: Oct 9, 2017
    Thread Status:
    Not open for further replies.

    Share This Page