|
3 years ago ::
Apr 12, 2010 - 5:36PM
#51
|
Date Joined:
Jul 24, 2009
|
i was actually posting that the way to resolve the problem is to make it manditory to declare combat
And we are just telling you that it's not a problem that needs resolving. The active player always has the opportunity to announce combat before he begins tapping attackers. Always. He can do that every time, if he wants to. If he declines that opportunity, then yes he gives up a small amount of advantage to the other player, but it's not like it's detrimental to the other guy either way. Only the attacker is suffering here, and that only happens if he declines to do what he could have done in the first place.
I know..i know....im not fighting for it to be implemented, i just brought it to everyones attention...i can understand based on my first few posts how it may have seemed that i was bothered by the rules in some fashion and wanted them to be changed...i was trying to point something out, and saying the only way for it to never ever happen was to make declaring combat manditory...i know its not the biggest deal ever
|
|
|
|
3 years ago ::
Apr 12, 2010 - 6:46PM
#52
|
Date Joined:
Jun 22, 2008
|
It could be worse. Some people dont allow the tournement shortcut for infinite combos in casual.
My colors and decks
Show
Where's the fun in that?
|
|
|
|
3 years ago ::
Apr 13, 2010 - 6:49AM
#53
|
Date Joined:
Apr 16, 2009
|
so its not an advantage compared to knowing who they want to attack with
I would argue it's not really an advantage at all to see who they want to attack with. Because if the game is rewound to Beginning of Combat, and the opponent takes an action, then the attacker is no longer bound to his choices. You might learn what he MEANT to do in the absence of interference, but you still don't know what he's GOING to do.
At best, the defender gets a small advantage by knowing with certainty that there was an attack planned, so the mana spent to keep someone out is worthwhile. Given that it would normally be fairly obvious if an attack should be coming anyway, this advantage is negligible.
|
|
|
|
3 years ago ::
Apr 13, 2010 - 10:02AM
#54
|
Date Joined:
Apr 12, 2010
|
Thank you for the depth of all your answers. It's only casual play, we're not going to be announcing or giving permission to continue after each phase/step... it was just a quick friendly game, but I guess that's where the problem lies. The real issue I had with Flood, (or any other tap creature card) was that my opponent was using it after knowing what creatures I chose to attack with then backing up the game and tapping said creatures, (he admits to this, and claims its legal play). Thanks again for your heated discussions
|
|
|
|
3 years ago ::
Apr 13, 2010 - 10:28AM
#55
|
Date Joined:
Jul 30, 2004
|
Thank you for the depth of all your answers. It's only casual play, we're not going to be announcing or giving permission to continue after each phase/step... it was just a quick friendly game, but I guess that's where the problem lies.
The real issue I had with Flood, (or any other tap creature card) was that my opponent was using it after knowing what creatures I chose to attack with then backing up the game and tapping said creatures, (he admits to this, and claims its legal play).
Thanks again for your heated discussions 
Bottom line:
As the active player, you're entitled to know whether the guy with Flood intends to use it before announcing which creatures you plan to attack with. If you get explicit agreement that your opponent is ready for you to declare attackers, then he can't back up and change his mind about what/whether to tap.
Even if you do declare attackers and then back up to let him tap stuff, you can change your mind about what (if anything) to attack with after he's tapped some of your potential attackers (the only time you're stuck with your initial declaration is when he doesn't want to back up and do something first).
In a casual game, asking "do you want to tap anything before I attack?" is easy to do, and means he has to decide before knowing which creatures (if any) you intend to attack with.
M:tG Rules Advisor
|
|
|
|
3 years ago ::
Apr 13, 2010 - 10:32AM
#56
|
Date Joined:
Feb 10, 2005
|
i was actually posting that the way to resolve the problem is to make it manditory to declare combat, not that i personally want that, i gave a scenario in the first/second page about how the standard practice of not declaring could lead to a potential(althought be it EXTREMELY rare) case where the defending player could exploit the ruling of backing a player up
I think the thing you missed in this conversation, is that it IS required by the rules to pass priority, and therefore players must be informed when new steps and phases start. But going from your main phase to turning attackers sideways is a SHORTCUT. And the tournament rules say shortcuts are okay because they take the pain out of a strict following of the rules and passing priority all the time. And if an opponent doesn't like your shortcut, you can't do it. And if you did it without asking them, they can have you back up.
I know you don't have a problem with it or whatever, but it's really not that hard to say "Beginning combat," look them in the eye, and then declare attackers. And if that shortcut isn't short enough, well that's the risk you take for using shortcuts of which your opponent might not approve.
|
|
|
|
2 years ago ::
Sep 02, 2011 - 6:41AM
#57
|
|
|
This happend to me once and I pulled out the rule book. 506.4a states "once a creature has been declared as as attacking or blocking creature, spells or abilities that would have kept that creature from attacking or blocking don't remove the creature from combat" and rule 508.1 states in short that declaring attackers does not use the stack. On the flip side, if I declare a blocker and it is removed before combat damage phase, it is still blocked.
|
|
|
|
2 years ago ::
Sep 02, 2011 - 6:49AM
#58
|
|
|
This happend to me once and I pulled out the rule book. 506.4a states "once a creature has been declared as as attacking or blocking creature, spells or abilities that would have kept that creature from attacking or blocking don't remove the creature from combat" and rule 508.1 states in short that declaring attackers does not use the stack. On the flip side, if I declare a blocker and it is removed before combat damage phase, it is still blocked.
You do realize this thread is over a year old?
DCI Level 1 Judge Please autocard: [c ]Skithiryx, the Blight Dragon[/c ] = Skithiryx, the Blight Dragon [ c=Skithiryx, the Blight Dragon]Skittles[/c] = Skittles Cards do what they say they do. No more. No less.
|
|
|