Page 1 of 1

StaticAbilityContinuous

PostPosted: 27 Mar 2012, 03:12
by slapshot5
In StaticAbilityContinuous, is there a reason we call directly to CardFactoryUtil.xCount instead of using the AbilityFactory.calculateAmount wrapper?

This prevents us from using things like Remembered$CardCounters.CHARGE with the StaticEffect. I change it like this to do some testing:

Code: Select all
//CardFactoryUtil.xCount(hostCard, hostCard.getSVar(setT));
AbilityFactory.calculateAmount(hostCard, setT, null);
and it works (for my purposes - implementing Gutter Grime).

Does anyone more familiar here know if this was done for a reason or if changing to calculateAmount would break other things?

Thanks,
slapshot5

Re: StaticAbilityContinuous

PostPosted: 28 Mar 2012, 06:13
by Sloth
I think there should be no problem.

Maybe xCount and calculateAmount could be merged/reorganized now that there is no reason not to use calculateAmount.