Re: Card AI (Improvements) Requests
Good job on the fix, Excessum! This looks like a reasonable and valid change, I appreciate your effort to make this logic better! 
- Agetian
- Agetian
High Quality Resources for Collectible Card Games and Home of the CCGHQ Team
https://www.slightlymagic.net/forum/
https://www.slightlymagic.net/forum/viewtopic.php?f=26&t=7032
There is currently no code to check for useless/harmful creatures and I doubt that there will ever be a way to solve this. The 0/2 that pings for 2 might still be saved to chump at a critical moment rather than at the first opportunity. Alternatively, the AI might have some way to remove the negative enchantment/equipment/etc. and "choose" not to waste the creature. When abilities like lord-effects, Eidolon of Blossoms triggers and Kird Chieftain activations are counted in, it becomes even messier. Even if the game-state rewinding code is implemented, all this requires long-term thinking which AIs are naturally terrible at (ie. decision-tree explosion).Agetian wrote:The AI does not try to get rid of useless+harmful cards on its part of the battlefield in any way - for instance, it won't consider using its 2/4 creature to chump-block after it was enchanted with Stab Wound and thus became 0/2 that deals 2 damage to its controller every upkeep.
- Agetian
Yeah, makes sense, it's indeed a pretty difficult decision for an AI to take.excessum wrote:There is currently no code to check for useless/harmful creatures and I doubt that there will ever be a way to solve this. The 0/2 that pings for 2 might still be saved to chump at a critical moment rather than at the first opportunity. Alternatively, the AI might have some way to remove the negative enchantment/equipment/etc. and "choose" not to waste the creature. When abilities like lord-effects, Eidolon of Blossoms triggers and Kird Chieftain activations are counted in, it becomes even messier. Even if the game-state rewinding code is implemented, all this requires long-term thinking which AIs are naturally terrible at (ie. decision-tree explosion).Agetian wrote:The AI does not try to get rid of useless+harmful cards on its part of the battlefield in any way - for instance, it won't consider using its 2/4 creature to chump-block after it was enchanted with Stab Wound and thus became 0/2 that deals 2 damage to its controller every upkeep.
- Agetian
The AI is only supposed to "waste" tricks pre-combat if it gets said creature(s) into combat (ie. Giant Growth a 0/4 that would otherwise stay back). There is no support for the AI to "see" this possibility and then attack with the 0/4 and cast the trick in combat.gecktrix wrote:AI seems to blow their combat tricks before attackers are announced. Is this a limitation of Forge or is there plans to improve this?
This card is listed as not playable by the AI. What deck are you playing against that has it?kestell wrote:Currently it just uses the second ability in it's upkeep step and it ruins its game.
mono green devotion in constructed.friarsol wrote:This card is listed as not playable by the AI. What deck are you playing against that has it?kestell wrote:Currently it just uses the second ability in it's upkeep step and it ruins its game.
Just witnessed AI tap out for Rush of Battle precombat on lone non-warrior 2/3 while I was tapped out with a 2/2 as a blocker. AI had a 4 drop as well as a 2 drop in hand. I believe the AI should prioritize playing creatures over unnecessary combat tricks.excessum wrote:The AI is only supposed to "waste" tricks pre-combat if it gets said creature(s) into combat (ie. Giant Growth a 0/4 that would otherwise stay back). There is no support for the AI to "see" this possibility and then attack with the 0/4 and cast the trick in combat.gecktrix wrote:AI seems to blow their combat tricks before attackers are announced. Is this a limitation of Forge or is there plans to improve this?