Craft-related AI issues
- Dominant language
- Java
- Stars
- 2.7k
- Forks
- 1.1k
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 158
Description
1. AI can currently pay Craft costs with XMin1 without exiling any creatures. In addition to this being a "cheating" problem, the AI should generally "want" to pay as much as makes sense for things like Saheeli's Lattice // Mastercraft Raptor. Exiling nothing in this case results in paying 4 R for a vanilla 0/4. I've got these cards all marked RemoveDeck:All for now.
I don't think this creates any new problems for existing cards that were refactored from XCantBe0 as a CostPart or with param `XCantBe0$` to XMin. In limited testing I didn't run across any AI cheating with old cards that were refactored. Seems more like the AI just won't play those effects? Corpseweft seems a bit more straightforward than Craft, but it's marked RemoveDeck:All. 😅 I can't seem to create a board state where AI will want to activate the Arcee, Acrobatic Coupe ability where it removes X counters.
For Craft abilities, part of the equation may be the "new" (at least new for CostExile?) ability to exile from different zones. My thought is the AI should generally (no Graveyard/reanimator theme) exile as many as possible from the graveyard to pump up the resulting effects. If the deck does have a Graveyard/reanimator theme, then the AI should probably get rid of as many low-cost / less useful things as it can? Based on the board state?
2. There is currently no support in AiCostDecision.visit(CostExile) for the new requirements on Fabrication Foundry activated ability and Eye of Ojer Taq craft ability. There are similar targeting requirements for the AI that exist, but I couldn't sort out how to port those over.
Contributor guide
Assessment
This issue has not been assessed yet.