Mystery

Registration

Sign ups for the Super Metroid Randomizer Mystery tournament is open and will close on Friday, March 27 at 3:59 AM. Please be sure to be officially registered before that time so we can get the matchups finalized that weekend for the official 1st week of the tournament, which will begin Wednesday, April 2nd.

Prior to the tournament, we will be confirming your participation and getting players to join the Discord server. Discord will be the official medium used to communicate with players and schedule races. Players must join the discord server to participate.

Format

The tournament will be swiss format with each match being 1 race. There will be one required match per week (Wednesday - Tuesday).

There will be 6 weeks of swiss competition, which means at least 6 guaranteed matches for each runner. Note, we are starting each week midweek in the hopes that fewer players will miss entire weeks while on vacation.

Qualifying Races + Seeding Procedure

There will be 4 qualifying races available at different times (as to accomodate as many time zones as possible).

• Saturday, March 21st 8PM Eastern: Qualifying Race 1
• Sunday, March 22nd 12PM (Noon) Eastern: Qualifying Race 2
• Saturday, March 28th 8PM Eastern: Qualifying Race 3
• Sunday, March 29th 12PM (Noon) Eastern: Qualifying Race 4

Seeding for match pairings for the 1st round of Swiss will be based on the average of a runner's top 2 qualifying race times.

Mode

The mode of this tournament is "Mystery II". What this means is runners will not know what the mode is until the race starts and they start playing the seed. The goal will always be to kill the “G4 bosses”, defeat Mother Brain and escape to the ship. Available settings will be weighted as follows:

These percentages are subject to change before the tournament starts. We will be testing them in the weeks leading up to the tournament. All percentages will be finalized at the same time that first round match ups are announced.

Timeline

• March 5: Registration begins
• March 27: Registration ends at 3:59 AM
• April 2: Start of swiss week 1
• May 14: Last day of swiss weeks
• May 15: Bracket scheduling can begin

Scheduling

Please do your best to communicate with your scheduled opponent and get your match played before the deadline of each week. Because we are using a swiss format we can not allow races to be played after the deadline of each week (Wednesday-Tuesday). If both players are considered no-shows (worst case), both players will be forfeited. Also please try your best to schedule your matches at least 24 hours ahead of time. Do not expect a restream if a match is not scheduled at least 24 hours in advance.

The first two rounds of brackets will get 3 weeks total to play (subject to actual number of bracket players). Each subsequent round will have one week to complete. Bracket scheduling can be more lenient, so long as any player needing extra time message the admins immediately upon knowing they need that time.

No Shows

• There will be zero tolerance for no-shows. If a player is a no-show, that player will forfeit the match.
• A player will be considered a no-show if they are not in the race room by 15 minutes after the scheduled start time, and has made no effort to contact their opponent or the admins.
• Even if said contact is made, if a race is unable to be played at that time, or reasonably be rescheduled within the weeks deadline, the player that was the original no-show will forfeit the match.

Playoff Structure

• Everyone with at least a 3-3 record will make the playoffs, with seeding determined by final swiss rankings
• Playoff matches will be best of 3 single elimination
• Races 1 and 2 are required to be scheduled back to back, with race 3 encouraged to follow
• The bracket (depending on number of participants) will most likely look like a 64 player bracket with several top records receiving byes. Match ups will be reverse seeding (i.e. 1 vs 64, 2 vs 63, etc).

Ties

1. The time on Racetime will be the official time for the race, unless otherwise specified.
2. If the race is within 3 seconds, a retime via frame count will be done by admins only if it is requested by the player finishing second on Racetime.
3. If a frame count is requested and confirmed to be warranted by admins, the admins will time both racers’ VoDs and determine the winner to the best of their ability.
4. If a clear winner can be determined via a frame count, the race result will be changed (if necessary) to reflect the results of the frame count.
5. If a clear winner cannot be determined via a frame count, the race result will fall back on the original Racetime results. If the original Racetime result was a tie, the final result will reflect that.

Async Races

It is the intention of this tournament that all races be run live/synchronously if reasonable. Nonetheless, we accept that due to the nature of Swiss tournament time constraints, there may be exceptions warranting use of asynchronous (async) races. All async races must be completed by the normal round deadline for the appropriate round.

If an async race is needed, the player requiring the async (or an agreed upon player should the need be mutual due to schedule incompatibility) should contact an admin as soon as the need is known. Organizers reserve the right to deny async requests. The player requesting the async will generally be expected to run the seed first.

