ALttPR Pilot Spoiler Tournament 2022

Welcome, everybody, to the second Pilot Spoiler Tournament!

What to Expect

Sign-ups will be open until December 3rd, 2022, 9:00pm EST at the following link:

https://forms.gle/aKBTiur9BuDh53sF9

All participants need to be members of the ALttPR Pilot Spoiler Discord: https://discord.gg/SBHWtUuGAZ

The runners need to have racetime.gg accounts connected to their Twitch accounts. Streaming will be required for all races conducted through racetime. Local recording will be required for all tournament asyncs and strongly recommended for all races as a precaution against internet failure. Delay is not required and cannot be requested. All races will be run under the Competitive Racing Ruleset as established by the Racing Council, found here: http://alttp.mymm1.com/wiki/ALTTPR_Racing_Ruleset.

Ensuring a safe, welcoming environment and maintaining the integrity of matches are equally vital to the health of the competitive community. As such, all staff and participants are expected to behave honorably, respectfully, and in good faith during discussions, scheduling, and races. In the event of interpersonal conflicts, everyone is expected to either reach an amicable resolution or privately contact staff through the #staff-mailbox or DM for help in doing so. The staff will exercise a zero-tolerance attitude towards any and all harassment.

The group phase begins December 5th and will be a round robin where each team will play six races. The tiebreaker week begins on January 23rd. The brackets phase begins January 30th and will be single elimination with best-of-three matches. Finals should be held no later than March 15th.

What is Pilot Spoiler

A pilot spoiler race involves a team of two racing an ALttPR seed against another team. Each team consists of a runner and a pilot- the runner has the seed, the pilot has the spoiler log. The runner’s job is to execute through the game, keep aware of what is needed, and communicate with the pilot. The pilot’s job is to gather and process information, strategize a route, and communicate with the runner. Whichever team finishes first wins the race.

Tournament Structure: Sign-ups and Seeding:

Sign-ups will open on November 1st, 2022, and close on December 3rd. Registration will be capped at the highest number divisible by four. (For instance, if we have 42 teams registered, the cap will be placed at 40 and the last two teams to sign up will unfortunately be dropped. If two more teams sign up, the cap will be moved to 44 and nobody will be dropped.)

During the sign-up period, teams are encouraged to complete three async seeds provided for seeding purposes and submit their in-game times. The deadline for submitting async times will be December 4th at 11:59pm EST. The mode for all three will be Open Keysanity. All three asyncs with their submission forms can be found at the following links:

        Seeding Async #1: https://forms.gle/Ah8pHpYovmrowQyr9

        Seeding Async #2: https://forms.gle/KWrDWTAqiNeqR3rg8

        Seeding Async #3: https://forms.gle/2EJbAgpx2feCQrXq5

The three times will be averaged into a final time. If teams are not able to complete all three asyncs (ie. due to focusing on League’s regular season), the teammates’ slowest, median, and fastest times in Pilot Spoiler Tournament 2021 and the Pilot Spoiler week of ALttPR League Season 4 will be used to fill in the missing times.

For example, let’s say RickyofKokiri and TreySpyre decide to team up and participate in the tournament but they don’t complete the seeding asyncs. Their representative run times from the 2021 events (1:23:48, 1:11:21, 1:05:00) would be taken and averaged (1:13:23) to determine their seeding rank. Their previous pilots and their own sessions as pilots will not be considered here as pilots do not have an official run time recorded.

If the seeding times are left incomplete with the 2021 events, the Pilot Spoiler week of League Season 3 will be looked at if necessary. If even that fails to provide three seeding times, blanks will be filled in by taking the slowest completed async time and adding five minutes. If just one blank is needed, Async 3 will be used; two blanks will use Asyncs 2 and 3; three blanks will use all three asyncs.

For example, let’s say RickyofKokiri and Hazukitty decided to team up and participate but they don’t complete the seeding asyncs. Hazukitty is a dedicated pilot and does not have any recorded times as a runner. RickyofKokiri did not participate in Pilot Spoiler 2021 and has only one relevant race in both League Season 4 and Season 3. Their times would thus be 1:05:00, 1:17:55, and 1:22:22, for an average of 1:15:07.

These alternate methods of determining a seeding time have obvious pitfalls for discrepancies and inaccuracies, so it is strongly recommended to complete all three seeding asyncs by the sign-up deadline to ensure that seeding is more reflective of your team’s current arrangement and skill.

Once the average time has been determined, teams will be ranked in order of seeding, with lowest times at the top and highest times at the bottom. Once the seeding is complete, the rankings will be divided into four quartiles.

Tournament Structure: Round Robin to Brackets 

The group phase begins on December 5th. Teams will be divided into groups of four, with rankings assigned to groups in a snake-style format so each group will have a team from each quartile. Teams will face off against each other twice for a total of six races per team. The group phase will last seven weeks, ending on January 22nd. The top two teams of each group will move forward to brackets.

The week starting January 23rd will be for necessary tiebreakers to determine seeding and bracket qualification. Teams are welcome and encouraged to complete tiebreakers during the group phase if able.

Brackets will begin on January 30th. Each match will be a best-of-three. Losing two games in a match will result in elimination from the tournament. All bracket rounds, including finals, should be completed by March 15th at the latest.

