http://pastebin.com/NzFY2H3e

Turn 6:

Uses tuskar (3 attack) to hit the twlight guardian, then rockbiter on self to kill off the twilight Guardian
Why not just use rockbiter on tuskar and kill guardian right away, saves 3 dmg to own face.

In the same log on turn 7:

why does it hit the frothing berserker with the mana tide? It just makes him mad (gains AT)

Confused why you quote those misplays in combination with your question XD but you mean these?:


Tbf i dont know. I made these a while ago when it was misplayed and this fixed it. But maybe this is fixed anyway now without the needs of these combo's. If i recall correctly there was indeed a fix about buffing tunnel trogg correctly so you might be right. Ill remove them and see.

No the penalty number behind the cardID makes the card less played. like i.e.

Behind the 2 cardID's the value is 0 so there is no penalty for playing it outside the combo. The bonus just makes it more likely to play it together if its in the hand together.

When u add value; so change the number behind the cardID higher then zero, it will be played less till not at all (Depending on the number) if not in the combo.

---

To make individual cards play LESS likely make a cardvalue in this example card X with the ID XXX_999


to make a card play MORE likely you can add a negative cardvalue by just adding - before the number so:


There is no science in this, start with a number not to high and do tests, the higher the number the less or relatively more, it gets played


I will check if i have time to write a more detailed version how to make combo's. Been testing around with it allot. You can also push cards on certain turns etc. the combo file can in some cases be even more important then the mulligan file

Turn 6: This is a misplay. The bonus to not waste rockbiter caused it. Demonstrates what Sepefeets says about trying to fix one thing but causing misplays in other situations.
The bonus that caused the misplay:
if (p.ownHero.tempAttack > 0) retval += -5; //bonus to not waste rockbiter


Turn 7: This is a misplay. There was datasync after the wolves, but I do not think it caused the misplay.

http://pastebin.com/XuAeYD9b

Turn 7, it should place a little bit more priority on killing the patron. As seen, it gets ugly fast. Turn 6 was played correctly.

http://pastebin.com/vVc5s5uP

Turn 6, doesn't play flameimp? Don't mind the settings. There was some experimenting :D

http://pastebin.com/SnS2DJ6G
Turn 4. Should attack with councilman into face than react from there. This is a case of valuing the councilman buff over trap checking.

Btw, can you make it so I can specify exact turns for the combo?

Idea #2

When the bot detects X seconds of your turn has passed, it will use secondary settings (same as settings.txt but different values as specified by the user).

It already does in the Logging.txt file.

I know but this is a very big file, very hard to see which mulligan was for which combatlog. It would be nice if that small piece like 5-6 lines are on the top of every combatlog. So you know what mulligan was for that log.

Swiping the wrong target:

1036. playcard: Swipe target: Blackwing Corruptor choice: 0 place1

Would have cleared the board if it had targeted the Azure Drake

//edit: looks like it didn't register the damage done to Blackwing Corruptor by the Wrath (still had 4 hp after it). Guess that makes it a syncing problem?

I want to report a bug for V122.5SE.
I don't know how to submit the log but this bug is pretty straightforward.
Every time when enemy's Sludge Belcher dies, the bot fails to recognize the remaning 1/2 taunt that spawns, and tries to go face, which obviously does not work because of the taunt. It keeps clicking on the enemy face until it ropes out.