Untap cost and summoning sickness

[thefiremind]

I have never tried to code a card with the cost... until now. I discovered that DotP2013 supports it partially: it requires the permanent to be tapped, which is OK, but it ignores another rule...

The "summoning sickness" rule applies to . If a creature with an ability hasn't been under your control since your most recent turn began, you can't activate that ability. Ignore this rule if the creature also has haste.

So if we want to code a creature with the cost, we need to manage the summoning sickness manually.

Let's quote the rules for reference:

The term “summoning sickness” is an informal term which describes a creature’s inability to attack or to use activated abilities that include the tap symbol when it has come under a player’s control since the beginning of that player’s most recent turn. See rule 302.6. See also Haste.

This is how I would do it:

Code: Select all

  <TRIGGERED_ABILITY internal="1">
    <TRIGGER value="ZONECHANGE_END" simple_qualifier="self" to_zone="ZONE_IN_PLAY" />
    <RESOLUTION_TIME_ACTION>
    ObjectDC():Set_Int(1, 0)
    </RESOLUTION_TIME_ACTION>
  </TRIGGERED_ABILITY>
  <TRIGGERED_ABILITY internal="1">
    <TRIGGER value="CONTROLLER_CHANGED" simple_qualifier="self" />
    <RESOLUTION_TIME_ACTION>
    ObjectDC():Set_Int(1, 0)
    </RESOLUTION_TIME_ACTION>
  </TRIGGERED_ABILITY>
  <TRIGGERED_ABILITY internal="1">
    <TRIGGER value="BEGINNING_OF_STEP" simple_qualifier="controller">
    return EffectController():MyTurn() ~= 0 and MTG():GetStep() == STEP_UNTAP
    </TRIGGER>
    <RESOLUTION_TIME_ACTION>
    ObjectDC():Set_Int(1, 1)
    </RESOLUTION_TIME_ACTION>
  </TRIGGERED_ABILITY>

I'm using ObjectDC's register #1 as a flag that says "no more summoning sickness". It's set to 0 when the creature enters the battlefield or changes controller, and it's set to 1 when the creature's controller starts a turn.

The ability will have:

Code: Select all

    <COST type="UntapSelf" />
    <AVAILABILITY>
    return ObjectDC():Get_Int(1) == 1 or
    Object():GetCurrentCharacteristics():Characteristic_Get( CHARACTERISTIC_HASTE ) ~= 0
    </AVAILABILITY>

I can't see any flaw in this, but if you see one, please tell me.