Spoiler Tournament Format and Rules


Spoiler Race: Players are given a spoiler log prior to go time and may refer to the spoiler document throughout the race.

Table of Contents









What is expected from you, the player

  1. You have SpeedRunsLive and Twitch accounts that are in good standing.
  2. You will be in the discord server for the duration of the tournament, and have DMs enabled for the server (this is the default).
  1. This is so admins and our bot can send you direct messages.
  1. Over a two week period, three qualifier runs shall be streamed to YouTube as unlisted streams, or publicly to Twitch.tv.  These don't need to be pre-scheduled.
  1. Guide for streaming to YouTube will be coming soon for those who chose to stream to unlisted YouTube.
  1. If you qualify, that you will register for Challonge by March 29th, 2019 @ 11:59PM.
  2. Over seven weeks up to 3 games will be played per round, for up to 5 rounds.
  3. You'll conduct yourself in an ethical and sportsmanlike manner.

What you should expect from the tournament admins

  1. If you ping @admins, an admin will respond to you in reasonable amount of time (assuming it isn't 1AM).
  2. The tournament admins will do everything in their power to maintain the fairness and competitiveness of this tournament.
  3. The tournament admins will handle potential cheating in a fair way that protects both the accuser and the accused from harassment.
  4. Changes to the tournament rules and format that occur will be clearly communicated to all players as much in advance as possible before the rule change takes effect.
  1. The tournament admins will strive to avoid rule changes mid-tournament, though reserve the right to do so to correct a major issue.



The format of the qualifiers is significantly different than that of other randomizer tournaments.

Qualifiers consist of three runs.  Every player attempting to qualify will play the same three seeds, which will be posted, along with their spoiler logs, at the beginning of the qualifier phase.

The important part of the qualifier is the player will get only one official attempt (excluding the retry explained below) per seed.  The player is permitted to practice the run as much as they want before attempting their official (scored) runs.

At the conclusion of the qualifier round, a spreadsheet with all of the submitted runs will be made public.

Streaming Qualifier runs

Qualifier matches will be streamed to either an unlisted YouTube stream (instructions will be provided) or publicly to Twitch.tv.  Maintaining local recordings is highly recommended.

If you chose to stream to Twitch.tv, you must have stream archiving enabled and a highlight of your runs must be taken and preserved for the duration of the tournament.

Verification Key

The player will receive a verification key from a bot before the start of their official run.  This key must be the first four characters of the save file and be displayed at the end of the credits roll.

The player will have 15 minutes after receiving the verification key to begin the run.  It is recommend that the player is already streaming before requesting the code.  If the code is requested on accident, it is the responsibility of the player to immediately ping @admin in discord to cancel the code.  Failure to do so may result in a forfeit for the run.


During the course of the qualifier phase, the player will get one retry for the entire qualifier round.  To use the retry, the player simply requests another code using the bot's "$qualifier" command.  We will only accept the player's first retry and other subsequent submissions of runs of a seed the player has already submitted will be thrown out.

Be warned, the player's previous run for the seed will be thrown out when a retry is used.  Even if the second attempt is worse than the original attempt, the second attempt will be the attempt counted for scoring purposes.

The retry may be used at any point during the qualifier period, though is still subject to the March 24th submission deadline.

Qualifier Scoring

The qualifier score will be a sum of the lengths of each run.  If a player has not completed a seed using a verification key requested, the run is considered a forfeit and will be scored as the worst time between all players of the run plus thirty (30) minutes.

The qualifier scores (and links to the VoDs of each run submitted)  will be published at the end of the qualifier round.


The below table is a list of results for this tournament from 5 players.

Run / Players




Old Man


Seed #1

1:10:43 (4243)

1:01:22 (3682)


Forfeit (8451)

1:50:51 (6651)

Seed #2

1:08:22 (4102)

0:50:45 (3045)

1:24:24 (5064)

1:03:28 (3808)


Seed #3


1:18:24 (4704)

1:35:44 (5744)


1:45:45 (6345)

Seed #1 Retry

1:35:44 (5744)

Seed #2 Retry

2:10:44 (7844)

Seed #3 Retry

1:15:25 (4525)

1:10:24 (4224)

Final Score






The bolded times are the times that will be summed for each player.  The number in parenthesis is the time converted to seconds.  Note that Ganon used his retry and scored a worse time.  The worse time is the run that is scored because the first run was thrown out when the retry was used.

The players seeding and ranking for qualification would be from lowest to highest.

  1. Link
  2. Aginah
  3. Old Man
  4. Uncle
  5. Ganon

For this example, let us assume we're only accepting 4 players for the bracket (in reality this is 32 players).  Ganon would be eliminated and would not progress to the bracket stage.

Old Man forfeited runs 1 and 3, and chose to retry the third run.  His first run is counted as a forfeit, so it would be the slowest runner for the run (Ganon) plus 30 minutes, making his score for the run 8451.  He still scored slightly better than Uncle because his other two scored runs had very low times.

Link opt'd to not use his free retry.

Qualifier Workflow

The process for racing in the qualifiers goes:

  1. A player sends a bot the command '$qualifier x' where 'x' is the number of the qualifier seed that they'll be playing (1, 2, or 3).
  2. The player is sent a 4 character code that is required to be in the beginning of the filename of the run when it is streamed. This is done to verify that the player is running the seed live and are not playing back a video of them doing the run in their stream.
  3. The player has 15 minutes to begin their run after receiving the code.  We recommend that the player is streaming before making the request.
  1. The player is required to immediately inform an admin if they do not play the race after receiving the code.  Failure to do so may be counted as a DNF and the game will be recorded as the slowest finish time between all players plus 30 minutes.  The free retry can be used to replay the game.
  1. The player plays the seed and then waits for the end of the credits (when in-game time and collection rate appears).
  2. Once the run is completed, the player will submit their results via a form.  A link in the original DM will pre-fill information on the form.  The player will need to supply their real time, in-game time, collection rate, and a link to the unlisted YouTube stream or to their Twitch VOD.
  1. The run will be reviewed by an admin and officially recorded once verified.


Brackets will be a single-elimination, best of three matches with a max bracket size of 32 players.  The bracket will be hosted on Challonge.

Bracket Qualification and Seeding

The top 32 players with the lowest sumed times will be put in a seeded bracket using Challonge's single-elimination bracket format. The highest seeded players, in this format, will get first round byes if there are less than 32 players.

If less than 32 players are in this tournament, then all players will qualify and be placed in the bracket.

Streaming Bracket Matches to Twitch

Bracket matches will be streamed to Twitch.tv, without a stream delay.  Maintaining local recordings are highly recommended.

Bracket Workflow

This will be the workflow of a typical race (regardless of it being restreamed).  At the surface it may seem a bit complex, but it is to help facilitate automation.

  1. The player or restreamer will create a new race room in SRL using the ".startrace alttphacks" command.
  2. The player or restreamer, in discord, will use the command "$bracketrace x y" in the #brackets channel in discord where:
  1. x = the id of the race on the SpeedGaming schedule
  2. y = the full name of the SRL room in IRC (e.g. #srl-abc12 )
  1. The bot automatically sends the players, commentator, and tracker the permalink of the seed, the file select screen code, and the SRL channel that was specified.
  2. In the SRL room, confirm the bot joined the correct channel.  If so, type the command ".spoilerstart" to have the bot begin gatekeeping.  The bot will set the correct goal and post the seed and code in the goal as well.
  1. The requirement for entering a command in the SRL channel is to verify the correct channel was specified when $bracketrace command was executed.  Otherwise the bot could potentially hijack another race that was about ready to start.
  1. The bot waits for all entered players to either ready up or leave the race.
  1. The restreamer gatekeeping the race should leave the race once the spoiler log is ready to be distributed.
  1. The bot will drop out and allow RaceBot to begin the race.
  2. Oncve the race has began, the bot will whisper a link to the spoiler log to both of the readied up players in the SRL race room.
  1. If more than two players are in the match, the spoiler log will be posted as a normal message in the SRL channel instead of being whispered.
  1. A fifteen minute countdown will occur by the bot in the SRL channel.
  2. Once fifteen minutes have passed, the bot will will post the message "Log study has finished.  Begin racing!" to the SRL channel.  Both players may then start running.
  3. Nothing needs to be submitted after the race has concluded.  We will be able to retrieve SRL race data and chat logs to verify the winner.



Game Settings

All games played this tournament will have the following settings:

Winning Condition and Ties (brackets)

The race winner will be the first person to enter the Triforce Room and have screen fade to black after defeating Ganon.  This is based on the time the runner enters ".done" in the SpeedRunsLive chat channel.

A tie shall occur if both runners finish within at the maximum two seconds of each other.  If this occurs, the match will be replayed with a new seed.

Permitted Glitches

  1. Use of minor glitches are permitted.
  2. Major glitches are prohibited.

Definition of minor glitches: https://docs.google.com/document/d/1cio22fU4_cEsMcHN0I1KceUzB5P1aFgB7dOBrZuwRHU/edit

Randomizer Version

During this tournament, the version of the randomizer being used will only be v30.4, the latest version of the randomizer as of February 1st, 2019.  A dedicated instance of the randomizer website will be used for all matches during this tournament.


For the purposes of this tournament, all scheduling and deadlines will be in the U.S. Eastern Daylight Time zone.

Exceptions to Normal Tournament Rules

Normally in a randomizer tournament, the race is played blind (players cannot see what other players are doing).  For this tournament the following normally prohibited actions are allowed:

  1. Players are allowed to view their opponent's stream during the course of the race.
  2. Players are allowed to view the restream.
  3. Players are allowed to chat in their stream's Twitch chat.
  4. Players are allowed to chat in the restream's Twitch chat.

Confidentiality of spoiler logs (brackets)

  1. The spoiler log is for the players’ eyes only.  The log cannot be shared with others not directly involved with the race.
  2. The spoiler log will be sent to players via IRC in the SRL channel.  The log will also be sent via Discord direct message to the players.
  3. For the Round of 32, the commentary and trackers will also receive the spoiler log.  For the Round of 16 and later, this practice will be re-evaluated and a ruling will be made on continuing to provide the spoiler log to the commentary and trackers.
  1. Commentary will be advised to use discretion when using the spoiler log to avoid giving unintentional routing hints to players.

Prohibition of use of automated tools to parse spoiler log

The use of automated tools to parse a spoiler log are prohibited. Ctrl+F, Copy/Paste, and other standard text editor functions are OK. Automated tools may include but are not limited to:

  1. Any program that automatically parses the spoiler log for any reason other than for you to read it in its unaltered format (e.g., a text editor technically parses the spoiler log but it does not alter it in any way or present this information to you in any way other than as text)
  2. Macros
  3. Settings that color-code characters/symbols/words/etc automatically in your text editor. E.g., a person cannot setup Sublime or some other code editor to highlight words with progression items in Orange - or even to color code text with different levels of indentation. All text and symbols must appear monochrome when loaded initially. A player may manually color-code text if they wish, but may not do this with an automated tool. This falls under the category of “no automatic parsing”
  4. Map tools which parse a spoiler log to show you visually where each item is on the map. This falls under the category of “no automatic parsing”

If the player needs to be able to view the spoiler log in a different format, the player should ask a tournament admin for assistance.

Administrative rulings

The tournament admin team reserves the right to make judgement calls on situations that may not be fully outlined within this document.

Reporting suspected rule violations

If any person believes a violation of the rules of this tournament has occurred, it is requested that those reports be directed to a form at https://goo.gl/forms/jMaD7eLFJdhpCQG92 . It is prohibited to publicly talk about suspected cheating.

Changing Discord Name or Discriminator

Changes a player's discord name or discriminator must be declared to a tournament administrator.

Streaming Rules

  1. You must stream your race on Twitch and enable VOD saving
  1. Qualifier runs may be streamed to YouTube as an unlisted stream.
  1. Race VODs must be highlighted and left on Twitch for the duration of the tournament
  1. Qualifier runs that were done on Youtube should remain on YouTube in an unlisted format for the duration of the tournament.  After the end of the qualifier round unlisted Youtube videos will be made public, along with placement data
  1. Players are expected to respond promptly to admin requests made in the race channel (for bracket phase)
  2. Players who drop will be considered to have lost all subsequent matches.
  1. Records of previous matches will remain unchanged
  1. All forms of cheating are strictly prohibited. This includes but is not limited to:
  1. ROM/RAM inspection
  2. Using external tools to modify game memory
  3. Using automated tools to parse the spoiler log
  4. Sharing the spoiler log with others (bracket stage only)
  1. Public accusations of cheating will not be tolerated in any way
  1. Use this to report suspicious play: https://goo.gl/forms/jMaD7eLFJdhpCQG92 
  1. Harassment and bullying will not be tolerated in any way
  1. You should not take matters into your own hands, DM an admin instead or report the harassment here: https://goo.gl/forms/jMaD7eLFJdhpCQG92 

Hardware/Software Rules

  1. Allowed emulators include SNES9X 1.51+, SNESGX (Wii), BSNES/HIGAN and BizHawk
  1. ZSNES & older versions of SNES9X are banned
  1. Allowed flash cartridges include the SD2SNES and Super Everdrive
  2. The following console brands are allowed for play with flash cartridges or SD-cards:
  1. Nintendo
  2. RetroBit
  3. Analogue (including SuperNT jailbreak firmware)
  1. The following console brands are not allowed for play with flash cartridges or SD-cards:
  1. Hyperkin
  2. MiSTer
  1. Turbo controllers and functionality are both banned
  2. Emulator specific functionality is banned (e.g. save states, fast forward, hiding layers, etc)
  1. Pressing Up+Down or Left+Right simultaneously is banned
  1. Only one action can be mapped to any given button
  1. For example you cannot bind Up and Right to the same button
  1. Only one button can be mapped to any given action
  1. For example you cannot bind Up to two different buttons
  1. If your preferred emulator isn’t listed please contact a tournament admin. You may be asked to display your input settings/hotkeys and emulator version before or after a race.

Change Log

1/31/2019 - Synack - Initial draft

2/4/2019 - Synack - Further small adjustments, added section on the randomizer version and changing discord name/discriminator.

2/7/2019 - Synack/Qirn/Cyclone - Final review of document.

2/14/2019 - Synack/Qirn - Allow Twitch.tv streaming for qualifier runs