These two cards have nothing in common, since
Kessig Wolf Run can produce mana, any activated ability need tapped on a card that can produce mana will cause error, usually, such as
Gavony Township, we add
- Code: Select all
<AVAILABILITY>
return EffectController():CanPayManaCost("{3}{G}{W}")
</AVAILABILITY>
to solve this problem, can pay mana cost equal to ability mana cost plus 1, but it's not valid for
Kessig Wolf Run, because of this
X.
RiiakShiNal wrote:For
Kessig Wolf Run wouldn't you use:
- Code: Select all
<COST type="Mana" mana_cost="{X}{R}{G}" />
then use the GetEffectX()?
Otherwise you'll need to determine the max cost a player can afford using something like:
- Code: Select all
local nMaxX = 0
while (EffectController():CanPayManaCost("{"..nMaxX.."}{R}{G}") do
nMaxX = nMaxX + 1
end
-- Adjust downward because we went over what can be afforded.
nMaxX = nMaxX - 1
Then ask the player a numeric question using something like:
- Code: Select all
EffectController():BeginNewNumericalChoice()
EffectController():AddNumericalChoiceAnswer( nMaxX )
EffectController():AskNumericalChoiceQuestion( "<CARD_QUERY here>" )
and then make them pay it with PayManaCost. Getting the amount using EffectController():GetNumericalChoiceResult().
This way is no problem in 2013, but now we have lost TapLand(), I have tried and EffectController():PayManaCost("{.. EffectController():GetTotalMana()..}") not always work fine, seem to conflict between PayManaCost and GetNumericalChoiceResult.
I guess because TapLand only consider the current state: lands are tapped or not, but PayManaCost seem to get the state before starting ability, so even
Kessig Wolf Run has been tapped by ability tap cost, it still be considered one of the mana sources.
Posted: 30 Jul 2013, 15:51
):