Racing Information

On this page you will find a detailed explanation of everything you need to get started racing in Majora's Mask Randomiser.

This will also include some helpful information, such as some more well-known as well as more uncommon crashes that can occur and links to helpful resources.

Requirements:

A racetime.gg account which can be created on the website here. This is mandatory for any tournament races.
A streaming software such as OBS or Xsplit. Preferably a software that allows you to both stream and record your race simultaneously in the event of your livestream crashing.
A Twitch.tv account, which you must use to livestream your races.
An active Discord user account in the Majora's Mask Randomiser server. This is where we announce qualifications, brackets, and keep runners up-to-date with racing information.
A method of patching your randomised seed. Please note: These seeds are provided 15 minutes prior to an official race, so allow yourself that much time to patch and upload your seed.
A method of playing your randomised seed. Further details will be provided of allow Emulators and Platforms below, however the MMR Discord does provide a pre-built PJ64 emulator tailored especially for Majora's Mask Randomiser.

Optional but recommended:

Livesplit: This is a software typically used in Speedrunning, however it can be connected to Racetime.gg to automatically start/stop when a Raceroom is initiated and finished, allowing viewers and Moderators alike to have an easy to see timing on-screen whilst you race. It can also be hot-keyed to mark yourself as 'Done' or to 'Forfeit' more quickly.
A controller input display. There are many of these input displays on the market now, and like above they provide a clean view point of your controller for viewers to engage with.
An Item tracker; these are used to track which items you have acquired, your hint distribution, and in the case of a map tracker, remaining and logical locations left to be checked. These range from more well know trackers such as EmoTracker to community made trackers. I recommend joining the Discord and searching for a community made tracker if you're intending on racing a particular subset of settings. In particular, FifthWhammy and TheOtherSection provide excellent, easy to use GossipStoneHD trackers for various settings lists.

Racing Rules:

Below you will find all of the rules surrounding racing, it is recommended to check back to this page occasionally as the rules can and are periodically updated.

General Racing Rules:

All races unless otherwise stated use the 'Standard Ruleset' which encompasses allowed and banned tricks. These will be given further below.
Timing rules are identical to the Speedrun scene of Majora's Mask. Timing begins when you press 'A' on 'Yes' on the file select screen, and timing ends on the first frame that Majora's Wrath dies.
All race entrants must stream during the race. Ensure you have a VOD recording as well in case you go offline.
VODs must be available for a reasonable amount of time after any race participation in case of a proof call.
Races with a custom goal may use any ruleset, but if no ruleset is specified in either the goal or the race info, the Standard ruleset applies.
You must under no circumstances be present in an opponent's stream or a public restream for any length of time, this will result in an immediate disqualification and strike against your account.
Outside help, i.e: from viewers or people in your gaming area is strictly not allowed. The only exception to this is if a Moderator or Race Moderator contacts you to inform you of any circumstances which may affect the race. If for any reason a viewer does provide a hint/spoiler, contact a Race Moderator immediately. It is also recommended to be in Emote or Sub only mode on Twitch.tv.
If for any reason you need to call FPA, simply post in the Racetime.gg chat FPA and the Race Moderators will provide further information from there. More information regarding FPA can be found below.

Restream Guidelines:

Sometimes when racing in a Tournament, the opportunity will arise for you to be showcased on a separate stream. This is known as a 'restream' where another team captures your gameplay and showcases it on their end with your opponent(s) viewpoint also visible. Whilst you do reserve the right to decline a restream, it is a great opportunity to review your footage against a fellow competitor with live commentary after the fact.

However, if you do accept the invitiation to a restream, there are some guidelines that are typically followed when racing. In the section below we have listed some dos/don'ts when on restream.

Pre-Race Setup:

When appearing on restream, it is best to ensure you go live with plenty of time to spare in order to give the restreamers plenty of time to crop and adjust your gameplay screen and balance your audio levels. If going live with a stream delay (typically 15 minutes) it is best to take this into account. For example, if your race is at 15:00, and you have a 15 minute delay, go live at 14:30 to give the restreamer the same 15 minute setup period.
Ensure your notifications such as Subscriber/Follower events are disabled, and any channel redeems you may have are disabled. We all enjoy a clip of Gordon Ramsay from time to time but it can be very disruptive during a restream.

During a race:

Prior to starting a race, the restreamer may ask if you have 'clean audio'. This is in reference to whethere or not you will be audibly speaking to your community during the race. If you will be muted and agree to provide clean audio, please remain muted for the duration of the race until you are called in for an interview.
Do not re-enable any Subscriber/Follower alerts, whilst we like to celebrate our communities, as stated in the pre-race setup it can be disruptive to a restream.

Post-Race:

After a race you may be asked to join the commentators for an interview. This involves being a member of the respective Discord (often ZSR), where you can find a 'waiting room' voice channel. Simply join that and a commentator or restreamer can pull you into the room to join the restream. Please be aware, these streams can attract hundreds of viewers, so please remember basic civility should apply at all times.

