Hello. There's been a number of questionable issues regarding Momodora 3 runs for a while now. Specifically not everyone's pause jumps are the same, the rules for autofire are insufficient, and not everyone is splitting at the same end timing. Therefore, there's going to be a few changes to the leaderboard rules to address these. The changes aim to promote transparency and maintain current accessibility and competition to the speedrun.

—Uncommon pausing frequencies will be allowed.

I don't ever intend to ban this as this will prevent some people from running the game. However, if a method to achieve commonly observed frequencies is available then I do wish to encourage it. Unfortunately, no such methods were found yet.

—Tricks and skips that aren't achievable via the common pause frequency will be banned from main categories.

This includes exiting Prim Doralina's room to the right as well as Cashias skip. For most people, doing this would require buying certain hardware or using multiple devices or a macro.

—You may bind autofire of only pause with an initial delay to a controller.

It's recommended to use Joy2Key with an autorepeat of 16 times per second and a start delay of 233 milliseconds. These numbers will result in slightly higher jump height than the commonly observed pause jump height but it was the most accurate that could be found. If you wish to use your own autofire program then please detail its name and your settings in the run submission so I can check it. I'm unable to provide universal values/settings because programs I tested behaved differently even with the same values.

—Multiple instances of pause autofire are banned from main categories.

Autofiring pause with two keyboards, keyboard + controller, etc simultaneously will result in higher height.

—A common end timing will be enforced.

The rules currently state that timing ends upon losing control. This would be the moment you talk to the final boss. However, some people have been splitting when the player lands which occurs after talking to the final boss, therefore creating an inconsistent end timing. Currently, it's undecided which end timing should be used but once decided, all current times on the leaderboards will be reviewed to match this change. EDIT (9/28/17): Runs on the leaderboards will now be adjusted to end timing at the moment you talk to the final boss.

Controversial issues that still remain:

—Higher than common pause rates may result in needing more or less pauses to perform a pause jump. Pause jumping is performed often throughout the run so the frame differences will add up.

—Pause jumping directly to the second springpad in the last room of Dim Hideout is possible but rare with the common pause frequency. Having a higher pause jump will make this very consistent. Optimally this isn't faster though.

—The usage of multiple input devices (e.g. controller + keyboard) may be questionable. For this game, the biggest concern would be being able to achieve higher pause jumps with two devices but this issue has already been addressed.

—Allowing usage of 3rd party programs to autofire on controller. It'll be ideal to not allow this at all but for some people who prefer controllers, using controller + keyboard may not be a practical option. Generally holding a button that is bind to pause on a controller will not cause it to autofire, therefore giving keyboard players a significant advantage. With a configured pause autofire, the execution of inputs between keyboard and controller players will be relatively the same.

If you have any questions or objections then please post them here.

With the addition of the [News] section on SRC, this thread is no longer necessary and will be locked.