Meta: Rules and Guidelines

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](https://discord.gg/dPKnZfGfFj).

# 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](https://discord.gg/dPKnZfGfFj) 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](https://www.speedrun.com/The_Site/thread/6sknq). 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](https://www.speedrun.com/wf/guide/oe489).

**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.

Meta: Timing Standards

# In-Game Time

Popularly abbreviated as IGT, this is the easiest, but least accurate method of timing. This uses the timer located at the Mission Success/Failure screens and does not require any other extra steps from the runner. Simply showcase your run and then take the time at the end which is then inputted into your submission.

IGT works best for multi-mission speedruns under the Full-game Leaderboard, since it allows a metric to bypass loading times. For single missions, IGT can actually be slower than a timer or framecounting.

## IGT Standards

- The entire run from the [First Action Rule](https://www.speedrun.com/Duet_Night_Abyss/guides/8p9ai) to Mission Success must be shown in your video. Cutting any portion of your video will result in your submission being rejected.
- For multiple missions, you are **REQUIRED** to provide your Mission Success times in the description of your submission.
- For multiple missions, you are not allowed to abort any portion of your submission, except in the case that the mission turns into a different objective. Aborting will be considered multi-segment and invalidate your time. If you need to abort a mission during your run, consider using one of the below timing standards instead. If the mission turns into a different objective, it has to be visible enough to not dispute and you are expected to immediately abort the mission and reattempt it.

# Framecounting

This is the most accurate method of timing available. It is a calculation of the difference between two frames of reference in a video divided by the FPS.

[quote] (endFrame - startFrame) / framesPerSecond [/quote]

This type of timing is considered Real-Time Attack (RTA).

## Framecounting Standards

- You must provide the first frame, the last frame, and the frames per seconds used to calculate the final time in the description of your submission.
- In the case of dispute by a verifier of final time, you will be asked to provide the raw footage used to calculate your final time. If a consensus is not agreed upon by the verifier, a separate moderator, and yourself, the slower of the two times will be used to represent the run's final time.

## Framecounting Tools

- You can framecount on YouTube using the [YouTube Frame Timer](https://somewes.com/frame-count/). Properly follow the directions on the page and you should output a nearly accurate time, with differences only in the milliseconds.

Mebius

**作为排行榜版主，我应该以身作则，目前需要一定时间挖掘游戏速通分类，以及更全面了解游戏，所以暂时先禁止排行榜30天，或许会提前解禁，大家有什么问题可以到板块图标右边的Discord社区提问。**

As the moderator of the ranking board, I should set a good example. Currently, it will take some time to explore the category of game speedruns and gain a more comprehensive understanding of the games. Therefore, I will temporarily suspend the ranking for 30 days. Maybe it will be lifted earlier.

If you have any questions, you can post them in the Discord community to the right of the board icon.

Duet Night Abyss

Mediation

Chase Bounty

Level 180

thesmollestbun

ashiv

// 1.5

TR 65

TR 64

TR 62

TR 60

TR 55

TR 50

TR 45

TR 40

TR 35

TR 30

TR 20

TR 15

VI - Lv. 80

V - Lv. 70

IV - Lv. 80

I - Lv. 40

IV - Lv. 100

VII - Lv. 70

VII - Lv. 80

// 2.0

Beta

III - Lv. 110

II - Lv. 75

I - Lv. 60

Anemo

Electro

Hydro

Pyro

Lumino

Umbro

IV - Lv. 60

300%

270%

240%

Classic Act 1-7

Featured Act 1-3

Immortal Act 1-12

1.2 Yuming

1.2 Zhiliu

1.1 Fushu

1.1 Kezhou

1.0 Fina

1.0 Psyche

// 1.2 - Yuming

1.2 - Zhiliu

1.1 - Fushu

1.1 - Kezhou

1.0 - Fina

1.0 - Psyche

Immortal Any Act

Featured Any Act

Act 12

Act 11

Act 10

Act 9

Act 8

Act 7

Act 6

Act 5

Act 4

Act 3

Act 2

Act 1

Berenica 贝蕾妮卡

Daphne 达芙涅

Fina 菲娜

Fushu 扶疏

Hellfire 海尔法

Kezhou 刻舟

Lady Nifle 妮弗尔夫人

Lisbell 利兹贝尔

Lynn 琳恩

Margie 玛尔洁

MC/Vita 主角

Outsider 奥特赛德

Phantasio 幻景

Psyche 赛琪

Randy 兰迪

Rebecca 丽蓓卡

Rhythm 黎瑟

Sibylle 西比尔

Tabethe 塔比瑟

Truffle and Filbert 松露与榛子

Yale and Oliver 耶尔与奥利弗

Zhiliu 止流

Yuming 煜明

Immortal

Featured (Act 1-3 only)

Version

Trial Rank provides additional boosts, select the closest trial rank you've achieveved e.g. tr63 would choose tr62.

Trial Rank

Difficulty

Difficulty Level

Which element the summit is focused towards

Element

Depth

Theatre Act

Theatre Patch

Character

Repertoire

Segment

Theater Version

Boss Level

Hi all, we are going to be pushing the leaderboard stuff hopefully on or before 1.1, we are looking for more moderators and verifiers right now, let us know if you're interested.

Join the DNA Speedrun Community here:
[https://discord.gg/dPKnZfGfFj](https://discord.gg/dPKnZfGfFj)

Name	Author
Meta: Rules and Guidelines	Mebius 8 months ago
Meta: Timing Standards	Mebius 8 months ago