Archived from groups: rec.games.trading-cards.magic.rules (
More info?)
phil@ideastakingshape.co.uk <phil@ideastakingshape.co.uk> wrote:
>This came up ina multiplayer game
>Player A : big fat creature
>Player B : A creature that can tap other creatures
>Player C : Propoganda.
Okay. Let me check something: okay, Propaganda only protects C in this case
("creatures can't attack _you_ unless".)
>Player A wants to storm over and clobber player C with the big fat
>creature, but he doesn't want to risk player B tapping it and stopping him.
Okay. (Note that the current rules are Weird about when you say who you are
attacking; I am attempting to point this out to them and get that Fixed.)
>So it becomes important when player A pays the propoganda costs. Does
>he declare attackers first, then pay. Or pay then declare attackers.
He pays _as part of_ declaring attackers; he pays at a time that B (and
everyone else too) does not have priority at all and can't do something.
308.2* goes through the sequence: in order, he chooses what to attack with
(or not to attack at all) and checks legality of the attacking set, makes bands
if any, taps the creatures, determines and pays costs to attack if any, then
the creatures actually become attackers.
At no time during this does B get priority; this is being done as step 2 of
combat, declare-attackers step, starts, and none of this uses the stack at all
in any way, so none of it can be 'responded to'.
>Should the case be pay, then declare, could player A pay the costs more
>than once,if he needed to dump mana?
Nope. He pays the costs or doesn't; you can NEVER "pay a cost multiple times
at once".
> I assume that whenever he pays
>the costs, player A has the option to not attack, or to attack player
>B. Would this be right, within the 'there are no rules for multiplayer'
>umbrella?
At present, yes (almost). There is, as alluded to above, a rule (306.3) that
says active player is the 'attacking player' during the -entire- Combat phase,
and nonactive player is the "defending player", that's been there quietly
since the first 8th Edition rulebook - but, clearly, if no attackers have
been declared yet, there can't be a 'defending player' -or- an 'attacking
player'. Players don't attack other players; creatures attack players...
It is unclear how 306.3 would extend to multiplayer, since most multiplayer
games operate under either a "pick who you'll attack as you declare attackers"
paradigm or a "who you can attack is determined by where you're sitting in
relation to them" paradigm for the structured ones. But, as far as I can
tell, nothing currently in the rules says "A has to pick who he will attack
before he actually declares attackers".
However, by the time A pays costs, A has already chosen his attackers and,
presumably, who they will attack, so your assumption is not totally correct;
A will have chosen who he's attacking before he pays _costs_ to attack - but
B can't interfere at any time in between those two - no "Okay, you're
attacking him with that? Then I use my Icy Manipulator on it and tap it before
it can attack" is allowed there. B can, of course, foresee that A wants to
attack C with Mr.Big, and tap Mr.Big during beginning-of-combat step, before
attackers are ever declared at all - but in that case A can't pick Mr.Big to
attack with as declare-attackers step starts.
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.