fixed issue 632,633 ...
converted {t} into a extra cost. almost all original code to handle it outside remains intact, i plan on slowly migrating to just using the cost...but even just what i changed was a massive headache...anyways as a cost you wont ever have an random bugs where cards don't tap when the ability had {t} in its cost.
while i was at it, i added {q} untap cost.
This commit is contained in:
@@ -110,7 +110,24 @@ public:
|
||||
MillExileCost(TargetChooser *_tc = NULL);
|
||||
virtual int doPay();
|
||||
};
|
||||
|
||||
//tap cost
|
||||
class TapCost: public ExtraCost{
|
||||
public:
|
||||
TapCost();
|
||||
virtual int isPaymentSet();
|
||||
virtual int canPay();
|
||||
virtual int doPay();
|
||||
virtual TapCost * clone() const;
|
||||
};
|
||||
//untap cost
|
||||
class UnTapCost: public ExtraCost{
|
||||
public:
|
||||
UnTapCost();
|
||||
virtual int isPaymentSet();
|
||||
virtual int canPay();
|
||||
virtual int doPay();
|
||||
virtual UnTapCost * clone() const;
|
||||
};
|
||||
//tap other cost
|
||||
class TapTargetCost: public ExtraCost{
|
||||
public:
|
||||
|
||||
Reference in New Issue
Block a user