Build .102 changelog

I am amazed how fast you push new changes. Great work!

 

Any info on the Rush profile? I played 5 games with a Warlock Murloc deck with and without rush " 10 games in total" I did not notice a different in the play style

 

thank you for frequent updates
I increased my win rate of 50% to 75%
continue as you are doing the good job

 

wow...it is a nice won rate.

can you share you deck,it will be the nice..thank you,.

 

I want it too, because i use Rush profile, winrate in rank game 40%-->25%, after i close the Rush profile, my winrate incause to 45% at the same deck
have any deital about the Rush profile? or the Rush profile only use for Some heroes?

 

on this post i have tell my deck...
now i have between 70% and 75% on one night^^
http://www.thebuddyforum.com/hearthbuddy-forum/160977-whats-your-guys-win-rate-3.html#post1508591

 

I was asking for rush profile it should work like HearthBuddy first version - Bot of Stone. It should always attack face, if there is a taunt kill that taunt and attack face. I was testing it on a special charge warlock profile and it worked very well. May be not in terms of win rate - it's the same as with normal warlock profile but games are much quicker - you either win or die fast. If you want it work you need to build your deck around quick, charge style.

 

Hello, thanks for the wonderful updates! I wanted to point out a crash i had yesterday it was a runtime error r6025 pure virtual function call. I was using Mage, it caused the bot to stop working not sure if anyone else has encountered this. I'm running windows 8.1.

 

never seen this im on windows 7 64bit win 8 is a shit os go back to win 7

 

Hi i found another bug, playing against Mage she used something that made her hero immune to getting attacked (not sure if it was a spell or minion ability i didn't check). I glanced over to the bot and realized it kept trying to attack hero over and over with same minion until time ran out. The sad part was it had 10/10 mana with a storm wind champion and it didn't play it nor its ability, so 10 mana went unused and bot ultimately lost. Oh well just pointing this out. Thanks.

 

Ok also i noticed opponent play abomination, then bot played a bunch of -2 health minions... Then the bot killed abomination which cause -2 all minions... So it was a huge waste. Would have been smarter bot killed abomination then played minions...

Additionally i haven't seen paladin play equality card... Hes held onto it a few games now. Thanks.

 

A bad move when playing a rogue, he does not properly the combos :
SI:7 Agent is never played as a second move !

 

there should something be doing on the lag while trowing the card on the board and when hitting the card with a minion i have 2 bots this one and another one with the other one i dont have those lag issue i hope u can fix that soon.

 

Hi, I found a bug here. When there is a faerie dragon. My hero will try to use Mortal strike to attack it. Apparently, it does not work. And I will do nothing this turn but try to use spell on it again and again.

 

None

 

bot should try to use equality and consecration when both in hand and enemy can either deal fatal damage, enemy has a hand full of minions on the field, enemy has a card on the field with 9+ or more damage, or maybe some sort of last turn we took a certain amount of damage and lay down both cards. bot also has to have some work done on its ability to prioritize. cant think of an example right now but, ill post results. good previously posted example was the abomination and the bot lays down a bunch of -2 hp guys and wipes out the field

 

Bot will sometimes decide that coin is valuable to use to be able to drop a higher mana minion. It plays the coin, but seems to forget about the card it was about to play afterwards.

 

I think bot should throw away 4 drops in mulligan. He keeps that 4 drops and it slows him down many times.

 

That'd be stupid. Especially if you have coin. You also risk getting an even higher drop.

 

The deck you use for the bot has to have a relatively good bell curve. Usually with human players, you can compensate for a bad spread by mulliganing specific cards and also playing coin/cards strategically. The bot does not take this aspect into account and thus plays your best option not thinking about what it can do the turn after. Therefore your spread has to be really good or else you'll be stuck with turns where it will just hero ability (which is a waste). Therefore if you are being slowed down by just 4 drops, your deck should be reworked.

I'll give an example of a bad play that a bot made, that a human wouldn't in regards to future turns:
-I have in hand a leper gnome (1 cost), frostwolf grunt (2 cost), harvest golem (3 cost), boulderfist ogre (6 cost), and coin
-turn 1 (going second) the bot drops coin and the 2 drop (which sometimes can be good, but in this case, no)
-turn 2 it didn't draw a 2 cost, and therefore now has to drop the leper gnome and end turn. (wasting our 1 mana crystal)

This is terrible, because a leper gnome is a 2/1 and therefore is a very good first drop, dropping a 2/2 over it makes zero sense, unless the other class is a mage (we want rogues/druid to face it most of the time, so it doesn't matter if they waste their turn 2 hitting it). ALSO in this case, it is also the better drop vs. a mage because the mage will be forced to ping it turn 2, and thus waste their turn to remove our 2/1 while still taking 2 damage. NEXT turn is where it's great for us, because turn 2 we drop the coin and bring out a harvest golem, now we're ahead quite a bit.

The way the bot does it, wastes our coin for a CHANCE at 2 damage (which would be have been guaranteed by our leper gnome anyway), and makes our turn 2 a waste. If it were played the other way, our mana would have been used efficiently, and we would also have greater board presence.

Sorry for the convoluted reply, but this is also a bot behavior I would like to report in this thread.