This first player, referred to as “Player 1”, will follow the following procedure:

Player 1 will arrange a time with an organizer for the async race to be run. Player 1 will receive a link to the race seed ~5 minutes ahead of the scheduled time, and will download/run the race seed starting no more than 10 minutes after the seed is sent. Player 1 will locally record the gameplay (and will not stream gameplay to Twitch, etc.) and report a time and an end game screenshot showing completion time and item collection rate to an organizer upon completing the seed. Player 1 will additionally upload the local recording as an unlisted Youtube video and provide a link to the organizer.

The player to complete the seed second, referred to as “Player 2”, will follow the following procedure:

Player 2 will arrange a time with an organizer for the async race to be run. Player 2 will receive a link to the race seed ~5 minutes ahead of the scheduled time, and will download/run the race seed starting no more than 10 minutes after the seed is sent. Player 2 may stream gameplay as normal, but is expected to archive vods as normal and/or be able to provide local recording evidence of gameplay as is typical. The only difference between this and a normal race is that gameplay stream delay is not required; other tournament rules must be followed. Upon completion of the seed, Player 2 should contact an organizer with completion time and item collection rate, and the organizer will provide the link to Player 1’s gameplay video for Player 2 to review.

Organizers will inform both players of the race result once both players have completed the seed.

Please note: Asyncs are not intended to be for situations where players can't find a convenient time to schedule. The admins will only allow asyncs in situations where it is deemed that opponents absolutely cannot find a mutual time.

Additional Race Procedures and Rules

1. Auto tracking is permitted only for item tracking. You MAY NOT use auto map-tracking.
2. Use of the FUNtoon2SNES room time tracker, or similar tools, is prohibited, due to their ability to tell apart surprise and shifted boss rando settings.
3. Runners will use RaceTime.gg to time and record their race. All runners must have a RaceTime account. The time listed on RaceTime is the official time for the match. All runners are required to stream and to follow all RaceTime rules.
4. All races must be streamed on Twitch. Additionally, all runners must have the vod of the stream available for potential review by the organizers for at least 1 week after the race. Failure to comply with this rule could lead to a win being overturned. If you have not enabled VOD saving on Twitch please go here for instructions
5. Players may not be in a restream channel or any chat (twitch, discord etc.) during a race.
6. Watching other racer’s streams or any restream while racing is not allowed.
7. Runners caught or who are suspected of cheating will be automatically forfeited from further participation in the tournament. All decisions on cheating will be made by the organizers and will be final.
8. Any form of out of bounds is banned, as is Underflow, wrong warps, and memory corruption.
9. The tournament will use the latest stable version of the DASH Randomizer for all races.
10. In the event that a new stable version is released, all subsequent races will move to the new version.
11. Runners must make their audio available when restreamed and may only use default audio. Use of alternate audio is prohibited in all cases. When on restream, runners must turn off their mics and all alerts.
12. Runners may use alternate color palettes and/or alternate sprites. All alternate sprites must have the same animation for screw attack with and without space jump. Failure to have the correct animation will result in a warning for the first infraction and a forfeit for any subsequent infraction.
13. Exceptions to the above rule: The Samus hitbox sprite may not be used at any time.
14. Any disputes will be handled by organizers and all decisions will be final.
15. All swiss races that end in a tie will result in both players receiving 0.5 points for the round. Playoff races will be re-run.
16. While not required, it is highly recommended that runners locally record all their races. If your stream goes down during a race (internet issues) you may be asked to provide proof of your finish time. Note that “filming” your screen with your phone (or other camera) is an acceptable form of proof. If you have internet or technical issues (for a moderate/significant period of time) and cannot provide a local recording then you will be forfeited from that match. There will be no rematches.

Stream Delay

Stream delay is not required.

Hardware Rules

• Runners may use cartridge, flashcart, approved emulator, SNES classic or a docked Analogue Pocket.
• ZSNES and Snes9x (v1.43 and below) are banned.
• The run-ahead feature in RetroArch is also banned.
• Turbo controllers and functionality are both banned.
• Emulator specific functionality is banned (e.g. save states, fast forward, etc).
• Pressing Up+Down or Left+Right simultaneously is banned.
• Only one action can be mapped to any given button.
• Only one button can be mapped to any given action.