 How I got into running events  A topic that is rarely discussed  Very useful for L1 and L2 judges  Useful for judges regularly attending store- level events

Part of the whole Magic experience that is sometimes overlooked but quite important  Help make events fun  Help make events run smooth  Enable reporting and PWP  Track player behaviour

 Wouldn’t it be nice if there was a definition somewhere?

MTR 1.9 Scorekeeper The Scorekeeper ensures the correct generation of pairings and all other tournament records throughout the tournament. The Scorekeeper’s responsibilities include: Generating correct pairings each round and accurately entering the results of those rounds. Solving all scorekeeping problems that arise in consultation with the Head Judge. Making sure all necessary information is included in the tournament’s report to be submitted to the DCI. The Head Judge has the final authority in determining corrective action for scorekeeping errors.

 Different role during events  Different “pacing”  Harder to replace  Higher autonomy  Higher impact on tournament flow  Does not require judge certification

 What could possibly go wrong?  Explain, educate, empower  Decide what can be done by someone else  Have a back-up plan  Don’t panic

 HJ and SC  The hungover guy  The person with no Magic experience

 Trained professionals  Different client  Much more challenging and demanding

 The only tool available to stores  Supports different products  Replaced DCI-R  Used for things other than scorekeeping  Updated periodically  At least it gets the job done… usually

Do NOT update.

 "object not set to valid bla-bla“  judges not allowed to play at regular events  not allowing newly created DCI numbers

 ending events after midnight  weird single elimination bracket  top 8 bracket are not useful  erasing data from an event  double bye in small events  must use multiprint

 Turn it off and on again  Contact support  Do it manually  Don’t forget the data logs

 entering the wrong player  not dropping a player  dropping the wrong player  entering the wrong result

 The event must go on  Don’t make players wait  Avoid mistakes or fix them ASAP  There is human interaction involved

 Not as scary as it seems  Be familiar with MTR  Keep track who played who  Double check points  Do it fast  Try to avoid tiebrakers if possible

 SC and WER can help make Magic events fun  Scorekeeing is easy  WER works, just don’t update it  Mistakes happen, look for solutions

Thank you!