HearthbuddyBeta GvG Release Thread

Edited: It crashes, my previous statment is pointless.

 

From the auto-stop stats, right? Not from the stats tab? Mine only crashes with the reset from the Auto-stop tab. The stats one works.

 

Edited: It crashes, my previous statment is pointless.

 

Reset button on Auto-stop settings crashes before pressing start button.

 

Is the Undertaker card well programmed into the AI? I get the impression it's missing the deathrattle bonus because it often times plays it after playing a deathrattle creature. The board simulation from the AI should be able to calculate that synergy.

 

There are mixed results. You can tell the bot does consider the card a high priority early game. So it is usually played on the board first and if you have a deck with many deathrattle minions, they will follow. For example in my Hunter Zoo deck, the bot will often turn 1 Undertaker then coin into Webspinner, Leper Gnome, etc. Next turn might be Haunted Creeper, and then the snowball begins =). It usually plays out very well early game. However, because the logic seems to be priority based and not combo based, turn four it would drop Harvest Golem before an Undertaker. I think this is a fine foundation in how the bot should make decisions. Further refinement would add specific combo logic making undertaker a temporarily higher priority even in later turns, as long as certain combo conditions are met.

EDIT: Just saw the bot turn 5 properly play Undertaker, then Sledge. Possible due to new beta updates.

 

How to edit Mulligan by myself ? Any tips

 

In the DefaultRoutine.cs file in the Routines/defaultRoutines folder. There's a section reserved for the mulligan rules with some examples of how to write the rules.

 

Does the AI use other threads to help speeding up the calculations? Sometimes it feels like it doesn't since the bot stop responding to inputs during the calculation phase. Then again I'm running some modifications on the AI parameters here. Even so there should be an option to limit the bot thinking phase to 30 seconds top. Anymore than that the risk to miss the turn becomes to great.

I guess this doesn't affect the default bot, though. So it's just my 2 cents on the issue.

 

Got an exception every time I started the bot with that final hand in the log. Something about an iteration error, probably a foreach in a collection that's being modified.

 

Alot of times both if i start or im out second when auto concede is activated it plays a card then concede feels pretty unrealistic when it
1, let opponent play. 2, My turn. 3, Greet Opponent. 4, Lay a card. 5, Concede
either concede on opponent turn or make it concede automaticly on your turn with no moves before

 

Same here, I think that's a pattern blizzard would pick up on quickly if they did any kind of investigating.

 

I think greeting your opponent (or using some other emote) is good as well as waiting for at least one card. You're just waiting if you get a good draw and then concede. Looks more realistic to me than conceding immediately.

 

for today update 0.3.806.90
in the constructed game .
change custom to basic , and my decktype to another .
every time i change deck type to custom next game it change it to basic .

 

It's the auto quest plugin. Since it doesn't check the decks anymore it doesn't work well. Disable it or click the re-cache custom decks for it to work.

 

I turn off quest plugin and click re-cache custom decks .
now working .
thanx narika

 

why there is no "auto Arena" in this update?

 

Got no response in this matter.. saw other too was interested in this question.
is this something the dev's are gonna do something about?

Today i got:
1 Oponent turn. -> 2 Oponent put out card. -> 3 My turn. -> 4 Use coin. -> 5 Put out weapon. -> 6 Greet oponent . 7 Attack oponent. 8 Attack. -> 9 Concede.
For me it feels pretty obvious (but im a botter) that its a bot but feels little suspicious i feel.
And also would be able to cut gameplay time alot too with faster when goldfarming if autoconcede cleared the quee for next moves.

 

He has explained how to make it concede faster somewhere in this thread, don't really wanna go look for it.
Go into your DefaultBot.json file in the /settings/default/ folder and change AutoConcedeMinDelayMs and AutoConcedeMaxDelayMs to something much lower.
Default is 15-30 seconds before it concedes which is why it's doing what you describe.

 

HearthBuddy crashes after hiting "Reset" button on the AutoStop plugin, above is log

https://www.thebuddyforum.com/heart...-autostop-plugin-post1828172.html#post1828172