Team Structure

• Each team will be composed of two people.
• Both teammates must be present and involved in each official race- no temporary substitutions and no solo runs.
• Both teammates must be members of the ALttPR Pilot Spoiler server.
• Both teammates must have access to racetime.gg and be in good standing with the community.
• Teams are allowed to have a designated runner and designated pilot for all races, or they may switch roles from race to race as they wish. Roles may not be switched in the middle of an ongoing race.

A Note on Drops

This tournament is structured to be as flexible as possible for scheduling, including the option of asyncs. However, life just really likes to get in the way of a good time. If a teammate needs to drop for whatever reason, the following protocols apply:

• If the team has completed less than three races during the group phase, the remaining team member may find a permanent replacement for the remainder of the tournament.
• If the team has completed three or more races during the group phase, and at any time during the brackets phase, both team members will have to drop.

Available Modes and Commands

Race Structure: Workflow

• Teams will make a good faith effort to schedule their races for a time when all members can be present and participate. If such a time proves impossible to find, teams may request an async.
• All four team members must unanimously agree on the mode to play. The only options available are the five modes listed above. If there is any disagreement, Open Keysanity will be run by default.
• At the scheduled time, one participant will start a new ALttPR race in the “Beat the Game (Assisted)” category on racetime.gg and post the link to the racetime room in the group channel / thread on discord, pinging their teammate and opponents.
• The runners will join the raceroom and go live on Twitch. The pilots will need to be present in the room to get the spoiler log but they should not join the race.
• One participant will type the racetime mode command into the race room to roll the seed. IMPORTANT: The racetime command must have the “0” to ensure the race begins immediately without any study time.
• The runner and the pilot of one team will join a voice channel on the tournament discord; the other team will join another voice channel.
• When both runners are ready the race will begin and the spoiler log will be automatically linked in the racetime chat when the countdown hits 0. The pilots will download the log and begin studying it and directing their runners.
• The runners will, as normal, .done after crossing the bridge to the Triforce at the end of the game.

Race Structure: Reporting Results

• The winning team will report the results in the #race-results channel. This may be done by the runner or the pilot, but it should be done within 24 hours of the race completion.
• The post should list the team names, game number and mode, finish times, and provide a link to the raceroom:

Team Nine vs. Team Kokiri

Game 1, Open Keysanity

1:13:10 - 1:17:32

https:/racetime.gg/this-isn’t-a-real-link

Team Management

• Pilots can only download the spoiler log from the link provided in the racetime room at the start of the race.
• Runners and pilots will both start their respective responsibilities at the same time. There is no study period before the race. Pilots may watch their runners through discord screen-share or Twitch.
• The pilot’s responsibility is information-gathering and analysis and communicating with the runner. As such, only pilots will have access to the spoiler log, their opponent’s stream, and any notes they may jot down.
• The runner’s responsibility is execution of skill and game knowledge and communicating with the pilot. As such, runners will not have access to the spoiler log, their opponent’s stream, and any of the pilot’s notes.
• Essentially, the runner is to run the race under the same rules that apply to any other non-spoiler mode in the Assisted or Voice-Call categories. The rule exceptions that are standard for solo Spoiler Log races are applied only to the pilot. There should be no overlap in responsibilities or activities of the runner and the pilot other than effective communication.

Spoiler Log Management

Please note the following may be subject to revisions and clarifications based on feedback. If you have any questions, comments, and concerns that are not addressed here, feel free to ask on the tournament discord server.

• The spoiler log text file is to be opened only in plain text programs such as Notepad (Microsoft), TextEdit (Apple), EditPad Lite (freeware), and similar. Pilots may open as many individual instances of the file as you wish.
• Pilots may not copy portions of the spoiler log into another program or application that has greater search functionality than the text programs listed above. Such programs can be used for notes and routing, but not for studying the spoiler log itself.
• Pilots will study the spoiler log manually with arrow keys, mouse wheel, scrollbar, and the “Find”, “Find Next”, and “Replace” functions.
• Pilots may manually input item locations on a personalized note sheet or tracker. Pilots may manually copy relevant item locations from the log into another document.
• Pilots will not use any automated functions to take advantage of their PC’s superior processing power over their own eyes, fingers and mind. All searches must be manual. All highlights and marks must be made manually.

Restream Management

There are currently no plans for network restreams of any of the group races. Brackets will be broadcast on the ZeldaSpeedRuns network based on volunteer availability.

If individuals wish to run indie restreams on their own personal channels, they are free to do so as long as a) they get the permission of all participants beforehand and b) the race is not already being covered by ZSR or another indie restreamer. Additional restreams that feature commentary in a different language than the scheduled restream are allowed.

Please note that for any race to be restreamed on ZSR it is required that at least one runner have only game audio on their stream. This requires some technical set-up on the runner’s part to separate the audio sources (ie. with virtual audio cables) to make sure they can hear their pilot’s communication while the viewing audience does not. Indie restreamers may or may not share this requirement (ie. an indie restreamer may mute both runners’ streams and play their own background music while commentating).

All restreamers are encouraged to announce their upcoming restreams on the tournament discord server in the #watch-party-awareness channel.

Restreams should not interfere with the participants’ scheduling or prevent a race from getting started on time.