Collectible Card Game Headquarters

I had to change some of your code Masher, because it caused the untap triggers to trigger, when the AI was planning the attack.

Regarding the canCauseDamage variable: I tested (and improved) the filter for creatures that won't deal damage and it works fine.

Combat prediction is looking better and better. Keep up the good work.

I just noticed a weird attack today. AI has a 2/2 and I was at 2 life. I have a 2/1 First Striker. But AI attacks anyway.

Code: Select all

3 = ai aggression
Normal attack


Not sure if he thought he was going to trade, or what the plan was. But it didn't work.

Edit: Next turn he attacks with a 1/1 in the same situation. They must not be considering the first strike in this case.

Code: Select all

2 = ai aggression
Normal attack
0
Adding 2 damage to Goblin Matron


With these changes, is the AI taking vigilance into account? In the Feb 19 release, the AI was low on life, but declined to attack with a vigilant flying creature that I was unable to block.

friarsol wrote:Combat prediction is looking better and better. Keep up the good work.

I just noticed a weird attack today. AI has a 2/2 and I was at 2 life. I have a 2/1 First Striker. But AI attacks anyway.

Code: Select all

3 = ai aggression
Normal attack


Not sure if he thought he was going to trade, or what the plan was. But it didn't work.

Edit: Next turn he attacks with a 1/1 in the same situation. They must not be considering the first strike in this case.

Code: Select all

2 = ai aggression
Normal attack
0
Adding 2 damage to Goblin Matron


I was unable to reproduce this. I used AI Savannah Lions against my Coiled Tinviper and even at low life (me), the AI didn't attack into them. How many creatures did the AI have?

Sloth wrote:I was unable to reproduce this. I used AI Savannah Lions against my Coiled Tinviper and even at low life (me), the AI didn't attack into them. How many creatures did the AI have?

That was the only one. AI was at a bunch of life (like 16) and I had a Vampire Hexmage and something that was tapped that I was attacking with (don't remember what it was).

Sloth wrote:I had to change some of your code Masher, because it caused the untap triggers to trigger, when the AI was planning the attack.

Regarding the canCauseDamage variable: I tested (and improved) the filter for creatures that won't deal damage and it works fine.

Haha. I was wondering what the heck was going on while testing Mesmeric Orb...

Sloth wrote:I had to change some of your code Masher, because it caused the untap triggers to trigger, when the AI was planning the attack.

Regarding the canCauseDamage variable: I tested (and improved) the filter for creatures that won't deal damage and it works fine.

No problem. Real life is preventing me doing anything on this at the moment.