MagicTargetChoice
Posted: 31 May 2014, 13:43
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?
instead of
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.
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
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.