After having internal discussion and receiving community input, the mod team is excited to announce a much-needed update to our moderation and run verification policies.

Rules update

The community ⁠rules have been updated with clearer language, wider coverage, and an introduction covering general intent and a discretion clause. Additionally, we will be handling cases involving evidence from outside our discord server on a case-by-case basis, where context is considered to ascertain whether a member is potentially harmful to the community.

To view the current community rules and ban appeal policy, please refer to this post: https://www.speedrun.com/destiny2/guides/n85oi

Submission bans

In the past, we have banned certain individuals from submitting to speedrun.com in rare extreme cases; now that we have created a clear and structured unban policy, we are expanding the scope of any ban to include submissions, whether solo or fireteam. Since this is a new policy and we don’t want to punish members retroactively, there are a couple caveats to note here:

• Members that were banned before this announcement may still submit runs until March 10, 2026 in order to allow for unban appeal processing. After this period elapses, any and all banned members will not be able to submit runs.
• Members who are unbanned may submit runs from during the period they were banned for once they are unbanned.
• Members who choose not to join our discord server in order to avoid this policy will still have their runs rejected if they would otherwise be banned.

If you feel that your ban is unjustified, you can still message a moderator at any time to have your case reviewed. If there’s a mistake, we will of course handle it immediately without having you wait 30 days for something you didn’t do.

Unban Policy

• After being banned, members cannot submit an appeal for at least 30 days.
• After this 30-day period, banned members may message any member of the mod team to submit an appeal.
• All appeals are to be voted on by the members of the moderation team.
• An appeal's result will be communicated to the appellant when a decision is reached.
• If rejected, members will not be able to appeal until another 30 days have elapsed.

Verifiers

Since this season is a bit drawn out and some community members have expressed interest in verification, we have decided to open verifier applications earlier than we normally do! We are currently looking to fill 3? spots, so if you’re interested, please fill out the form here: https://forms.gle/X3GM9bUEzms9okSm7

In addition, some community members have pointed out some issues with verification accuracy. In response, Aegis is working on a more straightforward verification guide for every category that will make it easier to spot timing mistakes as runners and to time runs correctly as verifiers, which can be found here: https://docs.google.com/document/d/19i8YG9y8FVTdMd-yOrcyOQb8GE68_jVMJNAlSUMq4NQ/edit?usp=sharing If you have any concerns about your run’s (or any run’s) timing, please do not hesitate to reach out to the verifier who timed your run or a moderator, if needed.

Overlay requirement

The mod team has reassessed its policy on input overlay requirements since the last time we discussed this a few years ago. At the time, we agreed that lowering the barrier to entry for submission was more important than the off chance that a macro was being used to make movement tech consistent. Today, runners have gotten more bold with their attempts to utilize macros and other tools in RTA runs, and the majority of runners that are using advanced movement tech are more than capable of using OBS and NohBoard in order to overlay inputs over their run.

As such, going forward we are going to require a standard left half of keyboard + mouse or controller input overlay for any potential top 3 runs that utilize excessive groundlines, relic groundlines, or diagonal/horizontal rocket grapples. In addition to potential macro checking, this will help combat macro usage concerns that have been brought up recently.