{"id":471,"date":"2015-09-28T15:17:34","date_gmt":"2015-09-28T22:17:34","guid":{"rendered":"http:\/\/blogs.magicjudges.org\/telliott\/?p=471"},"modified":"2016-04-10T22:18:46","modified_gmt":"2016-04-11T05:18:46","slug":"bfz-policy-changes","status":"publish","type":"post","link":"https:\/\/blogs.magicjudges.org\/telliott\/2015\/09\/28\/bfz-policy-changes\/","title":{"rendered":"BFZ Policy Changes"},"content":{"rendered":"

[cets_callout_box style=’yellow’ align=’right’ title=’The New Docs’]IPG<\/a> | MTR<\/a>
\n[\/cets_callout_box]<\/p>\n

\nThe Battle for Zendikar has been unleashed on us, and that means it’s time for an Eldrazi-sized policy update! Just kidding; it’s not as big as the last one, but there are still a few things to… process. Ahem.<\/p>\n

When we released the Origins update, we had the big change to Drawing Extra Cards policy. At the time, we didn’t know how it would be received by the players, so we were conservative about what it applied to. After seeing it in action for a few months and talking to players about it, I’m happy to say it’s been received well and we’re expanding Drawing Extra Cards in several interesting ways.<\/p>\n

<\/p>
\nDEC now applies to situations in which a player put a card in their hand that they were supposed to first reveal in order to prove that putting it there was legal. That one is straightforward. The player reveals their hand and the opponent chooses a card to be shuffled back into the library. Note that in this, and all other situations where this correction is used, the action that led to the problem is not repeated. So, if I activate Domri Rade, look at the top card and put it into my hand, a card from my hand goes back into the library, but I don’t get to try again with the next card. Moving this to DEC also means that the can’t-verify-legality upgrade in GRV becomes explicitly about how to handle illegally-played morphs.<\/p>\n

<\/p>
\nDEC now also covers situations where a player is instructed to do something with the top N cards of their library and does it for too many. So, for example, I cast Dig Through Time and take 8 cards off the top of my library. We apply the DEC fix, but we apply it to that set of cards! So, you reveal the 8, your opponent selects one of them to be shuffled back in, and you continue resolving Dig Through Time as normal.<\/p>\n

Be a little careful in situations where a dexterity error leads to a card being knocked off the top of the library at the end, but not added to the set of cards under consideration. That’s still Looking at Extra Cards. It’s most likely to come up with scry. Pulling the top card off for a Scry 1 and knocking the next one over is not the same as accidentally Scrying 2.<\/p>\n

<\/p>
\nFinally, there was a lot of confusion over which GRV-style errors fell under DEC and which fell under GRV. If I cast a Mulldrifer for 4R and drew two cards, where did it fall? Honestly, it wasn’t that important, since the remedy was the same in both locations, but we’ve cleaned that up. Now, any GRV that directly leads to a card draw is treated as Drawing Extra Cards, with the traditional back-up-or-leave-as-is remedy. We think it’ll be helpful to track players who make a series of errors that are leading to them drawing extra cards, even if the error was not the card draw itself.<\/p>\n

Phew, that’s a big change. Good thing that’s all we need to handle this… wait, did somebody say Scry?<\/p>\n

<\/p>
\nSo, as of Origins, Scry is evergreen. That means it’ll show up in most sets, along with our brand new shiny mulligan that everyone got to use over the weekend. But, that’s not the only effect that Scry becoming evergreen has. It also means that the barrier for making official shortcuts is lowered a bit, and so we’ve added one that essentially make Scry optional. If you don’t do it, we assume you did and left things as is. This applies to mulligans and scrying in the game. To not take up too much of your headspace, we removed a shortcut to compensate, and the winner there was the “no attacks” shortcut which… didn’t really do anything. It was just there as a standardized interpretation of a phrase that wasn’t causing any confusion. That’s not enough in this scion eat scion shortcut world.<\/p>\n

Beyond that, there’s the usual grammar cleanup and rephrasing things to make them clearer, especially for non-native English speakers. And then there’s a few quick tweaks. Highlights:<\/p>\n