FPA (Fair Play Agreement):

The Fair Play Agreement is the agreement that in the event of a crash or otherwise unavoidable situation occuring during your race that causes you to lose progress, you can call for a 15 minute grace period to attempt to restore your progress back to where you originally were.

What this entails in practice is that you must restore your progress as close to 1:1 in those 15 minutes, you cannot bypass items you know are 'junk' or 'not required' that you previously acquired in order to save time e.g; Heart pieces, ammo refills etc. Whilst your old knowledge may be kept, you cannot gain new knowledge in this time e.g; You previously acquired a hint stone near Road to Ikana in Termina Field but not Near Path to Mountain Village in Termina field, you cannot acquire the second hint stone during FPA even if you travel past it. Whilst your overall route may vary during this time, you must still end your FPA timeframe with the same items you had when you crashed, which also includes attempting to get your rupee/ammo count as close as possible as to when you crashed.

The final time you used during FPA will be deducted from your final 'finish' time in the raceroom. For instance if it only takes you 7 min 13s to return to your pre-crash state, this will be the only time subtracted from your final finish time. However the maximum amount of time that can be reasonably deducted is 15 minutes.

In the event that you or your opponent call FPA in the raceroom, do not wait for a Race Monitor to respond. If you personally call FPA, act as though FPA has been enabled and begin your returning route. If you see your opponent call FPA, do not ask for more information, simply keep playing. If necessary, a Race Monitor or Moderator will contact you via Discord.

Ultimately, the decision will be made to accept the FPA once the race concludes, and the Tournament Moderation team will keep in close contact to update you on the resulting outcome.

FPA Quick Guide:

If you believe you have encountered a crash/bug that falls under FPA and need a quick guide, check here:

- Call for FPA in the Raceroom, this will grant you 15 minutes to return to the exact point you were before the crash.

- Continue playing as normal, a Race Monitor or Moderator will be contact you to guide you through the process while you play.

- If your opponent calls for FPA, continue racing as normal, do not pause or forfeit your race.

- Whilst collecting your previous items, you must acquire all non-essential items you had before crashing. Heart pieces, ammo refills from chests etc.

- Your final time used for FPA will be deducted from your final finish time at the end of the race, and the Tournament Team will decide whether the FPA was valid or not.

Methods of playing your seed during a race:

In the following sections we have listed the various ways to play your seed, whether you play on native hardware or on an emulator, please refer to the below guide to understand any special requirements (if any) in order to race your seed in your chosen method.

Your race seed will be provided by the Race Monitor or Moderator, either through a patch file or by rolling the seed directly within the raceroom you're part of. This will link you to the Majora's Mask Website Randomiser with the relevant patch file pre-loaded for you.

Hardware:

Below is a list of the recognised hardware you can use to race. You do not need to show your FPS when using native hardware to race unlike when using an emulator.

Everdrive 64 - No special requirements to race.
WiiVC - No special requirements to race.
Analogue3D - No special requirements to race.

Allowed Emulators:

Below is a list of the recognised and allowed Emulators as well as the respective settings required to race using them. Please note, all Emulators carry an additional ruling that you must show your FPS at all times whilst racing.

Project 64 (PJ64) - No special requirements when using PJ64 to race.
Dolphin Emulator - Your CPU overclock must be set no higher than 115% and this must be shown on stream prior to beginning the race.
Retroarch - No special requirements when using Retroarch to race.
Bizhawk - No special requirements when using Bizhawk to race.

Banned Emulators:

Below is a list of Emulators banned for racing.

ModLoader64 - Due to the emulation being slightly faster, this emulator is not allowed in racing.
Any mobile emulator - This is due to us being unable to reliably moderate the settings etc used when racing.

Standard Ruleset

Here you will find a list of the tricks allowed and banned whilst racing a typical 'standard ruleset' seed. Unless otherwise stated, the Standard Ruleset always applies during any race.

Allowed Tricks:

Recoil Flip
Long Jump
Flame Storage
Gainers
Ground Jump
Death Warping
Voiding to reset Link's position
Broken Deku Stick
Jumpslashing while mid-air for more distance
Jumpslashing against walls for recoil
Momentary Antigravity
Lily Pad Jump
Deku Palace Doorframe Backflip (SoA early)
Stalagmite Jump
Snowhead Tunnel Jump
Great Bay Temple Boss Key Early
Zora High Ledge Grab (whether A button says Surface or Swim)
Stone Tower Boss Key Early
Early Eyegore
Precise Bow/Hookshot Aiming
Deku Playground Rupee Displacement
Avoiding Cutscene Triggers (ex: Lens Cave owl)
Passing through the back of a one-sided collision (e.g. Goron Jump to the Swamp Tourist Center HP)
Barn Shot
Cheating the Treasure Chest Game via clipping, rolling or passing through blocks.
Goron Rolling on the roof in Pirates' Fortress from the Hookshot Room door to the rear door of the 3 Guards room.
Any accidental glitch which does not grant the player an advantage is okay.
Incarnation Bomb
Big Octo Skip
Damage boosting (including Goron Bomb Jumps)
Fish Walk
Early Mountain Village via Snowball Hop
Snowhead Temple Compass Room Ice Switch (Roll into the Ice at a precise angle to trigger the switch)

