HearthbuddyBeta GvG Release Thread

Hello,

i don't know if it's a good place for that but:

View attachment Hearthbuddy 8104 2014-12-24 01.29.txt

 

We'll check into this, thanks!

We'll double check the code, thanks for reporting.

Please run the Buddy Dependency Wizard, restart your PC, and make sure your AV/Firewall software is not quarantining GreyMagic.dll.

The bot should work in any resolution. If you notice a resolution having issues, please report which resolution (as well as your monitor setup, e.g., 1 , 2, or 3) and we'll double check it. There's not much customizable for the rush vs control playstyle yet. I think SF has a setup for it, but right now we're only using control.

 

This is not possible, because the bot must take control of input in the client to work. In order to have the targeting arrow, and make the bot interact with the game as a normal player would, it must use input events the same way a human would, so there's no way for both the player and the bot to interact with the game at the same time when it's running.

Please change the game mode to practice, and run it again and see if it still happens. I'd like to see a longer log of the bot actually doing things in game in order to know what to look into next.

Yes, thank you for reporting with a full log. Your client somehow entered the "play queue" state once a new game was started, which is not currently handled. We'll try to look into handling this correctly.

 

The next version will change the error message you see. This change was also recently made in EB as well to make that error message more understandable.

From what I've seen so far, with people who have had that error in both EB and HsB, there's something running on your machine, whether it's a firewall, possibly a hosts edit, or another 3rd party software that is affecting HsB's auth process. As a result, when the bot goes to Auth, it cannot because something is either preventing it, or modifying it, so it breaks.

I do not know specifically what is affecting it, but users who have tried on a clean VM or reinstalled their OS seem to have fixed the problem. (if you do either, and it works, please let us know!) All I can recommend to you right now is to make a new Support thread with what you posted in your first reply, and I'll ask Tony to assign someone who can TV your machine and try to figure out what is going wrong. I don't know how soon someone will be able to help you, so you unfortunately might have to wait some time, as Support can be slow around the holidays.

 

Now i get this error instead, i using another computer to set it up.,

 

Max Sessions is an easy to fix issue.

Simply go to your BuddyAuth Sessions page and kill any sessions listed. Sometimes if there's an auth error, your session takes a while to timeout, so you reach your session limit rather fast. Killing off old sessions frees them up.

If you run into any other troubles, please let us know.

 

Am i the onlyone whos problem havent taken care off?

 

freez

bot beta freez at start

 

Never uses Tracking as hunter. Also plays rhino when starving buzzard would be a lot better.

 

Where we can change control for rush ?

 

some recommendations to be implemented overall are the bots general ability to understand combos that are oftenly used. i.e force savage

 

So if I use classic huntard deck he will never trade and only hit face ?

 

Please try this:

0. Make sure Hearthbuddy is not running.
1. Create a new file in your Hearthbuddy folder called "HearthbuddyBETA.exe.config"
2. Edit that file in a text editor, and paste in these contents:
You need to register and have one post to see spoilers! 3. Save the file and restart Hearthbuddy.

I believe that should fix your issue.

 

Tracking was never supported, even in the older version. We do plan on supporting it in the future though!

This is not possible yet, but some changes to settings will be made soon to allow changing it.

This is something we definitely want to have support for. We need a different system in place to do it first though, so we'll be working towards that.

No, Control plays all decks as control. It won't attempt to rush down the opponent, like Rush would.

Win rate with basic decks against Normal AI is pretty solid. I do a lot of testing with Hunter vs Hunter and the only times it really loses is when the deck order is terrible (big minions, useless skills come first, AI gets out raid leaders and wolves very fast).

I would not recommend trying to use Basic hunter deck for anything else. You can draft a custom deck with some basic cards that will perform better.

 

Ok thanks, I just want to farm my golden hunter and priest as fast as i can. So the basic deck with concede after win is good for that ?

 

I saw that changes to the settings will be made available at a later update. Please add a change for the weapons to not attack face unless lethal or setting up to lethal next turn. the 15 hp is too high of a default and weapons charges too valuable to waste at face in a control playing bot.

 

any way to speed the bot up its seems very slow to react.Also the targeting looks very bottish like it targets self than moves anybody know what i mean?

 

bot still takes too long to target often ending up with turns where 1 - 2 minions dont attack depending on how big my board is

 

Very big request onto developers or programmers! Plz make an option that will save statistics into file somewhere in the folder or somewhere else... but really last stats must be saved i usualy start bot for night and when i wake up im morning i enable my monitor and usualy what i see is: Bot has stoped working some time ago in night and i'm disconnected for long time probably as well. Stats are gone(i cant check how god or bad deck was with bot) Really upset sometimes becouse of it...

 

There's still a lot to look into and tweak with the play style of the AI as well as making it able to perform actions faster. Working out the speed of a turn is the next big thing going to be attempted to be resolved.

Settings should be saved as soon as you make a change to something that is automatically handled, but we'll throw in a few extra force saves to try and address that issue.

In addition, a statistics summary will be added back into the Stats plugin example so you can just check your log file for the info itself.