AbilityFactory TODO list

[friarsol]

A note for all the new AFs that are being worked on: Please when you get some time update the Wiki page so the info is a bit more accessible. I know some of the current AFs are a bit behind in their docs, so if you notice something in there that's incorrect feel free to fix it so the next guy can know what's going on.

[friarsol]

And another possible AF: EndGame, which would have three modes: Win, Lose or Draw. I think there are only two cards that can cause the game to Draw. We can hold off on those until we support Draws better.
Loses is mostly Door to Nothingness and Phage the Untouchable
We have a bunch of the the AlternateWinConditions already hard coded, and overall it's a pretty short AF.

[Replika]

Loses would also be needed for the Pact cycle, or the AI's-Doom-Cycle.

[slapshot5]

AF_Animate has the ability to do Memnarch style abilities ("Target permanent becomes an artifact in addition to its other types.").

The AI for AF_Animate currently doesn't know what to do with this. I was pondering what the AI should do for these style abilities. It seems like this ability would mostly be for combos. Suggestions for how the AI should use this, or is the AI simply not smart enough at the moment to be able to effectively use these abilities?

-slapshot5

edit: just fixing typo

[ZzzzSleep]

AF_Animate has the ability to do Memnarch style abilities ("Target permanent becomes an artifact in addition to its other types.").

The AI for AF_Animate currently doesn't know what to do with this. I was pondering what the AI should do for these style abilities. It seems like this ability would mostly be for combos. Suggestions for how the AI should use this, or is the AI simply not smart enough a the moment to be able to effectively use these abilities?

-slapshot5

Would it be worth adding a check to see if anything that it controls has a PumpedBy <AnimateType> and if it does animating as many things as possible?

Or if the computer is able to control/destroy <AnimateType> and animate the best card controlled by the opponent, then destroy/control it?

This could be completely useless, I'm just throwing out ideas here.

[slapshot5]

Would it be worth adding a check to see if anything that it controls has a PumpedBy <AnimateType> and if it does animating as many things as possible?

Or if the computer is able to control/destroy <AnimateType> and animate the best card controlled by the opponent, then destroy/control it?

This could be completely useless, I'm just throwing out ideas here.

Your ideas are spot on, but they involve the interaction of two cards, which the computer is very poor at dealing with. The first idea would be easy enough. I'm not sure the second part would be very easy.

-slapshot5

[friarsol]

Yea the second part would be tougher for sure. It involves:

Looking through all available SAs. Sorting through which ones fit the parameters. Throwing out whichever ones can't be activated after the first is activated. Then making sure that second SA which was the whole reason we activated the first SA actually gets played. Unfortunately, our infrastructure is not setup for these type of "planning" moves at this time.

[SoulStorm]

Is anyone contemplating AF_Copy?

[slapshot5]

Is anyone contemplating AF_Copy?

Contemplated as in "I wish we had that." Yes. Volunteering to do it? No.

[slapshot5]

The Win/Lose AbilityFactory is now implemented. Done by Sol I believe.

[slapshot5]

I just submitted an AbilityFactory for "look at target player's hand" type of stuff. Like Glasses of Urza and Lay Bare.

-slapshot5

[friarsol]

The Win/Lose AbilityFactory is now implemented. Done by Sol I believe.

Oh yea. I did those the other day, but only converted Epic Struggle as a sample. In particular, Helix Pinnacle will need some extra work in hasProperty.

[slapshot5]

There is now an AF_Reveal for cards like Impulse and Lead the Stampede.

It is currently of the form: SP$Reveal

I think maybe it should be SP$LookAt and save reveal for cards that have "Reveal the top..."

Thoughts? Other ideas? Maybe Sol's "SP$Peek" would be better? Or would that be better used for something else?

-slapshot5

[friarsol]

There is now an AF_Reveal for cards like Impulse and Lead the Stampede.

It is currently of the form: SP$Reveal

I think maybe it should be SP$LookAt and save reveal for cards that have "Reveal the top..."

Thoughts? Other ideas? Maybe Sol's "SP$Peek" would be better? Or would that be better used for something else?

-slapshot5

I was thinking either "Dig" or "Search" or "Seek" when I was trying to come up with other names aside from "Peek". Since many of these don't actually reveal anything, it's probably better not to be Reveal.

We should have a Reveal flag in this AF so we can combine the two AFs. If the Type we're looking for is not just "Card" that will get Revealed.

[slapshot5]

I think Search is too much like the Tutors. I'm good with Dig.