Upcoming Downtime for Patch 4.2.0

[pushedx]

This is just a heads up there will most likely be some downtime when the upcoming 4.2.0 patch is fully released. There's no known ETA when the patch will be available, or how it will affect the bot, but we'll let users know as soon as we do.

In addition, the next version of Hearthbuddy will have new prerequisites: https://www.thebuddyforum.com/the-b...s/241851-buddy-bots-prerequisites-update.html, so please plan accordingly if you are on an older system without the required updates.

A Hearthbuddy installer has also been made, and will be a part of the next update as well.

 

[pushedx]

We're approaching a release pretty soon for HSB. The current patch notes are as follows:

• 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: http://updates.buddyauth.com
• 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).

Based on what we've seen with our other bots with the .Net 4.6.1 migration, some users will run into issues. Please try using our new installer (once it is published on the BuddyAuth page) before asking Support for help (as they will ask you to do the same ).

We thank users for their patience, and compensation for the downtime will be given soon once we get launched.

 

[pushedx]

Build #249 has just been released! Once again, users can find the new installer on this BuddyAuth page.