Welcome to the Duet Night Abyss speedrunning leaderboards and thank you for taking the time to view these guidelines! The goal of this guide is to provide a friendly reminder on what rules pertain to speedruns of this game.

If you need assistance, feel free to contact any of the moderators through Discord.

Run Philosophy

This leaderboard is considered to be largely glitch-free. If you see a glitch that seems easily avoidable, it is probably not allowed.

Global Rules

This is the general rules of the leaderboard. Please checkout category specific rules before submitting runs to a category

• Speedrunning is the act of playing a video game with the intent of completing it as fast as possible. Runs will be rejected if this intent is not present, at Verifier discretion.
• Original game audio must be audible for the whole run. However, runs with limited or no audio may still be verified at Verifier discretion.
• Your run may not be tool-assisted in any form, including but not limited to macros, scripts, any form of network manipulation, and cheats.
• One FPS cap may be used in a mission (switching outside of missions is permitted). Switching the FPS cap mid-mission, through in-game or external means, is disallowed. Verifiers reserve the right to reject submissions of poor viewing quality.
• Prism usage is banned.
• HUD should be on and visible at all times.
• Intentional out-of-bounds or wall-glitching techniques are forbidden.

Co-op Specific

• Co-op runs must begin and end with the same players.
• You may not run missions in parallel for Co-op runs.
• Any intentional disconnects/crashes will invalidate your submission for Co-op runs.

Submission Standards

• Video proof of all players POV is required for all runs.
• POV must contain the run in its entirety from loading screen to mission success screen.
• Moderators reserve the right to retroactively reject or remove runs where submitted video evidence is deleted, made private, or otherwise inaccessible.
• Corrupted gameplay or gameplay obscured or impacted by overlays may be rejected.

Starting Conditions

• Starting with any weapon equipped is allowed, provided that it is not fired or prepped in any way (rules may vary depending on the mission type; refer to category rules).
• Any run utilizing an ability that a player would not have if they had started the activity immediately upon load-in may be rejected at verifier discretion.
• Valid starting positions are limited to where a player could randomly spawn upon loading into the activity (read category rules for exceptions).

Timing Standards

See category rules

Category-Specific Rules

For more information on category-specific rules, check the individual category rules by clicking "Show rules" at the top right corner of a leaderboard. If you have further questions, feel free to head to our Discord server.

Moderator Guidelines

This section is to provide clarity for how Warframe leaderboard moderators conduct business here.

• Verifiers reserve the right to reject a submission for any number of reasons, including, but not limited to, poor quality, rule breaking, cheating, or misrepresentation. Verifiers are NOT allowed to reject runs based on bias of any kind. Contact the verifier that rejected your run for more details on the decision before contacting higher ranking moderators.
• Runs can be verified anywhere from a couple minutes to a maximum of 30 days. Please be patient and allow the verifiers sufficient amount of time to review your submission before contacting them.
• Leaderboard verifications will be placed on hold for up to one week after every major update to allow Digital Extremes time to send out hotfixes to address bugs with the update.
• "Testing" a moderator's ability to verify a run is considered a bannable offense from speedrun.com according to site staff. Offenders will be notified to site staff in extreme cases.
• All runs can be disputed with proper claims, including a moderator's run. Please contact a moderator to discuss the legitimacy of a run.

First Action Rule

First Action is a method used to highlight when a runner starts an attempt of a category. It is mostly utilized for the highly accurate frame counting, where verifiers and runners use it as an agreed starting reference for timing. While this rule is meant to stamp out loading issues, simply standing around at the beginning for an excessive amount of time can result in your submission being rejected for AFKing.

First Action is defined by the following criteria:

• Any mouse or thumbstick movement to look around.
• Use of any gear item.
• Any movement of the Warframe.
• Opening the Pause menu.

Things that are not considered First Action:

• Opening the gear wheel. Please note that moving your cursor is considered First Action. This bullet point is mostly used to verify proper gear items.
• Opening the overlay map (not the expanded map from the open-world content).
• Viewing the quick view mission summary. This is defaulted to Tab on PC only.

Please note that categories may NOT have First Action applied to them, such as the Capture categories. Always check the rules for each category for timing standards.

Macro Rules

• Macros that press multiple keys are not allowed.
• One action macros (rebind macros) are allowed.
• A single autofire macro (single-button spam) is allowed.

Frequently Asked Questions

What is the accepted timing standard for this category? If not explicitly stated, then the timing standard falls underneath the one of three timing standards explained in this guide.

For certain categories, what order should I complete the missions in? For most cases, there is no order to the missions you need to do. Feel free to take on whatever order you like. For certain categories where there is an obvious progression metric (e.g. Immersive Theatre 1-12), you should follow the mission completion in order of that metric.

Are exploits, glitches, etc. allowed? If it's going to be patched or if you have any doubts, don't attempt it. Generally, any form of OOB or wall-glitching is not allowed.

Why differentiate Solo and Co-op runs? This allows for a better system of record-keeping and allows players to review runs that fit their playstyle. Certain categories also ban Co-op due to potential verification issues.

Why are certain categories or runs listed as "LEGACY"? Situations for these categories cannot be recreated anymore - that is, it would be unfair to compete against times that have a blatant advantage against runs that could be done now due to changes in speed, loading, or other factors. The game is changing constantly and these leaderboards attempt to make as little changes as possible, but it has to stay adaptable.