{"id":1021,"date":"2018-07-09T09:41:39","date_gmt":"2018-07-09T16:41:39","guid":{"rendered":"http:\/\/blogs.magicjudges.org\/telliott\/?p=1021"},"modified":"2018-07-09T09:41:39","modified_gmt":"2018-07-09T16:41:39","slug":"policy-changes-for-m19","status":"publish","type":"post","link":"https:\/\/blogs.magicjudges.org\/telliott\/2018\/07\/09\/policy-changes-for-m19\/","title":{"rendered":"Policy Changes for M19"},"content":{"rendered":"

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

It’s a small update this time around, so I’m going to use this space to talk about a few additional things at the bottom that aren’t policy changes, but are useful guidance. In the meantime, updates!<\/p>\n

We’ve Been Here Before<\/h2>\n

<\/p>\n

By far the biggest change in terms of text volume is a new Communication section in the Magic Tournament Rules dedicated to loops. They’d come up again because of Teferi, and I was talking to Magic Rules Manager Eli Shiffrin about how we could make them better. <\/p>\n

“It’s really easy. We just want to do this, and this, and this.”
\n“That all makes sense, but it’s not formal logic, so it won’t work in the Comprehensive Rules.”
\n“It’d work in the MTR. Loops are just a kind of shortcut, and we don’t have to be so strict there.”
\n“Go for it.”<\/p>\n

It turns out that expressing how to handle loops is much harder to do in formal Magic rules than it is if you can wave your hands and use plain English. So there’s a new section in the MTR that supersedes the simpler ones in the CR when there’s a tournament.<\/p>\n

From a game perspective, not a lot changes. Loops that span multiple turns are addressed, and judges have flexibility to identify that there’s a loop even if there’s irrelevant things changing. Everything is expressed in terms of asking the players questions and then applying the results, and hopefully it’s much easier to follow.<\/p>\n

We’ve Been Here Before<\/h2>\n

<\/p>\n

By far the biggest change in terms of text volume is a new Communication section in the Magic Tournament Rules dedicated to loops. They’d come up again because of Teferi, and I was talking to Magic Rules Manager Eli Shiffrin about how we could make them better. <\/p>\n

“It’s really easy. We just want to do this, and this, and this.”
\n“That all makes sense, but it’s not formal logic, so it won’t work in the Comprehensive Rules.”
\n“It’d work in the MTR. Loops are just a kind of shortcut, and we don’t have to be so strict there.”
\n“Go for it.”<\/p>\n

It turns out that expressing how to handle loops is much harder to do in formal Magic rules than it is if you can wave your hands and use plain English. So there’s a new section in the MTR that supersedes the simpler ones in the CR when there’s a tournament.<\/p>\n

From a game perspective, not a lot changes. Loops that span multiple turns are addressed, and judges have flexibility to identify that there’s a loop even if there’s irrelevant things changing. Everything is expressed in terms of asking the players questions and then applying the results, and hopefully it’s much easier to follow.<\/p>\n

We’ve Been Here Be<\/del>M19 Draft<\/h2>\n

<\/p>\n

Normally, we tell players to take out the token and the land from booster packs. But M19 introduces a wrinkle where there’s a mix of basic and draftable non-basic lands (and a checklist card) in the same slot! So we’ve called out that slot as being special; for most sets you still remove the basics, but if draftable cards appear in the basic land slot, keep it all in. That way, everyone will have the same number of cards to draft.<\/p>\n

This does have the downside of making the checklist draftable, even though it isn’t playable. Plus, there’s only one card listed on it, so make sure to remind new players that drafting the checklist doesn’t mean that they have a Nicol Bolas in their draft pool and they should just pass it along until the end. <\/p>\n

Upkeep, Draw, Untap<\/h2>\n

We’ve all seen it: a player draws a card for the turn, then untaps, or casts a spell with a stack of land that’s still tapped from the previous turn. It’s all obvious, and usually handled through Out-of-Order-Sequencing or a bit of handwaving. Now the IPG provides a stronger endorsement that this is OK in the form of a partial fix that untaps the things that were supposed to be untapped this turn. We don’t expect judges to need this much as OoOS is a better option in general, but it’s here when you need it.<\/p>\n

Quick Hits<\/h2>\n
    \n
  • We’d established that penalties reset at the Day 1 cut even with a round to go last update, but what REL was that “not really Day 2” round being played at? This update addresses that (Professional).<\/li>\n
  • Any time you change a decklist after the tournament has begun, a Game Loss should be issued. That includes when you can’t find replacement cards for marked ones. That’s explicitly called out as an upgrade now.<\/li>\n
  • Normally, if you have too many copies of a card that’s in both your deck and sideboard, it gets upgraded. But, if you discover it while all the copies (both deck and sideboard) are in the library, it’s not upgraded. <\/li>\n
  • CPV previously looked for an opponent to take an action before it could be called. Clearly choosing to not take an action also qualifies (though I think the threshold there is a little higher). <\/li>\n
  • We cleaned up the language about issuing Game Losses in both the introduction and Decklist sections. This is mostly nonfunctional, though it does emphasize that it’s pretty rare to wait on a Decklist penalty nowadays. It used to be a lot more relevant when we counted lists more aggressively.<\/li>\n<\/ul>\n

    Triggers<\/h2>\n

    One thing that’s come up a bit recently is a debate about Detrimental Triggers and defining them, and I want try to give a little insight into the philosophy here. In particular, I want to address the idea that self-mill triggers are always detrimental, even though some cards – when evaluated in full card context – use them for beneficial reasons.
    \n

    <\/p><\/p>\n

    There isn\u2019t an iron-clad edict from Wizards that self-mill must always be considered detrimental. It has the same weight as anything else that\u2019s regarded that way. It\u2019s like \u201cWhen this enters the battlefield, sacrifice a creature\u201d. That\u2019s a detrimental ability, but I think we\u2019d all agree that \u201cWhen you sacrifice a creature, you win the game\u201d on the same card would make it not a detrimental trigger. <\/p>\n

    However, when the trigger changes happened, we had Innistrad, and we got a lot more pushback on self-mill than all the other mechanics, since it was often a bonus in that format. That meant there was a lot more \u201cno seriously, self-mill is detrimental\u201d posts than on most other mechanics, and a lot more pushback on arguable cases. That has led to a perception that milling was more stringent than the others. It does default to detrimental, but it’s no different from other triggers. You need to look at the overall context of the card (*not* the game state) to make that determination, and this is true for all abilities, not just self-mill.<\/p>\n

    Slow Play<\/h2>\n

    Finally, a nudge.<\/p>\n

    Slow Play is one of the toughest calls a judge has to make. It’s a pure judgment call, and the player affected will almost always argue, talking about how they have lots of time on the clock, or this is a crucial turn, or that they didn’t take that long. This is partly because the perception of time when you’re tanking is different, and what may seem like not a lot of time to think is a huge amount of clock time.
    \n

    <\/p><\/p>\n

    How aggressive judges have been about calling slow play has ebbed and flowed over the years. We’ll make an effort to be more aggressive, that’ll happen for a bit, and then we’ll all collectively slide back a bit. It’s time for another one of those efforts. I’m here to tell you today that you (and I include myself here) aren’t calling slow play enough and need to make a conscious effort to do so.<\/p>\n

    I can’t give you a neat trick that will make your slow play calling game better; what works for one person won’t work at all for someone else. I personally find that if I’m watching a game and start to get bored, that’s a big warning sign, but that’ll vary a lot depending how much you play Magic and how good you are at analyzing options. Whatever your personal heuristic, it takes effort and practice to make it part of your judging repertoire, and a willingness to interrupt a player’s train of thought to get the game moving again. It’s not easy, but we’re not doing it enough right now, and everyone should make a conscious effort over the next few months to be aware of the clock and how long players are taking.<\/p>\n

    Thanks<\/h2>\n

    Thanks to everyone who offered suggestions this time around. In particular, a shout-out to Isaac King, who’s been providing great suggestions for improved wordings. If you see a sentence change that you think is much clearer, you probably have him to thank for it.<\/p>\n

    Enjoy M19!<\/p>\n","protected":false},"excerpt":{"rendered":"

    [cets_callout_box style=’yellow’ align=’right’ title=’The New Docs’]IPG | MTR [\/cets_callout_box] It’s a small update this time around, so I’m going to use this space to talk about a few additional things at the bottom that aren’t policy changes, but are useful guidance. In the meantime, updates! We’ve Been Here Before By far the biggest change in […]<\/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-1021","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\/1021","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=1021"}],"version-history":[{"count":9,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts\/1021\/revisions"}],"predecessor-version":[{"id":1030,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/posts\/1021\/revisions\/1030"}],"wp:attachment":[{"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/media?parent=1021"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/categories?post=1021"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/tags?post=1021"},{"taxonomy":"language","embeddable":true,"href":"https:\/\/blogs.magicjudges.org\/telliott\/wp-json\/wp\/v2\/language?post=1021"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}