Originally posted by Jon Nauert:
We consider Sidisi's trigger to be detrimental because you're being denied resources despite other cards being able to benefit from it, and yet we consider Emrakul's trigger detrimental because even though it's providing extra resources, it disallows other cards from benefiting from it? To me, this sounds a bit contradictory and double-standardy. If we consider Sidisi's ability in a vacuum regardless of other cards that can benefit from her ability, why not do the same for Emrakul?
Toby Hazes
That leaves us with self-mill. Beneficial or detrimental? It isn't as obviously good as drawing cards, but it isn't as obviously bad as exiling cards. So I would say, why not let the cards speak for themselves again?
Necromancer's Assistant vs Warpath Ghoul
Armored Skaab vs Wavecrash Triton
Millikin vs Manakin
The cards clearly cost self-mill as something beneficial. If R&D would agree with the theoretical assessment that it's detrimental because it denies resources then wouldn't they cost it as a detrimental ability? This has nothing to do with corner cases or context or other abilities. Standard rule is that self-mill is costed as something beneficial. So why not make it a beneficial trigger? Is there any card with a self-mill trigger that would look really weird as being beneficial?
Originally posted by Brian Schenck:Brian is (again) correct. And I agree with the rest of his latest post, too.
(I don't know if R&D is consulted on every trigger, but I bet someone who does help make the evaluation has the ear of someone in R&D to make certain for these narrow situations as necessary.)
Sam ShermanReally? I think it's a worthwhile discussion, even if a bit over the top.
This whole thing is completely ridiculous.
Bryan PrillamanIf we step in and issue a Warning for a trigger that turns out to be not generally detrimental, we haven't killed Magic. Still, for the sake of consistency, we should try to always stick to the official guidelines we are given, and that Missed Trigger Guide is part of our consistency toolkit.
the *worst* that can happen is that a trigger happens that should have happened … the game is played more correctly
Originally posted by Scott Marshall:I think Toby may actually have hit upon a problem with this logic. It doesn't seem that cards are designed in such a way that self-mill triggers are intended as a downside. And they are almost never played when that self-mill would be a downside. You have some odd cards like Arc-Slogger where exiling from your library is a real cost, but this certainly doesn't seem to be the case with the vast majority of self-mill effects.
Milling cards from your own library is generally detrimental. While it's true that you probably want to remember Sidisi's trigger, or that of Nyx Weaver, that doesn't change the guideline of “generally detrimental” (or not - this isn't detrimental vs. beneficial, it's generally detrimental vs. not generally detrimental).
Originally posted by Joshua Feingold:
It doesn't seem that cards are designed in such a way that self-mill triggers are intended as a downside. And they are almost never played when that self-mill would be a downside.
Originally posted by Joshua Feingold:
While milling your opponent is a possible route to victory, I think self-mill is also generally a route to victory. In much the same way that the upside of drawing a card is generally better than the downside of life lost to Dark Confidant's trigger, I think there is a very real possibility we should be saying that the value of having extra resources in your graveyard is generally better than the downside of increased risk of decking. And in the rare cases where decking is a real win condition, the opponent can still make them mill just like they can enforce the Bob trigger.
Originally posted by Wiley Jephson:Interestingly, before Sep. 26th of this year, both of those triggers were listed as non-detrimental. On Sep. 26th, a user changed Armored Skaab to detrimental. Splinterfright was changed to detrimental after you made that post.
Splinterfright (mill two) is not detrimental, but an armored skaab (mill 4) is detrimental…
Originally posted by Ian Edwards:This is actually not a problem for policy. Although the language doesn't precisely cover these types of situations, you can apply the intent behind this passage: “The current game state is not a factor in determining this, though symmetrical abilities (such as Howling Mine) may be considered usually detrimental or not depending on who is being affected.”
Where does “self-mill is generally detrimental” leave Curse of the Bloody Tome and Chronic Flooding? Are those cards non-detrimental if I enchant my opponent, but detrimental if I enchant myself?
Originally posted by Joshua Feingold:
Originally posted by Ian Edwards:
Where does “self-mill is generally detrimental” leave Curse of the Bloody Tome and Chronic Flooding? Are those cards non-detrimental if I enchant my opponent, but detrimental if I enchant myself?
This is actually not a problem for policy. Although the language doesn't precisely cover these types of situations, you can apply the intent behind this passage: “The current game state is not a factor in determining this, though symmetrical abilities (such as Howling Mine) may be considered usually detrimental or not depending on who is being affected.”
Edited Abraham Corson (Oct. 15, 2014 02:01:01 PM)
Whenever Sidisi, Brood Tyrant enters the battlefield or attacks, put the top three cards of your library into your graveyard. Put a 2/2 black Zombie creature token onto the battlefield for each creature card put into your graveyard this way
Randomly (usually) denying (usually) resources is bad, m'kay?I think this might actually be an underlying disagreement in this conversation. Is self-mill denying resources, or creating resources? The only resource being depleted is the number of cards in the library - which in 99 games out of 100 is never an issue. Graveyard recursion effects are so common that it's not hard to see cards in graveyard as a resource to be sought out - Emrakul's trigger is considered usually detrimental, as the assumption is that otherwise a player could make use of those effects.
And, let me reiterate - this thread needs to be about “why these are (not) generally detrimental” - i.e., an opportunity for global learning.If I understand this correctly, the remaining use of this thread is to come to an understanding on what the current guidelines are for usually detrimental/not usually detrimental, and how they apply to certain examples?
Edited Talin Salway (Oct. 15, 2014 05:05:18 PM)
Originally posted by Wiley Jephson:
When considering the status of a trigger, I always recall the rule of thumb arising around the same time as “generally detrimental,” which I remember to be similar to what Jason Lemahieu said in the “Missed Trigger Policy - What is ”usually considered detrimental“?” thread:
“The common rule of thumb is “Am I playing this card BECAUSE of this trigger, or IN SPITE OF the trigger?” Take the classic Dark Confidant, for example. 2/1's for 2 aren't going to be played in Legacy or Modern, so it's pretty clear that Dark Confidant is played BECAUSE of its trigger, meaning its generally beneficial.”
The controller of a missed triggered ability receives a Warning only if the triggered ability is usually considered detrimental for the controlling player. The current game state is not a factor in determining this, though symmetrical abilities (such as Howling Mine) may be considered usually detrimental or not depending on who is being affected. Whether a Warning is issued or not does not affect any additional remedies that may be applicable. Failure to Maintain Game State penalties are never issued to players who did not control the ability.
Edited Toby Hazes (Oct. 15, 2014 09:15:06 PM)