Collectible Card Game Headquarters

Currently MagicTargetChoice is functioning as a string replacement for groovy code.

As the TargetFilterFactory has expanded, would it not make more sense to use the constructors in groovy code?

Code: Select all

MagicTargetChoice.Negative("target spell")

instead of

Code: Select all

MagicTargetChoice.NEG_TARGET_SPELL

for example.

This would allow for a broader range of target choices than current, as the target filters are far more comprehensive. The only downside I see so far is that they wouldn't be caught when running in dev mode if the target filters don't yet exist.