Re: Restrictions for Card.isValidCard

Posted:
16 Jun 2011, 14:19
by slapshot5
In the interest of expanding isValidCard to handle things like the Echoing cards (ex. "Destroy target enchantment and all other enchantments with the same name as that enchantment."), what needs to be done? Looks to me like we just pass in the AbilityFactory object when called from an AF, and null otherwise. Then, in hasProperty, we check for null, get the targets, then check the name.
Seem reasonable?
-slapshot5
Re: Restrictions for Card.isValidCard

Posted:
16 Jun 2011, 14:27
by friarsol
slapshot5 wrote:In the interest of expanding isValidCard to handle things like the Echoing cards (ex. "Destroy target enchantment and all other enchantments with the same name as that enchantment."), what needs to be done? Looks to me like we just pass in the AbilityFactory object when called from an AF, and null otherwise. Then, in hasProperty, we check for null, get the targets, then check the name.
Seem reasonable?
Are we passing in the AF or the SA?
Re: Restrictions for Card.isValidCard

Posted:
16 Jun 2011, 20:03
by slapshot5
Niether right now. Just (String, sourceCard, controller).
I suppose passing in the SA would be better.
-slapshot5