All of those sounds like bot problems. Vinecleaver has a natural buff to attack face as well as a suggestion to not attack if you have 6 minions. The bot isn't handling weapon hits correctly. Report all of those misplays in the bot and hope they get better soon.

Still wish you would upload to github so we could know exactly which files were changed

@misused, When I get some free time, I'll submit a config for a couple decks

Right now I'm thinking

- Standard Zoolock
- Standard Rush Warrior
- Wild Odd Paladin
- Wild Murloc Paladin
- Wild Burn Mage

We really should start focusing more on Wild, because it's an easier grind to rank 5 than standard (even using a standard deck in Wild).

Won't happen because the bot performs best with simpler decisions like when playing aggro decks:
- Standard Taunt Warrior
- Standard Taunt Druid
- Standard Cubelock (You would think the bot could always figure out a full board clear with defile)
- Wild Malygos Druid/Rogue
- Wild Jade Druid
- Wild Giantslock
- Wild Mill Rogue

I have virtually every major META deck, I will happily test them in ranked for you ranks 15-5. At 14 currently. If I can help with testing or whatever please let me know. Have most cards, most decks, very good comp that I built so I won't time out on turns.

On the Baku Pally V 1.2, 1 important thing I noticed, over 100 games b0t with this deck, Previous version with config was 45% winrate in ranked at rank 15 with ~100 games. Currently using 1.2 and new config, at 57% winrate (21 games).
*STILL ON 1.2*

When you cleared the enemy board, have minions down and 1 durability left on weapon *with another weapon in hand* it wont always hit face...it should always hit face in this situation. No minions to hit on their team, you have board control and another weapon with enough mana for it. You should always finish your current weapon and hit face here at least with THIS deck 99.99% of the time. I over rode the b0t and proceeded to win the following turn by 1 dmg...wouldn't have won that turn without override. I know that not every situation is like this and its hard to code but with an aggro/baku deck like this you have to go face in that situation. pretty much always.

The thing with Glacial Shard can be fixed by config.

"BeforePlayCardBonus":
{
"values":
[
{
"comment":"Attack with minions first",
"condition": "my_minions(count(), tired = false) > 0",
"value":"-10",
},
],
}

With this bot will first attack with minions (and trade if necessary) and then freeze character that left. You can add it to your config if you want.

Try running on casual first, bots won't be as effective on ladder yet. Most odd paladin are doing good against aggro and losing out to taunt druids and cube locks, so it depends on what decks you are facing.

We don't really want to always use Glacial Shard last. If you see misplays regarding it make sure you report it in the bot.

Why would it be a bad thing to attack first and use glacial shard last?

The general rule of thumb is to not brute force anything in the configs unless it's lethal. Configs serve as a way to suggest things for the bot to do depending on the deck. Making the bot always freeze after attacking opens up a variety of misplays. What if the opposing minion has an active like draw a card whenever attacked? Or Increase attack when attacked? Stuff like that makes it too complex for us to write a config for every possible scenario when you can rather report the issue in the bot itself and let Joy update it in a few days.