I must say that I share astarael7's feeling regarding this topic. On the official forums, BaconCatBug had the habit of continually reposting this idea, posting comments about it in unrelated threads, and generally just repeating the same points without taking in what other people were saying. This was the second-most annoying behavior on those forums, and I was hoping not to see it here.
I'm probably going to regret posting in this thread, but there are people here who I'm going to assume are arguing in good faith, so I'll just address some points.
I can promise you I'm arguing in good faith. I'm also under no illusion that I am arguing with anyone capable of instating change, nor do I expect that change. I'm debating design and aesthetic principles because those are interesting to me.
The problem is that Magic is messy. There have been several major rules overhauls, and a whole lot of minor ones. Cards have been printed and reprinted at different times, under different errata policies. There have been misprints. There have been cards that were printed that were only later discovered to not actually work. And there have been cards that are just templated very poorly.
I'm a big fan of consistency. And I do find inconsistency jarring. However, because of the inconsistency in printed texts, this is really inevitable. If you try to find a single consistent algorithm for determining the Oracle text, you'll still get inconsistent end results, oftentimes undesirable ones.
right, but Nirvana fallacies. just because you can't be perfect (and I agree you can't) doesn't mean you can't be better, and it doesn't mean that sloppy, half-assed solutions are as good as anything else.
As such, the policy they use allows for human judgment calls. There are a variety of factors that go into determining the Oracle text, but no one factor will always win, and the people determining the Oracle text can make the call for which ones should be prioritized in which cases. It's certainly desirable for cards with the same printed text to work the same way. It's also desirable for a card to just work as printed, independently of other cards. It's also desirable for them to have the possibility of fixing typos, misprints, or accidentally non-working cards. It's also desirable for cards to keep working past rules changes. It's also desirable for cards to just not be really weird. It's also desirable for Oracle texts to stay constant over time. And these goals often pull cards in very different directions. So if you find a case where your favorite of these goals isn't met, that doesn't mean they're hypocritical or violating their policy. It just means a different one won out in that particular case.
sure.
If you want to know why
Lotus Vale and
Crosis's Catacombs work differently despite being worded the same, that's because the Vale is really old and was printed under different rules. That's also why
Waylay won't let you keep the creature past the current turn (even if you cast it in your end step), why
Carnivorous Plant can't attack, why
Chaos Orb's activation cost includes a
, and why
Wiitigo doesn't immediately go to the graveyard for having 0 toughness. In each of those cases, just reading the printed text and interpreting it as though it were a modern card will give the wrong result. In order to get the right result, you either need to know the old rule that caused it to work the way it does, or you need to recognize that it's an old card and check the Oracle text.
Waylay is just as silly, Chaos Orb says "mono artifact" which instructs players to look up what that means, and Wiitigo literally can't function without the fix, and thanks to the
Mitotic Slime principle most players will play it right anyway.
Plant is a fair point though. it was my recollection that all old walls had the
(walls can't attack.) reminder text, which would at least inform people looking at the card that something was up, but that does not appear to be the case. and I think I can agree that they shouldn't make it so all walls that weren't printed with Defender can now suddenly attack. that seems like a bad road to walk down.
there is still a difference, though: they've never printed a wall without Defender. someone can casually mention at some point that all walls have Defender and you can just remember that. you have a rule. a rule you can apply unambiguously across the board. if you see a wall without Defender, you'll know that it must be from before whenever they made the switch. with lands that sac on etb, though, there is no such rule. you have to memorize exactly when the switch was made so you can tell which ones of the identical-looking cards work one way and which work the other. actually, you can't even do that, because
Karoo was printed before Vale but works like Catacomb. (which, by the way, is also "really old" by now. Weatherlight and Planeshift were 3 and a half years apart, about 15 years ago.) so you literally have to memorize the list of cards this errata applies to, rather than just understanding them as an easily identifiable class like Walls.
there's also the difference that a lot of design work has been done
around the fact that walls can't attack. things like
rolling stones, for instance. are there any cards that are designed around the assumption that lands that sacrifice on etb unless you pay a cost don't actually ever enter the battlefield unless you pay?
the Wall solution is ugly, but I agree with you that all the other solutions there are uglier. I don't think that's true of Vale.
If you want to know why
Lotus Vale and
Phyrexian Dreadnought work differently despite being worded the same and both being old, it's because the Dreadnought didn't need the errata. That replacement effect thing is really weird, so they'll avoid it when possible. In the Dreadnought's case, the card itself works the same with or without the errata. It would take an interaction with additional cards for it to work differently. In the case of the Vale, however, no other cards are necessary; the card itself would be fundamentally different from what it was designed and printed as if it it didn't have that errata. Gaining the additional functionality of being a
Black Lotus is kind of a big deal. It's okay for them to fix what needs fixing, without the obligation to then also fix what
doesn't need fixing. That
would just be consistency for consistency's sake.
sure, but that's happened.
Master of Arms and
Kill-Suit Cultist lost inherent design-vision functionality with rules changes.
Chain of Acid got to kill a whole new card type that its designers had never dreamed of. fundamentally changing intended functionality isn't, in and of itself, a dealbreaker, and I think preserving it takes a back seat to preserving clear player intuition. the only difference here is that player intuition makes it an incredibly powerful card, but Legacy loses nothing by banning it and Vintage is all about playing broken stuff so adding one more puzzle piece doesn't hurt it.
If you still think that
Lotus Vale should be changed, that's fine. There are certainly cards whose Oracle texts I dislike (e.g. I'd prefer if
Burning of Xinye,
Imperial Edict and
Wei Assassins had kept their "sacrifice" wording, rather than reading Portalified rules text as though it were normal Magicese, and I literally have a list of little templating inconsistencies I'd want to have standardized away). However, if you think it's objectively wrong for the Vale to have its current text, that it's a violation of their policies, or that they're obligated to change it, I think you're mistaken.
in this context there's no such thing as objectively right or wrong, their policy is "things work the way we say they do", and I don't have any authority through which to obligate them. like I said I'm arguing aesthetic and design theory and I think they made a bad decision.
For Lotus Vale and its friends, a huge hint to check for that very thing is that anachronistic "bury" hanging out in its ability's effect. (One totally absent from Crosis's Catacombs.)
bury has nothing to do with timing.
bull elephant, for instance, uses bury but is a triggered ability.
seeing "bury" makes me have to figure out what "bury" means, but it doesn't give me any heads-up about any other changes. and given how obvious what "bury" means since there's a zone called the graveyard, it's unlikely seeing it will even make me look anything up. and, again,
Karoo.
And I'm now in the habit of checking Oracle text on many hing older than two years. Gatherer is very, very accessible and getting more so all the time. Would it be easier if we could all memorize hard-and-fast rules for translating every card into modern templating? Absolutely. But having to check a website for a card's correct wording isn't much of a barrier nowadays.
then why not change cards entirely? why not make
ancestral recall cost
so it doesn't have to be banned in Legacy or restricted in Vintage? why not make
black lotus cost
and only add one mana? why have a B/R list at all if you can just errata things so they do what you wish they would because everyone can just check a website?
whether or not people can, the fact, and you and I both know this is a fact, is that a
lot of people won't. which means there's a lot of value in cards doing what they say they do. you don't have to stick with the old wording, but at least stick with a logically reasonable interpretation of it.