Banned Tricks:

Recoil Jumps
ISG
Clipping through Ice
Megajumps
Megaflip
Megasidehop
Hookshot Jump
Bomb Hovering
Hidden Owl
Seam Walking
Action Swapping
Equip Swapping
Weird Shot
All forms of superslide
Superswims
Flying Zora
Bottle Duplication
Removing Light Arrow Blocks/Switches with Spring Water
Goron Lullaby Skip
Going out of bounds (any area which is beyond the boundary walls of the map such as an outer seam, or any area which is exposed to the lowest void plane in the map)
(including Goron Rolling on the roof in Pirates' Fortress from the Hookshot Room door to the upper chest near the roof hookshot target)
Ocarina Diving
Gold Skulltula Token / Heart Piece Duplication
Something except for a sword on B (excluding normal circumstances like riding Epona, and known randomizer problems (losing sword after riding Epona))
Opening Flaming Chests
Time Stop
Zero/Fourth day
SoT Storage
Z-slide
A-slide
Wrong Warp
Void Warp
Ocarina Items
Walking while talking
Causing a switch to remain pressed longer than it should
Passing through collision from the front (e.g. all forms of clipping)
Item Manipulation (BA, RBA, GIM)
Using restricted items
SRM (Stale Reference Manipulation)
ACE (Arbitrary Code Execution)
Text Overflow
QPA (Quick Put-Away)

Please be aware that list can be updated at any time, whilst we will endeavour to update players to any changes via Discord it is worth referencing this list from time to time to ensure you do not get caught out. Also be aware, depending on tournament settings, some banned tricks may be temporarily allowed.

Any newly discovered tricks should also be regarded as banned unless otherwise stated pre-race by the Race Monitor or Tournament Team.

Known Issues:

Here you will find a list of known issues you may encounter whilst racing in MMR. As these are known issues and can be found both here and in the MMR Discord here, any crashes/softlockes etc caused by these issues will not fall under FPA. Whilst we will endeavour to keep this list up-to-date, we recommend to keep up to date with the #known-issues channel in the MMR Discord.

Vanilla Specific Issues:

Rarely, around half-way through the dog race, a dog can be considered to be on the finish line
Burning a curtain in Igos du Ikana's room after defeating his minions but before starting the fight with Igos himself can crash the game.
After giving the town scrub the moon's tear, and giving the swamp scrub the land deed (thus relocating the swamp scrub to the town), beating town archery then going directly to South Clock Town crashes the game.
Performing various actions after playing a song for the Guay in Termina Field can crash or softlock the game. Best to reload the scene afterwards. Reproducible: drop bugs into soft soil. Potential: being revived by a fairy; playing a song at the northern song wall; maybe others.
Mashing through the message that kicks you out of the Doggy Racetrack after ~~winning~~ losing the Dog Race softlocks the game.
After defeating Twinmold as Giant Link while standing near where the blue warp will appear, if you step away just far enough for the blue warp to start spawning at the same time as taking off the Giant's Mask, the game will softlock when you take the warp. Putting the Giant's Mask on and taking it back off fixes the issue.
If you talk to Gorman in the Milk Bar just before the clock hits 5 AM, the game softlocks.
Having the hookshot in your hand and playing song of healing for the gibdo mask check crashes the game when you're supposed to receive the item.
Receiving a Sword whilst Fierce Diety makes you repeatedly swing it. Taking off Fierce Deity's Mask fixes the issue.
Various softlocks when navigating terrain as Fierce Deity (e.g. getting permanently stuck in Bombers' Hideout; or climbing the terrain near Zora Hall; can't get out of Bio Baba grotto water)
Pulling out the Ocarina immediately after Deku Playground day 3 can softlock the game.
Mashing A after dropping a fish into the Lab Fish tank can softlock the game.
Spawning in the upper area of Ikana Graveyard (either from defeating Keeta, exiting Dampe's House or exiting the grotto) and attempting to soar to Mountain Village crashes the game. The crash can be avoided by first soaring elsewhere or entering a grave then re-entering Ikana Graveyard in the lower area. Entering Road to Ikana will NOT avoid the crash. Entering Road to Ikana, then re-entering Ikana Graveyard will NOT avoid the crash. Entering Road to Ikana then entering Ikana Canyon or Termina Field will avoid the crash.