I argued that black could remove +1/+1 counters by using -1/-1 counters, and I explained how this could be done in a way that functioned mostly similarly to just preventing counters.In that post, YOU argued that REMOVING COUNTERS == PREVENTING COUNTERS... And you argued that it was functionally the same a few more posts.
I never argued that removing counters was the same as preventing counters, actually I've several times outright stated that it doesn't, yet you somehow choose to focus on the one place where you can kinda twist it to claim that I did.
Being able to prevent +1/+1 counters gives no basis for assuming they can prevent any other kind of counter. Especially not since I have already explained why it makes sense that they can prevent +1/+1 counters.From a mechanical perspective, there aren't much justifications. Black can already remove any number of counters and the article notes it as sole color for removing counters. Which is flawed. R&D drifted on it, so it's hard to say where they are right now, but it seems that white can prevent counters and black can prevent some counters.
I think Gauntlet sufficiently explained how black's relation to poison would be.From a flavor perspective, black would be a color that would allow you to dump your poison onto others, or manipulate it in a similar fashion. Not necessarily prevention, but in essence the same or worst.
And whether Melira is still within the color pie of green can be discussed, but we have no evidence that she's within black just because a black creature also prevents some kind of counter.And I've explained, Melira was before that article, Blightbeetle, Suncleanser, and Solemnity are after.
Adding corruption to yourself is indistinguishable from just paying life 99% of the time, so why even use corruption on yourself as a mechanic?Well, here is why I did. I didn't want corruption to be parasitic, I wanted to make sure that if you are adding corruption on yourself, it's a minor tradeoff, not a 99% free tradeoff.
We're not arguing against the damage, we are arguing against the "life gain prevention".In my book, the damage is part of the design space. Sure I give some design space up, but it is worth it for the flavor and interactivity.
How is it more interactive?
That's not what I ever claimed. I claimed "20 corruption=lose the game" was parasitic.Also, I was responding to your claim "corruption=1 damage in counters" was parasitic.
It's not. Not in any sane* way of defining it.
I've explained multiple times what my problem is, please address it.
I'm not sure why a purge can completely atomize a physical object but do nothing to a magical aura, when being anti magic is kind of what inquisitions are about.And I know why I'm doing it that way. Because it's meant to show how the Inquisition burns people and their instruments - that's the flavor. But even on a most basic mechanical level (modulo flavor), no one else found this problematic. Well. Almost no one
Does your limited environment actually require this? From what I have seen it isn't a
There were actually 3 before Alara, 2 of them castable with only colorless mana, and the third from time spiral. So it's safe to say that before Alara colored artifacts weren't really a thing. Then in Alara they made a decision, and they made sure to actually go by that decision, designing loads of colored artifacts because they were now able to.Congratulations. I wrote down Kaladesh by mistake, I meant to write Alara. In Kaladesh, they became deciduous.
This is not that, at all. You're not doing something new and interesting. You're doing something that exists already but you're doing it slightly differently than how it is ussaully done, and that is sometimes fine, but I think in this case it begs the difference, why not do it like it's usually done?
White occasionally gets exile target artifact or enchantment on common, you can do this with your set mechanic, that's a neat common to put into your set. Why do you need to shake it up more?
I don't have that mentality. I'm saying that if you want to do something unorthodox you're gonna need to think about how you do it, and maybe more importantly, why you do it. What implications does this have? Is there maybe a reason they haven't done this?I still have the problem with "They never did it, so they will never do it" mentality. R&D shifts their position all the time.
I don't see you trying to answer these questions.