Articoli
Attenzione: questo articolo è stato scritto oltre 1 anno fa! Alcuni contenuti potrebbero essere obsoleti.
JAR January 2011 update - James Mackay
Articolo del 1-1-2011 a cura di

 
 
 
Hi everyone,
As Uncle Scott has pointed out, we have a new look Document Centre - and the FCE is nowhere to be found. The document which covers judging at Regular REL is now called (quite deceptively) "Judging at Regular REL".
I'm going to go over some of the changes here, so bear with me - this might end up longer than the document we're discussing.
 
Firstly, the name change - "Guide to Fixing Common Errors at Regular REL" was clunky, awkward and I'm glad to see the back of it. Next time you see me, ask me what the working title was... yikes. Regardless, the name did not inspire people to read it - and discussion with judges from all over the world at Worlds showed me that, in fact, many judges had not read it.
 
Why should they read it? All the judges on this list know their IPG and deserve to show that knowledge - but they, like their players, also deserve to relax and have fun at their events too. The JAR is designed to be a touchstone for people running events without a judge like you, but also serves as the line we are all able to relax our events down to.
 
What do I mean?
 
Let me give you some examples; Player A calls you over, during Player B's turn to tell you they played an Umezawa's Jitte the previous turn, but they also controlled a Chalice of the Void set at 2. At Regular REL you could:
 
a) "Leave the game as is" - much like the IPG's GRV, both players were there, both should have been "more careful".
 
b) Back up - rewind the game, put the "Jitte" back in Player A's hand, then let the game flow from there.
 
b) ii) Put the "Jitte" back in Player A's hand, without backing up, as the game state ends up in the same place as Player A saying "I'll cast... no I won't, oops, your turn"
 
c) Put the "Jitte" in Player A's graveyard - it would have been countered by the CoV, had the game played out correctly, so backing up to the point of error has the trigger counter the spell.
 
Now, which is the correct answer? Well, here is where it gets interesting. These all seem like adequate fixes. Some are better than others, but all have the underlying philosophy of the JAR at heart - find a solution that works, and get the game moving again. As judges we love arguing the fine points of the "best possible solution" which is admirable, and in some cases desirable - but at Regular REL we have a deeper goal. Players playing MtG as best they can. Having the ability to quickly fix the game means we don't have to spend time explaining complex interactions or convoluted fixes – and we can get back to our match! You are all playing in your events, right?
Are these quick fixes open to abuse? I believe they are no more open to abuse than other rules sets - cheaters going to cheat. And that is where we use our skills and the power of community to drive unwanted elements from our game.
 
To that end, the "Serious Problems" section has been substantially reworked - and here I'd like to thank the many generous and vocal judges who rightly pointed out ambiguities and problems. This section now simply says "Boot Jerks" - and the clunky section about "stern chats" has been moved to the correct home in "General Unwanted Behaviour". It is our job to talk to players, and help them understand that certain behaviour is simply not on. With the help of the TO/store owner, and again "the power of community", we can all keep building a player base full of people we'd like to play cards with.
 
There has been a minor change to the Deck Problem fix, to clarify that players who have not desideboarded don't get to "draw from their sideboard" - thanks Jared Sylva!
 
Otherwise, have fun running and playing in your local Regular REL events under the new JAR - and if you have any questions feel free to ask here or off-list. This document could not have evolved without input from judges like you - and if you do play in events with a non-judge TO, encourage them to read the JAR and get their feedback. It is only 1.5 pages... :D
 
Cheers
James Mackay