Archived from groups: rec.games.trading-cards.magic.rules (
More info?)
Daniel W. Johnson wrote:
> Hylander <john.gagon@gmail.com> wrote:
>
> > So does it go like this then?
> >
> > Grinding station spell on stack
> > resolved Grinding station in play.
> > Stack empty.
> >
> > Trigger on stack.
> > (Trigger checks here for artifact coming into play.) YES.
> > Tap goes on stack
> > Mill effect resolves
> > Trigger resolves untapping Grinding Station.
> >
> > But I was thinking it was like this:
> >
> > Grinding station spell on stack
> > resolved Grinding station in play.
> > Stack empty.
> >
> > Trigger on stack.
> > Tap goes on stack
> > Mill effect resolves
> > Trigger resolves
> > (Trigger first checks artifact just coming into play.) NO.
> > Trigger doesn't resolve/fizzles not untapping Grinding Station.
>
> It goes like this:
>
> 1. You get priority and play Grinding Station. The cost is paid
using 2
> mana obtained in an unspecified way.
> 2. You get priority and pass.
> 3. Opponent gets priority and passes.
> 4. The top object on the stack (the spell played in step 1) resolves.
> Grinding Station comes into play. This triggers its comes-into-play
> ability.
> 5. You would get priority, but there is a triggered ability to put on
> the stack. You put the "Whenever an artifact comes into play, you
may
> untap Grinding Station." ability on the stack.
> 6. You get priority and play the "T, Sacrifice an artifact: Target
> player puts the top three cards of his or her library into his or her
> graveyard." ability of Grinding Station. You choose your opponent as
> the target, and you pay the cost by tapping Grinding Station and
> sacrificing an artifact (which presumably was already in play before
all
> this started).
> 7. You get priority and pass.
> 8. Opponent gets priority and passes.
> 9. The top object on the stack (the ability played in step 6)
resolves.
> Opponent puts the top three cards of his or her library into his or
her
> graveyard.
> 10. You get priority and pass.
> 11. Opponent gets priority and passes.
> 12. The top object on the stack (the ability put there in step 5)
> resolves. You decide to untap Grinding Station. You untap Grinding
> Station.
> 13. You get priority ....
Wow. Very detailed. And it appears very accurate too so thank you.
> > Is there a rule for when a trigger is checked.. I thought it might
need
> > to be checked when it resolves like other spells check for targets.
Ah, someone got me straight that I might have been remembering "if" or
"conditional" triggers when I read the rulebook a month ago.
> 404. Triggered Abilities
>
> 404.1. A triggered ability begins with the word "when," "whenever,"
or
> "at." The phrase containing one of these words is the trigger
condition,
> which defines the trigger event.
>
> 404.2. Triggered abilities aren't played. Instead, a triggered
ability
> automatically "triggers" each time its trigger event occurs. Once an
> ability has triggered, it goes on the stack the next time a player
would
> receive priority. See rule 408.1, "Timing, Priority, and the Stack,"
and
> rule 410, "Handling Triggered Abilities."
>
> Your thought would lead to something like:
>
> 1. You get priority and play some artifact spell. (Grinding Station
is
> already in play and tapped.) The cost is paid using mana obtained in
an
> unspecified way.
> 2. You get priority and pass.
> 3. Opponent gets priority and passes.
> 4. The top object on the stack (the spell played in step 1) resolves.
> The artifact comes into play. This triggers Grinding Station's
second
> ability.
> 5. You would get priority, but there is a triggered ability to put on
> the stack. You put the "Whenever an artifact comes into play, you
may
> untap Grinding Station." ability on the stack.
> 6. You get priority and pass.
> 7. Opponent gets priority and passes.
> 8. The top object on the stack (the ability put there in step 5)
tries
> to resolve. The artifact is no longer coming into play (that having
> completed way back in step 4), so the ability is actually countered.
>
> This would kill ALL event-based triggers.
Yes. I see what you mean...it's just interesting that when it resolves,
the "checking" has already occured and there is no "condition" or
"target disappearance" to check (unless I suppose there was a target in
the trigger) in which case it might "fizzle".
> > Is there a rule for how long or when a trigger's condition is true?
> > Perhaps I'm making it just a little harder than it is drawing
analogy
> > perhaps falsely regarding target disappearance etc. ie: Like a
> > boomeranged O-Stone. Triggers happen before instants from what I
can
> > tell as well and when someone has two triggers out, they decide.
ie:
> > Cowardice Horobi, Death's Wail.
>
> I'm not sure what you mean by a "boomeranged O-Stone". Using
Boomerang
> on an Oblivion Stone in response to its "4, T: Put a fate counter on
> target permanent." ability would not interfere with that ability at
all.
No, Sacrifice O-Stone. The more "critical" effect of that card. Sorry,
that was ambiguous. If the Boomerang bounces it in response to sac, it
is a bit different than Timmy lobbing damage (the example I've read
about in these rules forums), in the sense that the O-stone needs to
have it's target (self) to sac I think. Or am I wrong there? I just
thought that in a classic match I saw where two pros were
playing....ie: MUC vs T&N (type II). I saw boomerang sided in for the
O-stone and the O-stone bounced when it was going off. BTW, in the
Timmy case, I believe "prevent damage" and "stifle" effects are the
only effects that would negate timmy damage (Prodigal Sorcerer). ie:
his effect goes on the stack. With O-stone, it's effect might go on the
stack and I don't think paying costs is exempt like tapping for mana is
it? I forget. Perhaps it is.
H
> --
> Daniel W. Johnson
> panoptes@iquest.net
> http://members.iquest.net/~panoptes/
> 039 53 36 N / 086 11 55 W