{"id":1115,"date":"2019-07-08T09:04:16","date_gmt":"2019-07-08T16:04:16","guid":{"rendered":"http:\/\/blogs.magicjudges.org\/telliott\/?p=1115"},"modified":"2019-07-08T09:07:48","modified_gmt":"2019-07-08T16:07:48","slug":"policy-changes-for-core-2020","status":"publish","type":"post","link":"https:\/\/blogs.magicjudges.org\/telliott\/2019\/07\/08\/policy-changes-for-core-2020\/","title":{"rendered":"Policy Changes for Core 2020"},"content":{"rendered":"<p>[cets_callout_box style=&#8217;yellow&#8217; align=&#8217;right&#8217; title=&#8217;The New Docs&#8217;]<a title=\"IPG\" href=\"https:\/\/wpn.wizards.com\/sites\/wpn\/files\/attachements\/mtg_ipg_12jul19_en.pdf\">IPG<\/a> | <a title=\"MTR\" href=\"http:\/\/wpn.wizards.com\/sites\/wpn\/files\/attachements\/mtg_mtr_12jul19_en.pdf\">MTR<\/a><br \/>\n[\/cets_callout_box]<\/p>\n<p>Evil schemes. Blue-coated figures. Carnage in the streets. Sacrifices being made to save the day.<\/p>\n<p>Yeah, Narset has been interesting.<\/p>\n<h2>Narset<\/h2>\n<p><img  style='float:right'  class='lems-mtg-cardimg' src='http:\/\/gatherer.wizards.com\/Handlers\/Image.ashx?size=small&type=card&name=Narset, Parter of Veils'><\/p>\n<p>Many people have been worrying about Narset and, more generally, the static abilities on the War of the Spark planeswalkers. It turns out that they&#8217;re really easy to miss, and several of them alter game rules directly. They&#8217;re generating frequent judge calls and Game Rule Violations (or, in the case of Narset, Hidden Card Error violations).<\/p>\n<p>I got lots of suggestions on what needed to be done to handle one or both problems, from revamping our communication rules to fundamental changes on player responsibilities. In the end, a lighter touch seemed wise and hopefully this will make things smoother.<\/p>\n<p>Step one was to get Narset out of Hidden Card Error. Almost everyone felt that it was too easy to not realize there was a relevant card in play and wanted the opponent to take a more active role in preventing any issues. This isn&#8217;t to say that a player casting Divination with a Narset out should be able to take it back, but we&#8217;d prefer the opponent to be preemptive about reminding the player of what the result was going to be before things became harder to fix. With a potential reveal of the opponent&#8217;s hand and removing their best card available, staying silent was too good, to the point where the IPG was making Narset a stronger card. So we&#8217;ve added a line to Hidden Card Error that makes it not a Hidden Card Error if Narset (or another ability modifying the game rules) is the underlying cause. Instead it&#8217;s handled as a regular Game Rule Violation.<\/p>\n<p>Step two was to update the guidelines for when it&#8217;s appropriate to give a double Game Rule Violation as opposed to a Failure to Maintain Game State. We now explicitly call out cards controlled by the opponent that are modifying the rules of the game as a relevant factor. This makes instinctive sense; these effects are usually invisible, and if the opponent who controls that card also fails to notice the error quickly, they share responsibility for the problem. <\/p>\n<p>Between the two changes, we think everyone will have more incentive to catch potential Narset errors early, and the remedy will be less punitive when it does happen.<\/p>\n<h2>Which Isn&#8217;t To Say That HCE is a Bad Thing<\/h2>\n<p><img  style='float:right'  class='lems-mtg-cardimg' src='http:\/\/gatherer.wizards.com\/Handlers\/Image.ashx?size=small&type=card&name=Mystic of the Hidden Way'><\/p>\n<p>Judge extraordinaire Kevin Desprez and I were chatting in London about ways we might improve Deck Error. There were some edge cases that weren&#8217;t being handled as well as we thought they could be, especially around cards revealed to both players at right around the same time. We were playing around with various creative solutions and best things we tried&#8230; looked a lot like Hidden Card Error. What would happen if we treated Deck Problem the same way? It worked!<\/p>\n<p>There&#8217;s still a couple of upgrade paths. There&#8217;s no getting around putting more copies of a card into your deck than you started with, and the presentation upgrade is needed to keep people from presenting a deck short on cards. And there&#8217;s one more we&#8217;ll get to in a moment. But everything else can be handled with the help of your opponent.<\/p>\n<p>The way Deck Error works now is you locate all the cards that need to be put in, all the cards that need to come out, and the opponent chooses which goes where. Reveal a sideboard card when resolving an Explore? Your opponent chooses which card it really is. Have one in your hand? Your opponent decides what to replace it with.<\/p>\n<p>We managed to get it to a point where the player couldn&#8217;t benefit from not immediately pointing out a sideboard card, with one exception. What if the opponent had seen a sideboard card (from a Duress or a Surgical Extraction, or &#8211; worst of all &#8211; a sideboard card being played) and subsequently made decisions based on that knowledge? It would not be fair to them to try to fix the game at this point. But, we have a good precedent for that as well in Communication Policy Violation. So, if a judge thinks that the player made strategic decisions based on seeing a card that wasn&#8217;t supposed to be in the deck, we have our final upgrade.<\/p>\n<h2>The British Are Coming<\/h2>\n<p><img  style='float:right'  class='lems-mtg-cardimg' src='http:\/\/gatherer.wizards.com\/Handlers\/Image.ashx?size=small&type=card&name=Admiral%27s Order'><\/p>\n<p>The London Mulligan is here! For what is functionally a pretty small change, our old rules around mulligan mistakes weren&#8217;t compatible with it, and that section has been revamped. And by revamped, I mean made a lot simpler. Turns out there&#8217;s only two realistic ways to mess up a London Mulligan. Either you draw eight cards, or you forget to put cards on the bottom before beginning the game.<\/p>\n<p>Eight cards is easy. You simply make them take another mulligan. Forgetting cards is more of a challenge. Getting information about what your opponent is playing is an advantage, especially in a world where Leylines are in Standard. In the end, the best way to handle this was through Hidden Card Error, so we send it there.<\/p>\n<h2>Yes, We Have a Heart<\/h2>\n<p><img  style='float:right'  class='lems-mtg-cardimg' src='http:\/\/gatherer.wizards.com\/Handlers\/Image.ashx?size=small&type=card&name=Golem%27s Heart'><\/p>\n<p>For years, we&#8217;ve talked about &#8220;tardiness with a heart,&#8221; the idea that maybe we give the players until a minute after the round starts to get to their seat. The problem with that approach in big tournaments is that if that&#8217;s the policy players don&#8217;t worry about getting into their seats until a minute into the round; you&#8217;ve simply punted the problem forward a bit. But, what if we could forgive players for being late once? That turns out to be easy to do. There&#8217;s now a downgrade to a Warning if the player makes it in the first minute. Of course it happens again, they get another Warning&#8230; which for Tournament Errors is upgraded back into a Game Loss. <\/p>\n<h2>Status Conscious<\/h2>\n<p>Several people pointed out that we needed to add status information to the list of information types that you needed to be honest about. A couple also suggested that mana in pool could be a status type. This makes a lot of sense. We require players to announce floating mana, and if it&#8217;s going to stick around for any length of time, we really want it to be visually represented (I&#8217;ve seen players try to storm out while tracking verbally. It&#8217;s never pretty.) <\/p>\n<p>A nice side effect is that it removes the need for the X-spell shortcut; mana as status information handles it for you.<\/p>\n<h2>Quick Hits<\/h2>\n<ul>\n<li>The wording for the zone-change-undo trigger rule has been updated to make it clear that the zone the object goes to doesn&#8217;t have to be the same as the one where it started. For example, Sneak Attack&#8217;s delayed trigger can&#8217;t be missed.<\/li>\n<li>Looking at Extra Cards got tweaked in the last update to include the sideboard in locations you could accidentally see cards from. Unfortunately, that messed up Bomat Courier and friends, so there&#8217;s another small update this time that restricts any remedy to cards seen from the library.<\/li>\n<li>Technically, when a player passed the turn, the opponent could announce that they were acting in second main phase and keep the turn there until time expired. That obviously wasn&#8217;t the intent of our new end-of-round policy, so it got tweaked to avoid that loophole. It now works the way you thought it worked all along.<\/li>\n<li>We really don&#8217;t care if players use Snow-covered lands accidentally in Standard. Fix it and don&#8217;t issue a penalty.<\/li>\n<li>The section about representing tokens was moved from Game Markers to Board Layout, where it feels appropriate. It also means that if a player does a poor job of representing a token, it may fall into Communication Policy Violation if the opponent acts on bad information (such as the tapped\/untapped status of a die)<\/li>\n<\/ul>\n<p>That&#8217;s it for this update. Thanks as always to everyone who sent in suggestions or requests. Particular shout-outs to Kevin Desprez, Isaac King, Matthew Johnson, Alfonso Bueno, Joseph Steet, Florian Horn and Sara Mox. Enjoy the new Core set and we&#8217;ll see you in the fall for whatever Archery turns out to be.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>[cets_callout_box style=&#8217;yellow&#8217; align=&#8217;right&#8217; title=&#8217;The New Docs&#8217;]IPG | MTR [\/cets_callout_box] Evil schemes. Blue-coated figures. Carnage in the streets. Sacrifices being made to save the day. Yeah, Narset has been interesting. Narset Many people have been worrying about Narset and, more generally, the static abilities on the War of the Spark planeswalkers. It turns out that they&#8217;re [&hellip;]<\/p>\n","protected":false},"author":26,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_links_to":"","_links_to_target":""},"categories":[3],"tags":[],"language":[9],"class_list":["post-1115","post","type-post","status-publish","format-standard","hentry","category-policy","language-en"],"_links":{"self":[{"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts\/1115","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/users\/26"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/comments?post=1115"}],"version-history":[{"count":14,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts\/1115\/revisions"}],"predecessor-version":[{"id":1129,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts\/1115\/revisions\/1129"}],"wp:attachment":[{"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/media?parent=1115"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/categories?post=1115"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/tags?post=1115"},{"taxonomy":"language","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/language?post=1115"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}