Community

Dec 7, 2012 -- 11:35AM, DroneOn wrote:

Dec 7, 2012 -- 11:32AM, thedevilwuster wrote:

So, does it check for Fume and Crippling only when you're playing against OD, or does it happen all the time? I haven't used the card.

It checks for there being a counter whenever you cast a B or W spell.  Probably because it would be messy to code it to only check if there's a counter on it if there's a counter on it.  Much simpler to just code it to always check.

In fact, think of this situation; you have Hatchling out with no counters on it.  You cast a spell.  In response, your opponent uses Fume Spitter.  Yes, it's a dumb play, but it's a play that could happen and justifies having it check every time.

It really wouldn't be that difficult to check for counters before adding to the stack. I don't claim to know how they coded this thing, but something as simple as:

if(vHatchling.hasCounters){
   theStack.push(vHatchling.ability);
}

They just didn't do it because it works as is and it's pretty evident that they are lazy.


Edit: I just read the last part of your post and that actually makes sense. Maybe it was actually thought out. I doubt it though.

Edit Edit: While it makes sense, it still doesn't justify it. Why would anyone interupt the ability to put a counter on your dude just so the ability can remove it?

Dec 7, 2012 -- 11:35AM, DroneOn wrote:

In fact, think of this situation; you have Hatchling out with no counters on it.  You cast a spell.  In response, your opponent uses Fume Spitter.  Yes, it's a dumb play, but it's a play that could happen and justifies having it check every time.

Even if the play itself isn't so dumb (perhaps the Fume Spitter is the target of an Unmake) the timing certainly is.  The sequence should be this...
Unmake goes on stack, targeting Fume Spitter
Hatchling ability triggers (twice, in fact)
**Wait for Hatchling ability to resolve and remove nothing**
Return to the stack, Unmake is still waiting for responses
Now sacrifice Fume Spitter to put a counter on the Hatchling


To find a situation that matters it'd have to be some difference between responding to a counterless Hatchling's own ability vs responding to the spell that set off that Hatchling ability.

Now someone might say that a player is allowed to be an idiot and respond at the wrong time on the stack.  To which I counter that this game protects people from doing silly things in other situations.  Best example I can give it that I can't tap all my lands during my upkeep.