Two Noobie Questions

Page 3 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Archived from groups: rec.games.trading-cards.magic.rules (More info?)

Sentinel <robbuchanan@hotmail.com> wrote:

> But, if the PS had fired first and the CS boosted in response, the spong
> would still be alive. Logical?

While the "stack" does not "start" the way batches used to (it's always
there, it's just empty most of the time), you got everything else right.

- ∞
 
Archived from groups: rec.games.trading-cards.magic.rules (More info?)

On Tue, 1 Feb 2005, Sentinel wrote:

> Hopefully the last query - would someone mind checking this situation?
>
> If I had a 1/1 creature token (spong) and a Civic Guildmage (Creature: G,[T]
> to give target creature +0/+1) (CS):
>
> I tap the CS to give my spong 0/+1 (a stack starts

The stack was always there. It just stops being empty.

> and the ability goes on
> it) and my opponent had a Prodigal Sorcerer (PS) & taps it to zap the spong
> (PS's damage ability goes on top of stack) - if both players pass priority,
> the spong would take the damage (and die). If both players pass priority
> again, the CS effect wouldn't have a legal target and would dissipate.

"be countered on resolution" that is.

> But, if the PS had fired first and the CS boosted in response, the spong
> would still be alive. Logical?

I think you understand it now.

--
David
 
Archived from groups: rec.games.trading-cards.magic.rules (More info?)

Keith Piddington <uj551@vtn1.victoria.tc.ca> wrote:
>Brings up a question that has bugged me for years...
>
>: Note that some
>: abilities cause a source to do something (for example, "Prodigal
>: Sorcerer deals 1 damage to target creature or player") rather than the
>: ability doing anything directly. In these cases, any activated or
>: triggered ability that references information about the source will
>: check that information when the ability resolves, or will use the
>: source's last known information if it's no longer in play.
>
>Does *not* fit perfectly. Why, if an ability becomes independent
>once activated/triggered, is it able to refer back to its source
>for any reason after being a/t'ed? To be truly independent, and
>to follow the logic of the first parts of this rule, any and all
>information regarding the ability (damage colour, source type,
>etc., etc.) should be locked in once it gets onto the stack.
>Changing the source should not affect the ability any more than
>changing the ability affects the source.

Changing the source doesn't affect the ability or its text. However, if the
effect _tells a source to do something_, the effect gets its information from
the game on resolution (413.2f, not the same rule you're looking at here)...
so gets its information -about- the source that's dealing the damage then. It
doesn't in any way "lock in what the source referred to in the effect looks
like on announcement". [Same for its own source, by the way.]

So if the source that the effect will tell to deal the damage "looks different"
by resolution time, it's the source-as-it-looks-now that the damage comes
from, not the source-as-it-was-back-then.

Now if the source -goes missing- in between, there is no information about
it available -right now-. In this case, the game says "Well, when last we saw
Our Hero, he looked like -this-" - this is where "last known information"
comes in. If he changed how he looked and then left play? How he looked when
he left play is used.

>Why are removal of source and change to source treated differently?

They're not, not as such. In both cases, the most recent information is used.
But if the source is still there, that's "the CURRENT information about it",
while if the source isn't there any more, that's "the last known information
we had before it vanished".

>An example of the difference, using good ol' Tim:
>
>Version 1:
>A: Tap PS for 1 point damage targeting Order of Leitbur (2/1 pro-
>black). Assume nothing else relevant in play except mana sources.
>B: Cast Terror targeting PS. All pass.
>Terror resolves, PS goes to graveyard.
>PS ability resolves, O-of-L takes 1 point damage, dies, and goes to
>graveyard.

Right. 1 point of damage from a blue 1/1 Wizard creature A controlled ... not
"1 point of damage from a blue creature card in A's graveyard".

>Version 2:
>A: tap PS for 1 point damage targeting Order of Leitbur, as above.
>B: cast Deathlace targeting PS. All pass.
>Deathlace resolves, PS becomes black.
>PS ability tries to resolve but as source is now black, damage is
>now black, O-of-L has pro-black, nothing happens.

Right. In this case it doesn't matter where the damage is from, the -ability-
is now from a black source, and can't target a creature with pro-black. The
ability gets countered and has no effect at all - it never even tries to deal
the damage.

>What is the rationale or logic for treating removal and change
>differently like this?

What "differently"? Both are using the latest available information about
the source.

> In version 2, changing the source to
>black after the ability has been launched should not affect
>it *if the ability is truly independent*. (this is the intuitive
>way, as per the first sentence of 402.6.)

The ability -is- independent. BUT pro-black does not ask about the ABILITY,
it asks about the SOURCE OF the ability. The ability doesn't have any
characteristics at all other than its text; it is not a "black ability",
a "Wizard ability", a "creature ability", etc. It's an ability _from_ a
black 1/1 Wizard creature... and if where the ability is FROM changes, then
where the ability is from _changes_.

>I know I'm not putting this very clearly; I'm hoping you
>understand my confusion here.

I think I know where it's coming from; it's not an uncommon problem,
conceptually. You just have to realize that the ability itself is not "a
blue ability", and the damage the ability makes is not 'blue damage'. Rather,
both are "from a blue source"... and thus get to track what happens to the
source, in a fairly natural manner.

Dave
--
\/David DeLaney posting from dbd@vic.com "It's not the pot that grows the flower
It's not the clock that slows the hour The definition's plain for anyone to see
Love is all it takes to make a family" - R&P. VISUALIZE HAPPYNET VRbeable<BLINK>
http://www.vic.com/~dbd/ - net.legends FAQ & Magic / I WUV you in all CAPS! --K.
 
Archived from groups: rec.games.trading-cards.magic.rules (More info?)

<snip excellent thread>

I wish I'd read that before I posted the "Order of things" post.

So, to answer my own query in the aforementioned thread:

Player A announces the lava burst (and pays the cost!). Passes priority to
Player B.

Player B can then boomerang Player A's lands all he likes, the costs have
been paid.

Player B passes.

Player A passes.

Boom goes Player B, lava bursted to the Nine Hells.

<state based effect - Player B loses. End of game>


Right?
 
Archived from groups: rec.games.trading-cards.magic.rules (More info?)

On Mon, 31 Jan 2005 16:43:52 -0600, "Gene P." <alcore@uurth.com>
wrote:

>On Mon, 31 Jan 2005, Sentinel wrote:
>
>>Thanks for everyone's help on this! I've given one more simple example below
>>to see if I've got it yet - could someone 'mark' for me?
>>
>>Player A taps Prodigal Sourcerer to deal 1 damage to Player B's Prodigal
>>Sourcerer (PS), so the damage effect enters the stack.
>>
>>Player B takes priority & returns the favour by tapping his PS to deal 1
>>damage to Player A's PS, so the damage effect is the next on the stack.
>>
>>Both players pass priority so the last effect that entered the stack deals
>>one damage and kills Player A's PS ('cos the stack is L I F O).
>>
>>Both players pass priority again so the first effect that went into the
>>stack takes effect and deals one damage and kills Player B's PS.
>
>The Prodigal Sorcerer Oracle text says the "Prodigal Sorcerer deals one
>point of damage to target creature or player".
>
>Since the PS must exist to do the damage, the effect is that Player B's PS
>kills player A's PS before it can do the damage. When the activated
>ability of player A's PS resolves, the PS that is supposed to do the
>damage will no longer exist and the effect will fizzle.

Nope. You ignore the Silver Rule of Magic, which says, effectively
"Once an ability is on the stack, removing or destroying the source of
that ability does NOT remove the ability from the stack".

At one point, both "deal 1 damage to <target>" abilities are on the
stack. They exist independently of the Prodigal Sorcerors which
generated them. The ablities can be countered (using, say, "Stifle"),
or the target of a targetted ability can be made an illegal target, or
the game can end before the abilities resolve, but that's about it.

Analogy: one I light the fuse on the dynamite, killing me won't put
the fuse out.