AI Work/Combat Prediction
Post MTG Forge Related Programming Questions Here
Moderators: timmermac, Agetian, friarsol, Blacksmith, KrazyTheFox, CCGHQ Admins
22 posts
• Page 2 of 2 • 1, 2
Re: AI Work/Combat Prediction
by Sloth » 28 Feb 2011, 16:55
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.
Regarding the canCauseDamage variable: I tested (and improved) the filter for creatures that won't deal damage and it works fine.
-

Sloth - Programmer
- Posts: 3498
- Joined: 23 Jun 2009, 19:40
- Has thanked: 125 times
- Been thanked: 507 times
Re: AI Work/Combat Prediction
by friarsol » 28 Feb 2011, 18:14
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.
Edit: Next turn he attacks with a 1/1 in the same situation. They must not be considering the first strike in this case.
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
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
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: AI Work/Combat Prediction
by ZzzzSleep » 28 Feb 2011, 23:24
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.
Re: AI Work/Combat Prediction
by Sloth » 01 Mar 2011, 20:25
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?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.Not sure if he thought he was going to trade, or what the plan was. But it didn't work.
- Code: Select all
3 = ai aggression
Normal attack
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
-

Sloth - Programmer
- Posts: 3498
- Joined: 23 Jun 2009, 19:40
- Has thanked: 125 times
- Been thanked: 507 times
Re: AI Work/Combat Prediction
by friarsol » 02 Mar 2011, 03:09
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 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?
- friarsol
- Global Moderator
- Posts: 7593
- Joined: 15 May 2010, 04:20
- Has thanked: 243 times
- Been thanked: 965 times
Re: AI Work/Combat Prediction
by jeffwadsworth » 02 Mar 2011, 05:48
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.
- jeffwadsworth
- Super Tester Elite
- Posts: 1172
- Joined: 20 Oct 2010, 04:47
- Location: USA
- Has thanked: 287 times
- Been thanked: 70 times
Re: AI Work/Combat Prediction
by Masher8 » 02 Mar 2011, 16:42
No problem. Real life is preventing me doing anything on this at the moment.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.
- Masher8
- Posts: 18
- Joined: 05 Feb 2011, 13:57
- Has thanked: 0 time
- Been thanked: 0 time
22 posts
• Page 2 of 2 • 1, 2
Who is online
Users browsing this forum: No registered users and 14 guests