Commander rules update!

Started by particle, March 23, 2015, 08:50:35 PM

Previous topic - Next topic

LinkCelestrial

Morph commander damage shouldn't count. For all other rule purposes It's not your commander it's a morph.

Munchlax

It's never counted as commander damage with {Akroma Angel of Fury}

particle


Munchlax


rarehuntertay

Quote from: Munchlax on March 24, 2015, 04:49:36 PM
Quote from: particle on March 24, 2015, 04:09:51 PM
Quote from: Munchlax on March 24, 2015, 12:54:45 PM
It's never counted as commander damage with {Akroma Angel of Fury}

Then you were playing incorrectly. http://boardgames.stackexchange.com/questions/20799/commander-status-as-hidden-information
Then why did they care about that with tucking?
Because then that would be giving information to your opponents. You randomly manifest your commander "oh look it's my commander". Now everyone knows what to gun for

Kaylesh

Quote from: rarehuntertay on March 24, 2015, 05:32:00 PM
Quote from: Munchlax on March 24, 2015, 04:49:36 PM
Quote from: particle on March 24, 2015, 04:09:51 PM
Quote from: Munchlax on March 24, 2015, 12:54:45 PM
It's never counted as commander damage with {Akroma Angel of Fury}

Then you were playing incorrectly. http://boardgames.stackexchange.com/questions/20799/commander-status-as-hidden-information
Then why did they care about that with tucking?
Because then that would be giving information to your opponents. You randomly manifest your commander "oh look it's my commander". Now everyone knows what to gun for
They will know as soon as damage is dealt. Since you have to announce commander damage. And, in the case of a morphed commander like Akroma, cast face down from the command zone: you have to differentiate your morphs. It has to be clear what is morph1 and which is morph2. So when cast as morph from command, it would be known. In the case of manifesting your commander after a tuck, if asked you should give every known attribute of the card: no name, no color, 2/2, commander.

Stoneco1d869

Quote from: LinkCelestrial on March 24, 2015, 12:39:44 AM
Always hated tucking. Glad to see it. I don't play super competitive commander, I play pretty casual commander. You're talking the only insane {Niv-Mizzet, the Firemind} combo card being {Enter the Infinite}.

Great in theory, but I play with super competitive degenerate decks and the only way to slow or stop them is the tuck, or threat there of.

Looking at you Animar.

Munchlax

Quote from: Stoneco1d869 on April 02, 2015, 09:21:47 AM
Quote from: LinkCelestrial on March 24, 2015, 12:39:44 AM
Always hated tucking. Glad to see it. I don't play super competitive commander, I play pretty casual commander. You're talking the only insane {Niv-Mizzet, the Firemind} combo card being {Enter the Infinite}.

Great in theory, but I play with super competitive degenerate decks and the only way to slow or stop them is the tuck, or threat there of.

Looking at you Animar.
Hehe. Sorry. My deck isn't multiplayer anymore though. I have {Alesha Who Smiles At Death} for multiplayer

gtfotis

Quote from: the_intelligentleman on March 23, 2015, 10:49:15 PM
Quote from: Popper23345 on March 23, 2015, 10:44:39 PM
This rule sucks

Blue is getting its ass whupped by all these bans because they are "too good" or "scared they might break the format". If you are worried about tucking, then get tutors. I mean seriously, if your commander is CONSTANTLY getting tucked, then add some extra tutors.

Tucking someone's commander is just an extra "wincon" (I say that loosely because it isn't actually a win condition, but it helps..) Banning tucking is like banning anything with infect on it. Infect is another way to screw people over in commander because you have more time to grab your {blight steel colloses} and {darksteel colloses} yet these are still perfectly fine for commander.

I am against the rule change because It is pushing the game away from certain colors *cough cough* blue *cough cough* and it is something that doesn't even occur all that often.

First {treasure cruise} and {dig through time} in standard. Now cards like {hinder}? Might as well cut blue and add pink instead

#{water gun balloon game}

Edit: plus, wasn't commander a fan-made format? Why does wizards have to stick its grubby little ban fingers in our format?

/end rant
1. Lol blue is still by far the best color in magic, and commander.
2. WoTC doesn't do commander ban list updates.
3. Dig and Cruise are still legal in standard
#rekt

DimirOverlord1300

Quote from: gtfotis on April 03, 2015, 08:37:20 AM
Quote from: the_intelligentleman on March 23, 2015, 10:49:15 PM
Quote from: Popper23345 on March 23, 2015, 10:44:39 PM
This rule sucks

Blue is getting its ass whupped by all these bans because they are "too good" or "scared they might break the format". If you are worried about tucking, then get tutors. I mean seriously, if your commander is CONSTANTLY getting tucked, then add some extra tutors.

Tucking someone's commander is just an extra "wincon" (I say that loosely because it isn't actually a win condition, but it helps..) Banning tucking is like banning anything with infect on it. Infect is another way to screw people over in commander because you have more time to grab your {blight steel colloses} and {darksteel colloses} yet these are still perfectly fine for commander.

I am against the rule change because It is pushing the game away from certain colors *cough cough* blue *cough cough* and it is something that doesn't even occur all that often.

First {treasure cruise} and {dig through time} in standard. Now cards like {hinder}? Might as well cut blue and add pink instead

#{water gun balloon game}

Edit: plus, wasn't commander a fan-made format? Why does wizards have to stick its grubby little ban fingers in our format?

/end rant
1. Lol blue is still by far the best color in magic, and commander.
2. WoTC doesn't do commander ban list updates.
3. Dig and Cruise are still legal in standard
#rekt
Also blue only had 3 tuck effects (I think), that's not many. Banning tucking isn't a push away from blue, it's a push away from mean things. I still disagree with it, but basically every point you made was false.

cltrn81

{Terminus} can suck it.  I remeber a recent commander game where I had puked up a ton of indestructible tokens in my {rhys, the redeemed} deck only to watch em all go bye bye to terminus....and lost my commander 😥

JordanCirk

Quote from: cltrn81 on April 03, 2015, 04:12:49 PM
{Terminus} can suck it.  I remeber a recent commander game where I had puked up a ton of indestructible tokens in my {rhys, the redeemed} deck only to watch em all go bye bye to terminus....and lost my commander 😥
It's still a powerful card, but yes I'm glad that it won't "tuck" commanders anymore.