Yep, maybe I didn't got it first time, but my point of view it this one... If you plan on using both LB and Kamahl to kill a 6/6, AI must plan both moves and perform then sequentially. Problem is, AI is currently casting the LB and then "forgets to finish the job". It may seem boring, but you as a player wouldn't ever think of doing that move unless you target the same 6/6 with Kamahl afterwards. As some people has pointed, looks pretty dumb for the AI to cast a LB on a 4/4 and then leaving the monster alone.wololo wrote: 1) There was a strong misunderstanding here. I wasn't saying casting LB on the Kahmal. I was saying using Both a LB AND Kamahl to deal a total of 6 damages in one turn to a 6/6 creature, sorry if I wasn't clear on that. I don't know why an experienced Magic player wouldn't use several damage cards in a row to kill one creature, if this is needed. If you have 2 lightning bolts, or a lightning Bolt + Kamahl, you can kill a 6/6, that's my point. I agree this does not happen very often, but I don't understand why we would want to completely remove this possibility. I still believe that knowing the AI will never cast a lightning bolt if it knows it can't "one shot kill" will be pretty obvious and fairly boring to most players. Again, we can tweak the values, but making this possibility entirely 0 sounds extremely weird to me. From a pure logical point of view, reducing the life of an enemy creature should not be considered as a "wrong" move, which is what "0 chances of doing it" means to the computer.
Here's the failure, AI doesn't take into account the EoT full healing. That's why AI (at least for now) should always consider partial damage as a "wrong move". Of course, this is mainly a "patch" (that I'm pretty sure will highly improve AI efficiency) till "finish the job targeting" is coded somehow.